Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When -dc option is used with -rdl, address conflicts when 2+ tables will occupy the same space #35

Open
dstreev opened this issue Apr 19, 2023 · 1 comment
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@dstreev
Copy link
Collaborator

dstreev commented Apr 19, 2023

If you have 2+ tables that have the same 'location' end path element, this will cause a conflict during the distcp operation.

@dstreev
Copy link
Collaborator Author

dstreev commented Apr 19, 2023

In this case, the tablename needs to be used to specify the target path in order for the -rdl location to sync up with the table.

dstreev added a commit to dstreev/hms-mirror that referenced this issue Apr 25, 2023
dstreev added a commit to dstreev/hms-mirror that referenced this issue May 10, 2023
- Previously Migrated
- Old Artifact Tables
- Validations when using -dc (table name mismatches to directory name)
- Table Status Rollups in Report
- Simplified options for -rdl, -dc, when using STORAGE_MIGRATION
- Support for STORAGE_MIGRATION in same Namespace (used to migrate/organize data to another directory)

Fixes Issue #35 cloudera-labs/hms-mirror#35 for STORAGE_MIGRATION strategy.
@dstreev dstreev self-assigned this May 12, 2023
@dstreev dstreev added bug Something isn't working enhancement New feature or request labels May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant