Hi team, I created a dataset with the new UI but the option for incremental refreshes doesn’t appear. Is this a bug or am I doing something wrong?
Hi @DannyV,
Hope everything is well! Although this is scenario is a little different, I would check out this previous thread, as if the scenario in there applies to you, that could be why the incremental refresh option is not popping up. If that does not help, please feel free to elaborate on your use case a little further to see if any issues are present there. Let me know if this helps!
Hi @WLS-Luis , I really appreciate the quick response. I think the problem is different (I’ve attached images).
I’m creating the exact same simple dataset (select * from table) using both the new and old UI.
The first images are of the dataset created with the new UI, and as you can see, the Incremental refresh option isn’t available.
The last images are the exact same select * from table but using the old UI, and here the Incremental refresh option does appear.
NEW INTERFACE
OLD INTERFACE
Hi @DannyV, incremental refresh is not currently supported in the new data preparation experience. While Amazon Quick plans to implement these features in the future with the new experience, you can view the current limitations in the documentation here:
In the meantime, for use cases that require these features, you can choose to switch to the legacy experience.
3 Likes
Hello,
I’m halfway through developing a project and I need incremental updates. How can we proceed?
I’m having the same problem mentioned above; every dataset created in the new interface doesn’t offer the “incremental scheduling” option…
Hi @thais,
If you need to use incremental refresh, you will need to use the legacy data preparation experience for those datasets. When you create new datasets (before they are saved and published), there is a button below publish to “Switch back to legacy experience”. Once the dataset has been published, there will not be an option to go back to the legacy experience, so this selection must be done when first creating the dataset.
Is there any other drawback of using Legacy experience. @Jackson_Dowden @WLS-Luis
Hi @Tanu_13,
To my knowledge, I don’t think there are any other huge discrepancies between both of the experiences. If you do run into anything though, I would definitely look into Jackson’s link above so that you can look at the differences between legacy and new. If you run into any specific issues when trying to switch between both or using one experience, please definitely feel free to create a new topic!
Thank you!