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

Support Conversion from ACID to EXTERNAL table #40

Open
dstreev opened this issue Jan 4, 2022 · 2 comments
Open

Support Conversion from ACID to EXTERNAL table #40

dstreev opened this issue Jan 4, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@dstreev
Copy link
Owner

dstreev commented Jan 4, 2022

Convert ACID table to EXTERNAL table.

Steps:

  • RENAME ACID table (<original_name>_to_delete)
  • CETAS from ACID table to 'name' that matches the original ACID table name.

Location of EXTERNAL table will go to default location base on Metastore configurations or the Database "LOCATION".

Cleanup of ACID table will be up to user.

@dstreev dstreev added the enhancement New feature or request label Jan 4, 2022
@dstreev dstreev self-assigned this Jan 4, 2022
@dstreev
Copy link
Owner Author

dstreev commented Jan 4, 2022

Translation to EXTERNAL table 'without' a STORED AS ... clause will default to 'textfiles'. So we need to pick up the serde on the source acid table and ensure the same for the external table.

@dstreev
Copy link
Owner Author

dstreev commented Jan 6, 2022

There are two facets to this:

  1. Convert 'inplace' ACID tables.
  2. Convert 'migrated' tables.

For the migrated option where the table is ACID on the LEFT, it should be converted to EXTERNAL/PURGE on the RIGHT. I see this second scenario being accomplished by adding a 'option' to -ma|-mao call 'TO_EXTERNAL'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant