[
https://issues.apache.org/jira/browse/ASTERIXDB-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875696#comment-17875696
]
ASF subversion and git services commented on ASTERIXDB-3484:
------------------------------------------------------------
Commit 58913f683a2e0876aaa54e903babfd4e26166ad8 in asterixdb's branch
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=58913f683a ]
[ASTERIXDB-3484] Support storing large values in metadata pages
- user model changes: no
- storage format changes: yes
- interface changes: yes
Details:
Add the support to store large key-value pairs
in the component's metadata page
Ext-ref: MB-62875
Change-Id: Ie3f5cb6820b98ef78841c49b13ae33436c71a99a
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18633
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Wail Alkowaileet <[email protected]>
Reviewed-by: Murtadha Hubail <[email protected]>
> Support putting large values in the on-disk component metadata page
> -------------------------------------------------------------------
>
> Key: ASTERIXDB-3484
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3484
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: STO - Storage
> Affects Versions: 0.9.10
> Reporter: Wail Y. Alkowaileet
> Assignee: Wail Y. Alkowaileet
> Priority: Major
> Labels: triaged
> Fix For: 0.9.10
>
>
> In columnar dataset, the schema can be greater than on-disk pages. In such
> scenario, we fail to flush. We should be able to grow the metadata page to
> occupy more than a single page.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
