Just pushed this: http://github.com/elasticsearch/elasticsearch/issues/issue/152. Basically,
the idea I had is to create a wrapper on top of how elasticsearch handles
JSON allowing for other wire formats (with same JSON characteristics) to be
supported. The first implementation aside from JSON is XSON, which is an
optimized binary format of JSON (I will doc the BNF soon).
A note for Java API users, some classes have been renamed. The previous
JsonXXX have been removed and renamed. Also, by default, the query / filter
builders and the search source builders use the XSON format which means
faster operations :). It is up to you to decide how to encode the indexable
data, either using JSON or XSON. ElasticSearch will automatically handle
both.
Hi,
Just pushed
this: XContent - An abstraction on top of content (JSON inspired) · Issue #152 · elastic/elasticsearch · GitHub.
Basically, the idea I had is to create a wrapper on top of how elasticsearch
handles JSON allowing for other wire formats (with same JSON
characteristics) to be supported. The first implementation aside from JSON
is XSON, which is an optimized binary format of JSON (I will doc the BNF
soon).
A note for Java API users, some classes have been renamed. The previous
JsonXXX have been removed and renamed. Also, by default, the query / filter
builders and the search source builders use the XSON format which means
faster operations :). It is up to you to decide how to encode the indexable
data, either using JSON or XSON. Elasticsearch will automatically handle
both.
cheers,
shay.banon
BSon might also be supported, but I don't really like the format as its not
aimed at streaming data (pull parsing). For example, you need to write the
size of the array before you write all its elements. This is an aspect of
JSON that I really wanted to preserve.
Also, BSON is a superset of JSON, while XSON is exactly like JSON.
Hi,
Just pushed
this: http://github.com/elasticsearch/elasticsearch/issues/issue/152.
Basically, the idea I had is to create a wrapper on top of how
elasticsearch
handles JSON allowing for other wire formats (with same JSON
characteristics) to be supported. The first implementation aside from
JSON
is XSON, which is an optimized binary format of JSON (I will doc the BNF
soon).
A note for Java API users, some classes have been renamed. The previous
JsonXXX have been removed and renamed. Also, by default, the query /
filter
builders and the search source builders use the XSON format which means
faster operations :). It is up to you to decide how to encode the
indexable
data, either using JSON or XSON. Elasticsearch will automatically handle
both.
cheers,
shay.banon
BSon might also be supported, but I don't really like the format as
its not aimed at streaming data (pull parsing). For example, you
need to write the size of the array before you write all its
elements. This is an aspect of JSON that I really wanted to preserve.
Also, BSON is a superset of JSON, while XSON is exactly like JSON.
Basically, the idea I had is to create a wrapper on top of how
elasticsearch
handles JSON allowing for other wire formats (with same JSON
characteristics) to be supported. The first implementation aside
from JSON
is XSON, which is an optimized binary format of JSON (I will doc
the BNF
soon).
A note for Java API users, some classes have been renamed. The
previous
JsonXXX have been removed and renamed. Also, by default, the
query / filter
builders and the search source builders use the XSON format which
means
faster operations :). It is up to you to decide how to encode the
indexable
data, either using JSON or XSON. Elasticsearch will automatically
handle
both.
cheers,
shay.banon
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.