[
https://issues.apache.org/jira/browse/HADOOP-14335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522788#comment-16522788
]
Steve Loughran commented on HADOOP-14335:
-----------------------------------------
bq. no ASF code has shipped the schema, so in theory we could be guilt-free
about changing things.-
update: we have
> 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: 3.0.0-beta1
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
