[
https://issues.apache.org/jira/browse/HADOOP-14335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15977747#comment-15977747
]
Sean Mackrory commented on HADOOP-14335:
----------------------------------------
This is definitely the case for HADOOP-13760, and may be the case for future
changes: we can fairly easily make things work on existing tables that don't
have new columns, etc. So I'm thinking we should separate the notion of
"current schema version" to be used for new tables, and "minimum schema
version" to be used when connecting to existing tables. A new version can keep
using existing tables if they're there, and we provided a CLI to bump up the
schema version and make any other required changes when the upgrade is
complete. That should work for the HADOOP-13760 case, but I'd like to come up
with likely schema changes we might make further in the future and consider
those. Going to think about this for a while...
> Improve DynamoDB schema update story
> ------------------------------------
>
> Key: HADOOP-14335
> URL: https://issues.apache.org/jira/browse/HADOOP-14335
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
>
> On HADOOP-13760 I'm realizing that changes to the DynamoDB schema aren't
> great to deal with. Currently a build of Hadoop is hard-coded to a specific
> schema version. So if you upgrade from one to the next you have to upgrade
> everything (and then update the version in the table - which we don't have a
> tool or document for) before you can keep using S3Guard. We could possibly
> also make the definition of compatibility a bit more flexible, but it's going
> to be very tough to do that without knowing what kind of future schema
> changes we might want ahead of time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
