[
https://issues.apache.org/jira/browse/ASTERIXDB-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003883#comment-18003883
]
ASF subversion and git services commented on ASTERIXDB-3601:
------------------------------------------------------------
Commit 4dc60abf2e4b3064454bc30fadca2e23de0c4edd in asterixdb's branch
refs/heads/master from Ritik Raj
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=4dc60abf2e ]
[ASTERIXDB-3601][STO] Unpinning the not required segmentPages
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
In order to calculate the length/size of the columns,
all the columns' offset is to be known, hence need to
pin all the segment pages, irrespective of being asked
by the query. But, after calculating the length of columns
the segments are unpinned and the buffer is cleared.
Ext-ref: MB-66306
Change-Id: I915031e39a17ac853a24d78809b7742e2ea60163
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/20016
Reviewed-by: Peeyush Gupta <peeyush.gu...@couchbase.com>
Tested-by: Ritik Raj <ritik....@couchbase.com>
> Support unlimited number of columns in columnar storage
> -------------------------------------------------------
>
> Key: ASTERIXDB-3601
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3601
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: STO - Storage
> Affects Versions: 0.9.10
> Reporter: Ritik Raj
> Assignee: Ritik Raj
> Priority: Major
> Labels: triaged
> Fix For: 0.9.10
>
>
> There may be cases where the number of columns is too large to fit within the
> standard pageSize. This can prevent a tuple from being added to the dataset
> and may also trigger a flush failure, leading to repeated I/O retries that
> ultimately fail.
> To mitigate this issue, we can expand pageZero to accommodate the necessary
> metadata.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
