By using AWS re:Post, you agree to the Terms of Use
/Do we have to Spice duplicate data?/

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?

asked 2 months ago21 views
1 Answers
Accepted Answer

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.

If any of the logical tables refer to a QuickSight dataset that is a parent dataset:
The parent dataset must use direct query.

answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions