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.
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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.