You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Production datasets are never overwritable. But this means if there was any error in the code or other circumstance which interrupted registration of a production dataset, the next attempt must use a different name or version, which can be awkward for legacy datasets. Is this a rare enough occurrence (once we have stable, debugged code) that we just clean up by hand, deleting the unfinished entry?
Or do we allow, not only the data but also the entry to be overwritten if status=0? If the latter, do we need to add yet another argument to DatasetTable.register to request this behavior (but leave the default to not overwrite)?
The text was updated successfully, but these errors were encountered:
Production datasets are never overwritable. But this means if there was any error in the code or other circumstance which interrupted registration of a production dataset, the next attempt must use a different name or version, which can be awkward for legacy datasets. Is this a rare enough occurrence (once we have stable, debugged code) that we just clean up by hand, deleting the unfinished entry?
Or do we allow, not only the data but also the entry to be overwritten if status=0? If the latter, do we need to add yet another argument to DatasetTable.register to request this behavior (but leave the default to not overwrite)?
The text was updated successfully, but these errors were encountered: