Open maoning opened 6 years ago
I have the same issue when adding geo context to my context suggester field and set path for its geo field. Any update available for this?
PS: I'm using El 6.2.2
"index" => array:5 [
"_index" => "v1"
"_type" => "_doc"
"_id" => "98270402205220"
"status" => 400
"error" => array:2 [
"type" => "number_format_exception"
"reason" => "null"
]
]
I'm able to reproduce this on master, it looks like it's expecting a geohash but instead gets the coordinate pair as a string
@elastic/es-search-aggs
Pinging @elastic/es-search (Team:Search)
Pinging @elastic/es-search-relevance (Team:Search Relevance)
Elasticsearch version (
bin/elasticsearch --version
): Version: 5.4.2JVM version (
java -version
): 1.8.0_141OS version (
uname -a
if on a Unix-like system): Linux 3.10.0-693.11.6.el7.x86_64 #1 SMP Thu Jan 4 01:06:37 UTC 2018 x86_64 x86_64 x86_64 GNU/LinuxDescription of the problem including expected versus actual behavior: When path field in geo type context suggester refers to a stored field, ES fails at indexing documents with error:
Steps to reproduce:
Provide logs (if relevant):