You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/09/01 14:24:00 UTC
[jira] [Updated] (HADOOP-14335) Improve DynamoDB schema update
story
[ https://issues.apache.org/jira/browse/HADOOP-14335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran updated HADOOP-14335:
------------------------------------
Parent Issue: HADOOP-14825 (was: HADOOP-13345)
> 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
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org