Do we have to Spice duplicate data?
When joining 2 pre-existing datasets where at least 1 is spiced, the resulting 3rd dataset automatically defaults to be spiced also, with no apparent way of changing this. is this the expected behaviour?
The datasets are all from the same data source. This results in the data in the parent dataset that is spiced being also spiced in the child dataset, resulting in a double charge for this data.
If this is correct, are there any plans to change this, so that the customer only pays for the same data once?
Hi, @PhillB.
This is a designed behavior.
Your pattern does not meet the following, so it is considered a cross-source join and will be loaded into SPICE.
https://docs.aws.amazon.com/quicksight/latest/user/joining-data.html
If any of the logical tables refer to a QuickSight dataset that is a parent dataset:
The parent dataset must use direct query.
Relevant questions
Do we have to Spice duplicate data?
Accepted Answerasked 2 months agoList of AWS Spice datasets and it's size
asked 3 months agoError bringing in additional datasets/tables to Amazon Quicksight Dataset
asked 4 months agoRedshift Spectrum: no way to glance at tables with nested data
asked 3 years agoJoining Datasets with != Conditions in Quicksight
asked 7 months agoDelete Images in Custom Labels Datasets
asked 2 years agoHow to resolve the issues in viewing the dataset and creating the calculated fields when using edit dataset option in quicksight?
asked 7 months agoQuicksight dataset SPICE refresh not loading data
asked 2 months agoQuicksight not able to ingest dataset bigger than 1GB at a time
asked 5 months agoHow to create revisions automatically when a new file is added to S3?
asked a year ago