Our application creates a 64-bit hash id that is stored in an
ElastichSearch long field. We have some problems retrieving
documents. Retrieving "_source" works. Trying to retrieve any
specific field(s) causes the following error from some shards:
Can you create a recreation? Even when indexing, if it works, your numbers
will loose resolution if they are too big since they are converted to a
long number.
I'm a C++ programmer using the HTTP interface. I didn't realize that
Java doesn't have unsigned integers.
I understand what you are saying. Java is not able to parse the value
so that field would not be indexed. I can see them in the _source,
because that is the exact json text I sent. A search asking for
specifc fields causes the _source to be parsed which generates the
Java error.
If I wanted 64 bit hash ID's I would have to cast the unsigned value
to a signed value before passing it to ElasticSearch.
Actually I have the same problem when running ES 0.19.3. I also have 64-bit
hashed id for many different attributes in our documents, but it seems ES
can't automatically recognize these id's:
On Monday, January 9, 2012 2:58:29 PM UTC-5, kimchy wrote:
Can you create a recreation? Even when indexing, if it works, your numbers
will loose resolution if they are too big since they are converted to a
long number.
Actually I have the same problem when running ES 0.19.3. I also have
64-bit hashed id for many different attributes in our documents, but it
seems ES can't automatically recognize these id's:
On Monday, January 9, 2012 2:58:29 PM UTC-5, kimchy wrote:
Can you create a recreation? Even when indexing, if it works, your
numbers will loose resolution if they are too big since they are converted
to a long number.
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.