The geo_point type does not support passing the lat / lon as an array. I
will update the docs to reflect that. The problem is that I can't tell (at
the parsing / mapping abstraction type) if its a single point array of
lat/lon, or array of points.
The geo_point type does not support passing the lat / lon as an
array. I will update the docs to reflect that. The problem is that I
can't tell (at the parsing / mapping abstraction type) if its a single
point array of lat/lon, or array of points.
Well, if the first value of the array is a scalar, then it is
[lat,long], otherwise it is an array of points, no?
Yes, but its problematic in how the current implementation is built, which
basically derived from the fact that I pull parse the json (never create a
full in memory representation of it, ala map of maps).
The geo_point type does not support passing the lat / lon as an
array. I will update the docs to reflect that. The problem is that I
can't tell (at the parsing / mapping abstraction type) if its a single
point array of lat/lon, or array of points.
Well, if the first value of the array is a scalar, then it is
[lat,long], otherwise it is an array of points, no?
The geo_point type does not support passing the lat / lon as an array. I
will update the docs to reflect that. The problem is that I can't tell (at
the parsing / mapping abstraction type) if its a single point array of
lat/lon, or array of points.
The geo_point type does not support passing the lat / lon as an array.
I
will update the docs to reflect that. The problem is that I can't tell
(at
the parsing / mapping abstraction type) if its a single point array of
lat/lon, or array of points.
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.