# \[ANN\] Elasticsearch Skywalker 3.0.0

**URL:** <https://discuss.elastic.co/t/ann-elasticsearch-skywalker-3-0-0/12119>\
**Category:** Elasticsearch\
**Created:** [May 24, 2013, 10:20pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-3-0-0/12119 "2013-05-24T22:20:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**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 24, 2013, 10:20pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-3-0-0/12119/1 "2013-05-24T22:20:58Z")

</div>

Hi,

I have pushed the Skywalker project to version 3.0.0 which gives  
compatibility with Elasticsearch 0.90

If you don't know it - Skywlker is a plugin that can dump Elasticsearch  
structures in a manner like Luke can examine Lucene. It's JSON output only,  
no UI.

For me, Skywalker serves as a simple learning tool to explore Lucene und ES  
API and data structure internals.

Changes:

- update to ES 0.90 (Lucene 4.2.1)
- package name moved to org.xbib.elasticsearch
- added two REST commands, one for cluster state file consistency check,  
and one for reconstruction, dumping all documents and terms of a given index

Example:

curl 0:9200/\_cluster/consistency

The \_cluster/consistency bypasses the currently active cluster state, it  
reads the ES cluster state files from disk, and writes the "metadata" back  
as JSON, together with the absolute file names of the cluster state of the  
node. If the state files are lost/corrupt, no "metadata" entry will be  
shown in the output.

curl 0:9200/indexname/\_reconstruct

Hopefully, one day in the future, the \_reconstruct command can be used to  
recreate indices/mappings settings if the cluster state is lost/corrupt and  
only Lucene indices are there. For now, it is just dumping what is found in  
the Lucene Index.

Project page:

> **[jprante/elasticsearch-skywalker](https://github.com/jprante/elasticsearch-skywalker)**
>
> elasticsearch-skywalker - Skywalker for Elasticsearch is like Luke for Lucene

Binaries are at Bintray.

Hope you enjoy it,

Jörg

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![btiernay](https://avatars.discourse-cdn.com/v4/letter/b/bb73d2/32.png) [@btiernay](https://discuss.elastic.co/u/btiernay)\
**Post date:** [May 24, 2013, 11:00pm UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-3-0-0/12119/2 "2013-05-24T23:00:49Z")

</div>

Very nice indeed. Thanks Jörg 🙂

On Friday, 24 May 2013 18:20:58 UTC-4, Jörg Prante wrote:

> Hi,
> 
> I have pushed the Skywalker project to version 3.0.0 which gives  
> compatibility with Elasticsearch 0.90
> 
> If you don't know it - Skywlker is a plugin that can dump Elasticsearch  
> structures in a manner like Luke can examine Lucene. It's JSON output only,  
> no UI.
> 
> For me, Skywalker serves as a simple learning tool to explore Lucene und  
> ES API and data structure internals.
> 
> Changes:
> 
> - update to ES 0.90 (Lucene 4.2.1)
> - package name moved to org.xbib.elasticsearch
> - added two REST commands, one for cluster state file consistency check,  
> and one for reconstruction, dumping all documents and terms of a given index
> 
> Example:
> 
> curl 0:9200/\_cluster/consistency
> 
> The \_cluster/consistency bypasses the currently active cluster state, it  
> reads the ES cluster state files from disk, and writes the "metadata" back  
> as JSON, together with the absolute file names of the cluster state of the  
> node. If the state files are lost/corrupt, no "metadata" entry will be  
> shown in the output.
> 
> curl 0:9200/indexname/\_reconstruct
> 
> Hopefully, one day in the future, the \_reconstruct command can be used to  
> recreate indices/mappings settings if the cluster state is lost/corrupt and  
> only Lucene indices are there. For now, it is just dumping what is found in  
> the Lucene Index.
> 
> Project page:
> 
> [GitHub - jprante/elasticsearch-skywalker: Skywalker for Elasticsearch is like Luke for Lucene](https://github.com/jprante/elasticsearch-skywalker)
> 
> Binaries are at Bintray.
> 
> Hope you enjoy it,
> 
> Jörg

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**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, 2:34am UTC](https://discuss.elastic.co/t/ann-elasticsearch-skywalker-3-0-0/12119/3 "2017-07-06T02:34:52Z")

</div>


