Can topic can be created only on spice dataset?

I’m trying to create a Q topic on a dataset (live query on snowflake), and i get error of extraction fail, once i change the dataset to be spice its working.
is it possible that i can’t build a topic on top of live query dataset? if so why?

1 Like

Hello Netser,

No, Creating topic on direct query dataset should work as well. I am not sure how big the data set is like the number of rows. how fast is it in generating the output ?

May be its temporary issue. If issue persist, I would recommend filing a case with AWS Support where support engineer can dive into the details so that we can help you further. Here are the steps to open a support case . If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf.

hope this helps.
Cheers,
Deep

1 Like

Hello @Netser, I was looking through some documentation on this as well and it does look like Direct Query is supported like @Deep mentioned, but it also seems to function similarly to a SPICE dataset.

This has some of the best documentation I have been able to find regarding datasets with Q topics. Hopefully this gives you a little more insight into the issue you are facing as well. Maybe you need to set up some of the items mentioned in the bullet points differently to make this work as expected.

Let me know if this helps!

1 Like

Hi @DylanM and @Deep thanks you so much for you quick answers.
its just seems that something is not working when i’m intialize the q topic with a direct query dataset, i get this error:


I will ope a case to support and update about the resolution, but i was just curious if this functionality is possible.
Thanks

1 Like

Hello @Netser, my best guess is that it may have something to do with the size or complexity of the query you are running that is causing it to fail. It may be exceeding a timeout with your database that is causing it to fail in QuickSight.

If you still require assistance after reaching out to support, please post a new topic in the community and link to this question to provide relevant information. That will ensure you are at the top of the priority list for a response from one of our QuickSight experts. I will also mark this topic accordingly and archive it for our support team so they can view the issue you are facing.

Thank you!