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
As of now the only way to drop tables on the RIGHT cluster that not exist on the LEFT is to use they --sync option, but using it if we're converting a legacy managed table to an external one it does not set the PURGE option, potentially keeping unwanted data on the RIGHT cluster.
The text was updated successfully, but these errors were encountered:
Adding the purge back in this scenario might cause issues with a schema update, since that process drops and recreates the table. If the purge flag were set, we'd inadvertently remove the data.
What if we built an extra 'post' run file that issued hdfs dfs rm -r -f commands when a RIGHT side schema meets this 'drop' scenario?
As of now the only way to drop tables on the RIGHT cluster that not exist on the LEFT is to use they --sync option, but using it if we're converting a legacy managed table to an external one it does not set the PURGE option, potentially keeping unwanted data on the RIGHT cluster.
The text was updated successfully, but these errors were encountered: