ajantha-bhat commented on PR #225: URL: https://github.com/apache/polaris-tools/pull/225#issuecomment-4437968888
> So this may not be 100% valid as people can be using namespace as tenant/workflow separator for a given writer. Assuming one app is writing to 1k tables and each of the table has their own namespace, the purposed solution may not be useable in this case. I can understand that namespace by namespace migration is not possible in this case. What about retrying again for failed tables like mentioned below? > Also, I would like to add that, if only 'K' tables migrated out of 'N' and you need to migrate remaining. You can call same cli for all 'N' tables. It will skip migration for registered tables (with the error that table already exist). But other tables will still be migrated in that process. It won't pause migration of other tables if current table already exists. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
