# \[Ann\] Elasticsearch Skywalker Plugin **URL:** \ **Category:** Elasticsearch\ **Created:** [May 30, 2012, 8:20pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922 "2012-05-30T20:20:09Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [May 30, 2012, 8:20pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922/1 "2012-05-30T20:20:09Z")
Hi, some discussions lately - for example I enjoyed [https://github.com/elasticsearch/elasticsearch/issues/1934](https://github.com/elasticsearch/elasticsearch/issues/1934) with Stefan Fussenegger - showed me that I was rather clueless about the JSON object field model and how it maps to Lucene fields. So I started to look if I could examine the IndexReaders, Stores, and other objects down in the very deep internals of a shard. My idea was to check out how Luke works and to implement some of the interesting aspects of Luke the Elasticsearch way. The Skywalker plugin for Elasticsearch is like Luke for Lucene. Well, almost, it's not coming with a GUI right now. Skywalking gives you - ## a deeper insight of how Elasticsearch stores Lucene indices and fields ## lists timestamps and checksums of Elasticsearch's Lucene files ## shows field names, both from mapping and Lucene indices ## shows field types and attributes, both from mapping and Lucene indices retrieves a ranked list of most frequent terms Because Elasticsearch and Elasticsearch Head offers already a lot what Luke does with Lucene, Skywalker has rather few features, just to complement some missing parts. More details are here: [https://github.com/jprante/elasticsearch-skywalker](https://github.com/jprante/elasticsearch-skywalker) In the hope it's useful, Jörg ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [May 30, 2012, 8:36pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922/2 "2012-05-30T20:36:36Z")
That's great Jörg ! I will play with it tomorrow... Thanks for sharing it to us. David Le 30 mai 2012 à 22:20, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) a écrit : > Hi, > > some discussions lately - for example I enjoyed [Add an optional \_all field like index to mapped objects · Issue #1934 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1934) with Stefan Fussenegger - showed me that I was rather clueless about the JSON object field model and how it maps to Lucene fields. So I started to look if I could examine the IndexReaders, Stores, and other objects down in the very deep internals of a shard. > > My idea was to check out how Luke works and to implement some of the interesting aspects of Luke the Elasticsearch way. The Skywalker plugin for Elasticsearch is like Luke for Lucene. > Well, almost, it's not coming with a GUI right now. > > Skywalking gives you > > a deeper insight of how Elasticsearch stores Lucene indices and fields > lists timestamps and checksums of Elasticsearch's Lucene files > shows field names, both from mapping and Lucene indices > shows field types and attributes, both from mapping and Lucene indices > retrieves a ranked list of most frequent terms > Because Elasticsearch and Elasticsearch Head offers already a lot what Luke does with Lucene, Skywalker has rather few features, just to complement some missing parts. > > More details are here: [GitHub - jprante/elasticsearch-skywalker: Skywalker for Elasticsearch is like Luke for Lucene](https://github.com/jprante/elasticsearch-skywalker) > > In the hope it's useful, > > Jörg ---
**Author:** ![Tanguy1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tanguy1/32/1749_2.png) [@Tanguy1](https://discuss.elastic.co/u/Tanguy1)\ **Post date:** [May 31, 2012, 7:30am UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922/3 "2012-05-31T07:30:18Z")
That sounds great, thanks. -- Tanguy Le mercredi 30 mai 2012 22:20:09 UTC+2, Jörg Prante a écrit : > Hi, > > some discussions lately - for example I enjoyed > [Add an optional \_all field like index to mapped objects · Issue #1934 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1934) with Stefan > Fussenegger - showed me that I was rather clueless about the JSON object > field model and how it maps to Lucene fields. So I started to look if I > could examine the IndexReaders, Stores, and other objects down in the very > deep internals of a shard. > > My idea was to check out how Luke works and to implement some of the > interesting aspects of Luke the Elasticsearch way. The Skywalker plugin > for Elasticsearch is like Luke for Lucene. > > Well, almost, it's not coming with a GUI right now. > > Skywalking gives you > > - > > ## a deeper insight of how Elasticsearch stores Lucene indices and fields > > ## lists timestamps and checksums of Elasticsearch's Lucene files > > ## shows field names, both from mapping and Lucene indices > > ## shows field types and attributes, both from mapping and Lucene indices > > retrieves a ranked list of most frequent terms > > Because Elasticsearch and Elasticsearch Head offers already a lot what > Luke does with Lucene, Skywalker has rather few features, just to > complement some missing parts. > More details are here: [GitHub - jprante/elasticsearch-skywalker: Skywalker for Elasticsearch is like Luke for Lucene](https://github.com/jprante/elasticsearch-skywalker) > > In the hope it's useful, > > Jörg ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [June 1, 2012, 4:44pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922/4 "2012-06-01T16:44:24Z")
Very cool! I am currently investigating why my index is quite large, so perhaps skywalker can provide some insights. First, installing 1.0.0 does not work since there is no zip file in Github: Trying [https://github.com/downloads/jprante/elasticsearch-skywalker/elasticsearch-skywalker-1.0.0.zip](https://github.com/downloads/jprante/elasticsearch-skywalker/elasticsearch-skywalker-1.0.0.zip)... Trying [https://github.com/jprante/elasticsearch-skywalker/zipball/v1.0.0](https://github.com/jprante/elasticsearch-skywalker/zipball/v1.0.0)... Failed to install jprante/elasticsearch-skywalker/1.0.0, reason: failed to download There is a jar file, but not a zip. Second, I cannot get the plugin to work after install master. Is it because I am running ES 0.19.2? [2012-06-01 09:41:11,940][INFO][node] [Mantra] {0.19.2}[7388]: initializing ... [2012-06-01 09:41:11,947][INFO][plugins] [Mantra] loaded , sites [skywalker, head] No handler found for uri [/\_skywalker] and method [GET] Cheers, Ivan On Wed, May 30, 2012 at 1:20 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Hi, > > some discussions lately - for example I > enjoyed [Add an optional \_all field like index to mapped objects · Issue #1934 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1934) with > Stefan Fussenegger - showed me that I was rather clueless about the JSON > object field model and how it maps to Lucene fields. So I started to look if > I could examine the IndexReaders, Stores, and other objects down in the very > deep internals of a shard. > > My idea was to check out how Luke works and to implement some of the > interesting aspects of Luke the Elasticsearch way. The Skywalker plugin for > Elasticsearch is like Luke for Lucene. > > Well, almost, it's not coming with a GUI right now. > > Skywalking gives you > > a deeper insight of how Elasticsearch stores Lucene indices and fields > > lists timestamps and checksums of Elasticsearch's Lucene files > > shows field names, both from mapping and Lucene indices > > shows field types and attributes, both from mapping and Lucene indices > > retrieves a ranked list of most frequent terms > > Because Elasticsearch and Elasticsearch Head offers already a lot what Luke > does with Lucene, Skywalker has rather few features, just to complement some > missing parts. > > More details are here: [GitHub - jprante/elasticsearch-skywalker: Skywalker for Elasticsearch is like Luke for Lucene](https://github.com/jprante/elasticsearch-skywalker) > > In the hope it's useful, > > Jörg ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [June 1, 2012, 11:09pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922/5 "2012-06-01T23:09:42Z")
Hi Ivan, I added the zip file, sorry for inconvenience. In your plugin list, skywalker is listed as a 'site' plugin. This will not work, it should be listed under 'loaded'. Jörg On Friday, June 1, 2012 6:44:24 PM UTC+2, Ivan Brusic wrote: > Very cool! I am currently investigating why my index is quite large, > so perhaps skywalker can provide some insights. > > First, installing 1.0.0 does not work since there is no zip file in > Github: > > Trying > [https://github.com/downloads/jprante/elasticsearch-skywalker/elasticsearch-skywalker-1.0.0.zip](https://github.com/downloads/jprante/elasticsearch-skywalker/elasticsearch-skywalker-1.0.0.zip)... > > Trying [https://github.com/jprante/elasticsearch-skywalker/zipball/v1.0.0](https://github.com/jprante/elasticsearch-skywalker/zipball/v1.0.0)... > > Failed to install jprante/elasticsearch-skywalker/1.0.0, reason: > failed to download > > There is a jar file, but not a zip. > > Second, I cannot get the plugin to work after install master. Is it > because I am running ES 0.19.2? > > [2012-06-01 09:41:11,940][INFO][node] [Mantra] > {0.19.2}[7388]: initializing ... > [2012-06-01 09:41:11,947][INFO][plugins] [Mantra] > loaded , sites [skywalker, head] > > No handler found for uri [/\_skywalker] and method [GET] > > Cheers, > > Ivan > > On Wed, May 30, 2012 at 1:20 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) > wrote: > > > Hi, > > > > some discussions lately - for example I > > enjoyed [Add an optional \_all field like index to mapped objects · Issue #1934 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1934) with > > Stefan Fussenegger - showed me that I was rather clueless about the JSON > > object field model and how it maps to Lucene fields. So I started to > > look if > > I could examine the IndexReaders, Stores, and other objects down in the > > very > > deep internals of a shard. > > > > My idea was to check out how Luke works and to implement some of the > > interesting aspects of Luke the Elasticsearch way. The Skywalker plugin > > for > > Elasticsearch is like Luke for Lucene. > > > > Well, almost, it's not coming with a GUI right now. > > > > Skywalking gives you > > > > a deeper insight of how Elasticsearch stores Lucene indices and fields > > > > lists timestamps and checksums of Elasticsearch's Lucene files > > > > shows field names, both from mapping and Lucene indices > > > > shows field types and attributes, both from mapping and Lucene indices > > > > retrieves a ranked list of most frequent terms > > > > Because Elasticsearch and Elasticsearch Head offers already a lot what > > Luke > > does with Lucene, Skywalker has rather few features, just to complement > > some > > missing parts. > > > > More details are here: > > [GitHub - jprante/elasticsearch-skywalker: Skywalker for Elasticsearch is like Luke for Lucene](https://github.com/jprante/elasticsearch-skywalker) > > > > In the hope it's useful, > > > > Jörg ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [June 2, 2012, 1:01am UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922/6 "2012-06-02T01:01:10Z")
No problems. Just trying to help out the project by highlighting issues. Will test the site issue next week. Should it work with ES 0.19.2? -- Ivan On Fri, Jun 1, 2012 at 4:09 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) wrote: > Hi Ivan, > > I added the zip file, sorry for inconvenience. > > In your plugin list, skywalker is listed as a 'site' plugin. This will not > work, it should be listed under 'loaded'. > > Jörg > > On Friday, June 1, 2012 6:44:24 PM UTC+2, Ivan Brusic wrote: > > > Very cool! I am currently investigating why my index is quite large, > > so perhaps skywalker can provide some insights. > > > > First, installing 1.0.0 does not work since there is no zip file in > > Github: > > > > Trying > > [https://github.com/downloads/jprante/elasticsearch-skywalker/elasticsearch-skywalker-1.0.0.zip](https://github.com/downloads/jprante/elasticsearch-skywalker/elasticsearch-skywalker-1.0.0.zip)... > > Trying > > [https://github.com/jprante/elasticsearch-skywalker/zipball/v1.0.0](https://github.com/jprante/elasticsearch-skywalker/zipball/v1.0.0)... > > Failed to install jprante/elasticsearch-skywalker/1.0.0, reason: > > failed to download > > > > There is a jar file, but not a zip. > > > > Second, I cannot get the plugin to work after install master. Is it > > because I am running ES 0.19.2? > > > > [2012-06-01 09:41:11,940][INFO][node] [Mantra] > > {0.19.2}[7388]: initializing ... > > [2012-06-01 09:41:11,947][INFO][plugins] [Mantra] > > loaded , sites [skywalker, head] > > > > No handler found for uri [/\_skywalker] and method [GET] > > > > Cheers, > > > > Ivan > > > > On Wed, May 30, 2012 at 1:20 PM, Jörg Prante [joergprante@gmail.com](mailto:joergprante@gmail.com) > > wrote: > > > > > Hi, > > > > > > some discussions lately - for example I > > > enjoyed [Add an optional \_all field like index to mapped objects · Issue #1934 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1934) with > > > Stefan Fussenegger - showed me that I was rather clueless about the JSON > > > object field model and how it maps to Lucene fields. So I started to > > > look if > > > I could examine the IndexReaders, Stores, and other objects down in the > > > very > > > deep internals of a shard. > > > > > > My idea was to check out how Luke works and to implement some of the > > > interesting aspects of Luke the Elasticsearch way. The Skywalker plugin > > > for > > > Elasticsearch is like Luke for Lucene. > > > > > > Well, almost, it's not coming with a GUI right now. > > > > > > Skywalking gives you > > > > > > a deeper insight of how Elasticsearch stores Lucene indices and fields > > > > > > lists timestamps and checksums of Elasticsearch's Lucene files > > > > > > shows field names, both from mapping and Lucene indices > > > > > > shows field types and attributes, both from mapping and Lucene indices > > > > > > retrieves a ranked list of most frequent terms > > > > > > Because Elasticsearch and Elasticsearch Head offers already a lot what > > > Luke > > > does with Lucene, Skywalker has rather few features, just to complement > > > some > > > missing parts. > > > > > > More details are here: > > > [GitHub - jprante/elasticsearch-skywalker: Skywalker for Elasticsearch is like Luke for Lucene](https://github.com/jprante/elasticsearch-skywalker) > > > > > > In the hope it's useful, > > > > > > Jörg ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:25am UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-plugin/7922/7 "2017-07-06T03:25:56Z")