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

Possible to have 'alternative' mappings for columns for legacy data? #206

Open
djhworld opened this issue Apr 10, 2018 · 0 comments
Open

Comments

@djhworld
Copy link

Say I have the following table

window string

and at some point I want to rename window because the process that it outputting data to my data lake has started calling this column timewindow

I can rename the column in HIVE to be timewindow but now all the 'legacy' data that we've been ingesting in the data lake before the change still has the column window

Is there a mapping/method/way in the SerDe of saying that on read any data with the column name window should be mapped to timewindow?

Or do I need to do a batch post process of all the data to correct it?

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

No branches or pull requests

1 participant