Announcing the winners & finalists of the Dataiku Frontrunner Awards 2021! Read their inspiring stories

Why DSS import behaves differently than export for bundle which is already exists

arielma2304
Level 3
Why DSS import behaves differently than export for bundle which is already exists

Hi

Why DSS behave differently when user tries to export/import bundle zip file, which is already exists by its name?

In export, the UI throws "Bundle ### is already exists for project ####", and marks it with error.

But in import, it doesn't give any warning, just overwriting the bundle and changes the import info date. Why it doesn't have same exception as export, or at least some warning or other info.

0 Kudos
2 Replies
CoreyS
Community Manager
Community Manager

Hi, @arielma2304! Can you provide any further details on the thread to assist users in helping you find a solution (insert examples like DSS version etc.) Also, can you let us know if you’ve tried any fixes already?This should lead to a quicker response from the community.

Looking for more resources to help you use Dataiku effectively and upskill your knowledge? Check out these great resources: Dataiku Academy | Documentation | Knowledge Base

A reply answered your question? Mark as ‘Accepted Solution’ to help others like you!
0 Kudos
arielma2304
Level 3
Author

There is no real example, only trying to understand DSS behavior, and how come import just override the existing version if exists with no warning or exception (unlike export bundle action)

0 Kudos
Labels (1)
A banner prompting to get Dataiku DSS