[
https://issues.apache.org/jira/browse/ASTERIXDB-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003882#comment-18003882
]
ASF subversion and git services commented on ASTERIXDB-3601:
------------------------------------------------------------
Commit 07cc6b8b750cec349a4cb52c8f9b89cfda163bba in asterixdb's branch
refs/heads/master from Ritik Raj
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=07cc6b8b75 ]
[ASTERIXDB-3601][STO] Fixed calculation issues
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
1. isFull calculation
2. sparse column columnToIndexCache reset
3. bounding the offsetColumnIndexPairs per leaf
Ext-ref: MB-66306
Change-Id: I796b74355eca845f006abb5b45789a5136ba8c84
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/20013
Reviewed-by: Peeyush Gupta <[email protected]>
Tested-by: Ritik Raj <[email protected]>
> 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)
