- Newest
- Most votes
- Most comments
I've been able to enable cursors using an undocumented feature: sending the settings to the query endpoint instead of the _cluster/settings:
PUT _opendistro/_sql/settings
{
"persistent" : {
"opendistro.sql.cursor.enabled" : true
}
}
{
"acknowledged" : true,
"persistent" : {
"opendistro" : {
"sql" : {
"cursor" : {
"enabled" : "true"
}
}
}
},
"transient" : { }
}
works.
After this it is possible to ingest data to SPICE from QS.
Hi - I believe this is due to "The ElasticSearch/OpenSearch domain doesn't have SQL cursors enabled ("opendistro.sql.cursor.enabled" : "true")." (1). The Cursor is one of the settings you can configure on your cluster (2). You can enable it using Kibana or CLI as well.
(1) https://docs.aws.amazon.com/quicksight/latest/user/errors-skipped-rows-during-import.html
(2) https://opendistro.github.io/for-elasticsearch-docs/docs/sql/settings/
I don't understand how this can be the accepted answer, that setting is removed from OpenSearch since version 1.0. https://github.com/opensearch-project/sql/pull/75
It is not working in OpenSearch v1.2 either.
Relevant content
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 days ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 8 months ago