I am trying to get data from OpenSearch into Quicksight. I successfully added a data source and could see my indices. When I try to create a dataset, I get an error that “fields were skipped because they use unsupported data types.” These are all text fields; they are set up as multi-fields, so they also have a keyword version (for example, account_name.raw).
I have tried adding a keyword version of the field with copy_to. The field appears in the field list, but has no data; it seems this will require re-indexing everything.
I also tried creating an OpenSearch dataset with custom SQL to cast the text fields to keyword types. A query like this returns results in the OpenSearch console:
select account, CAST(account_name as string) as account_name from bill-issues
The results show the account_name field being returned as keyword:
Creating the dataset through boto3 (create_data_set with the query in CustomSql) returned a 200 (success), and I can see the dataset in the Quicksight UI. But when I edit the dataset, I get a popup that says
Can’t perform this action
Something went wrong
with no other information. If I close the popup, I can see and edit my SQL, but even select * from bill-issues gives the same error.
How can I get OpenSearch text fields converted to string / keyword fields so that I can use them in Quicksight?
Thanks for the suggestion, but the text fields don’t get imported Quicksight dataset at all: “fields were skipped because they use unsupported data types.” The skipped fields are not in the field list on the left side.
I ran into this problem as well and the only solution I could come up with was adding new keyword fields to the index for the text fields I wanted to report on and then populating them in my ingestion pipeline