[
https://issues.apache.org/jira/browse/ASTERIXDB-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15635534#comment-15635534
]
ASF subversion and git services commented on ASTERIXDB-1725:
------------------------------------------------------------
Commit 15e49e0db5a40d68e6e6dbf60138d6ec61fd15b0 in asterixdb's branch
refs/heads/master from [~imaxon]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=15e49e0 ]
Fix for ASTERIXDB-1725
This is tricky, the best method I could think to fix this involved simply
putting the root page number in the metadata page rather than trying to
calculate it somehow going backwards from the end of the file.
I also fixed a bug discovered by Mike B where getLSNOffset was not
taking into consideration page header sizes.
Change-Id: I9f21e96ab045d331e4fc1c77b5c73b975e6260fa
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1331
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mb...@apache.org>
> Root page location calculation does not account for multipages
> --------------------------------------------------------------
>
> Key: ASTERIXDB-1725
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1725
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Ian Maxon
> Assignee: Ian Maxon
>
> The root page calculation is based on a fixed number of pages. This is
> usually fine, unless the root page happens to be a leaf page. In this case it
> may consist of any number of pages due to large object storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
