[
https://issues.apache.org/jira/browse/ASTERIXDB-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406863#comment-15406863
]
ASF subversion and git services commented on ASTERIXDB-1479:
------------------------------------------------------------
Commit ca3b9b28f681382b88781d8c62aa1e0fd53a2659 in asterixdb's branch
refs/heads/master from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=ca3b9b2 ]
ASTERIXDB-1479: Change storage valid int and add explicit version
This change will stop old versions from possibly corrupting data written
by newer versions of Hyracks. It also adds an explicit version to the
tree metadata that must match the version at runtime.
Change-Id: I888ff0eacf5b3cb6ad7ec002c74f113c6ffcd496
Reviewed-on: https://asterix-gerrit.ics.uci.edu/919
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
> Explicit Storage Versioning
> ---------------------------
>
> Key: ASTERIXDB-1479
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1479
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: Hyracks, Storage
> Reporter: Ian Maxon
> Assignee: Ian Maxon
>
> Right now storage versioning is largely implied, there's no exact indication
> of when an index structure has changed from one revision to the next. We
> should have a marker in the metadata page that explicitly is changed along
> with any sort of backwards-incompatible storage change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
