スキップしてコンテンツを表示

AWS re:Postを使用することにより、以下に同意したことになります AWS re:Post 利用規約

Do we have to Spice duplicate data?

0

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?

トピック: 分析
タグ: Amazon QuickSight
言語: English

質問済み 4年前450ビュー

1回答

新しい順
投票が多い順
コメントが多い順

これらの回答は役に立ちましたか？コミュニティがあなたの知識を活用できるように、正解に賛成票を投じてください。

0

承認された回答

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.

エキスパート

回答済み 4年前

関連するコンテンツ