Open DannyDu26 opened 2 years ago
I think the answer of the 1st question is the object type in ElasticSearch is currently not supported by Presto.
But for the 2nd question, even field type in ElasticSearch mapping is number, it still can be a string. e.g. data could be: {"rolelevel": "165"} or {"rolelevel": 165} the link below just show why. (https://www.elastic.co/guide/en/elasticsearch/reference/current/coerce.html#coerce) I would like to know if this problem is resolved in the newer version?
After I set all the field type to text, I resolved the 2nd error. But still another error. ElasticSearch can still save boolean like true or false in text filed, which will cause this error.
// Exception
java.sql.SQLException: Query failed (#20220524_021033_00005_yecxa): Expected a string or numeric value for field 'isbinding' of type VARCHAR: false [Boolean]
// mapping
"isbinding": {
"type": "text",
"store": true
},
// data
{"isbinding": false,}
Got some errors while using ElasticSearch Connector.
ElasticSearch index mapping
ElasticSearch index mapping