I have a dataset that is failing to import to spice, I want to change it to direct query while we solve the problem but the toggle doesn’t appear when I edit the dataset
Hi @JavierC
do you join datasets within the dataset?
BR
1 Like
Are they build based on the same datasource?
Yes, same data source from Athena
Validate DataSources . You could have created multiple Athena datasources which means cross data source connection with the end result being SPICE.
Data Source 1
Data Source 2
Result
Kind regards,
Koushik
Yes what we want to say. You have to make sure the datasets are using the same QuickSight datasource. Even both using the same Athena source.
e.g. Athena$ - datasourceA - dataset1 join Athena$ - datasourceB - dataset2 will end up as a SPICE dataset.
I checked, all queries are from the same DataSource
@JavierC ,
Could you paste a few screenshots ?
@JavierC ,
The last test I can think of is to check existing datasources so that the datasources have not been created multiple times.
@JavierC
If possible you could also check the datasource id of each dataset via API
Hello @JavierC, I am pretty sure that once you create your joins within the QuickSight console, it will only allow for SPICE ingestion of the overall dataset. The best solution here would be to join your datasource tables/views within SQL either in Athena or in QuickSight and ingesting as a single dataset. That will ensure you can run this on direct query rather than only being able to set it to SPICE.
Since you are utilizing Athena, you can build the joins directly in the Athena console to create a new View. Then you can import that directly into QuickSight.