We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
text
Search doesn't work properly for fields of non-keyword data type. Mapping
keyword
{ "mappings": { "properties": { "numbers": { "type": "text", "fields": { "values": { "type": "integer" } } } } } }
Create new index:
$ curl -s -H 'Content-Type: application/json' -XPUT "http://localhost:9200/tmp?pretty" -d '{"mappings": {"properties": {"numbers": {"type": "text", "fields": {"values": {"type": "integer"}}}}}}' { "acknowledged" : true, "shards_acknowledged" : true, "index" : "tmp" }
Add a doc:
$ curl -s -H 'Content-Type: application/json' -XPOST "http://localhost:9200/tmp/_doc?pretty" -d '{"numbers": [12, 20, 30]}'
Validate data:
$ curl -s -XGET "http://localhost:9200/tmp/_search?pretty" | jq .hits.hits
[ { "_index": "tmp", "_id": "wNh6soQBeC3wK8rxBHNm", "_score": 1, "_source": { "numbers": [ 12, 20, 30 ] } } ]
$ curl -s -H 'Content-Type: application/json' -XGET "http://localhost:9200/tmp/_search?pretty" -d '{"query": {"match_all": {}}, "fields": ["numbers", "numbers.values"], "_source": false}' | jq .hits.hits
[ { "_index": "tmp", "_id": "wNh6soQBeC3wK8rxBHNm", "_score": 1, "fields": { "numbers.values": [ 12, 20, 30 ], "numbers": [ "12", "20", "30" ] } } ]
Try an SQL query:
opensearchsql> select numbers from tmp; fetched rows / total rows = 1/1 +-----------+ | numbers | |-----------| | 12 | +-----------+ opensearchsql> select numbers.values from tmp; {'reason': 'Invalid SQL query', 'details': "can't resolve Symbol(namespace=FIELD_NAME, name=numbers.values) in type env", 'type': 'SemanticCheckException'} opensearchsql> select * from tmp where numbers.values = 20; {'reason': 'Invalid SQL query', 'details': "can't resolve Symbol(namespace=FIELD_NAME, name=numbers.values) in type env", 'type': 'SemanticCheckException'}
$ curl -s -XPOST http://localhost:9200/_plugins/_sql -H 'Content-Type: application/json' -d '{"query": "select numbers from tmp;"}'
{ "schema": [ { "name": "numbers", "type": "text" } ], "datarows": [ [ "12" ] ], "total": 1, "size": 1, "status": 200 }
Listed above queries should return something like this:
12 20 30
12, 20, 30
"12 20 30"
[12, 20, 30]
["12", "20", "30"]
Add limitation section to documentation and return error on querying such kind of fields (aka columns).
Related to #794, #1038 and #1113.
The text was updated successfully, but these errors were encountered:
Mapping could be even more complex:
"fields": { "keyword": { "ignore_above": 128, "type": "keyword" }, "float": { "ignore_malformed": true, "type": "float" } }
Sorry, something went wrong.
OpenSearchDataType
No branches or pull requests
Is your feature request related to a problem?
Search doesn't work properly for fields of non-
keyword
data type.Mapping
Create new index:
Add a doc:
$ curl -s -H 'Content-Type: application/json' -XPOST "http://localhost:9200/tmp/_doc?pretty" -d '{"numbers": [12, 20, 30]}'
Validate data:
$ curl -s -XGET "http://localhost:9200/tmp/_search?pretty" | jq .hits.hits
$ curl -s -H 'Content-Type: application/json' -XGET "http://localhost:9200/tmp/_search?pretty" -d '{"query": {"match_all": {}}, "fields": ["numbers", "numbers.values"], "_source": false}' | jq .hits.hits
Try an SQL query:
$ curl -s -XPOST http://localhost:9200/_plugins/_sql -H 'Content-Type: application/json' -d '{"query": "select numbers from tmp;"}'
What solution would you like?
Listed above queries should return something like this:
12 20 30
12, 20, 30
"12 20 30"
[12, 20, 30]
["12", "20", "30"]
What alternatives have you considered?
Add limitation section to documentation and return error on querying such kind of fields (aka columns).
Do you have any additional context?
Related to #794, #1038 and #1113.
The text was updated successfully, but these errors were encountered: