Child dataset of RLS-enabled SPICE dataset fixed to Direct Query mode

[hoyeon]

I tried to create a child dataset of RLS-enabled SPICE dataset to test joining with other dataset.

I noticed that was changed to Direct Query mode in dataset creation page.

Q1. Why is it happening?
Q2. What does it mean by Direct Query mode for parent SPICE dataset?

[Pradeep_Subramanian]

Hi @hoyeon

As per my understanding, we can only create child datasets from datasets with RLS rules active in direct query

Attaching reference links FYR

Create a Child Dataset that is Spice from a Direct Query

I’m trying to work around the limitations of Row level security in Quicksight where you cannot create a child dataset of a SPICE Dataset with RLSS applied. The Master Dataset is an absolutely enormous (~500 million rows) dataset, and my intention is to use it as a master dataset that I can then take pieces off of. However, for one of my main purposes, I just want to make a copy of the Direct Query version into spice, so I can take advantage of the SPICE performance. Is such a thing possible? …

Creating a dataset using an existing dataset in Amazon QuickSight - Amazon...

Thanks,
Pradeep S

[hoyeon]

@Pradeep_Subramanian
I noticed that joining with other RLS-enabled parent dataset in the child dataset fails with this error.

“Can’t create join. Joining tables from different sources requires SPICE, which this dataset isn’t permitted to use. To continue, you’ll need to remove the join.”

Does it mean that if any of parent datasets enabled RLS rules then those cannot be used in child dataset for joining?

[Pradeep_Subramanian]

@hoyeon

Yes, that is correct.

I recreated the same scenario and it’s not possible to join parent dataset enabled RLS with a child dataset. Because, whenever we create a child dataset from a RLS enabled parent dataset, that becomes a direct query

Regards,
Pradeep S