[
https://issues.apache.org/jira/browse/ASTERIXDB-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014172#comment-18014172
]
ASF subversion and git services commented on ASTERIXDB-3601:
------------------------------------------------------------
Commit ce8031ffae373d80c86a35c1905e76c6c892cffc in asterixdb's branch
refs/heads/master from Ritik Raj
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=ce8031ffae ]
[ASTERIXDB-3601][STO] Fix calculation of presentColumns
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
During the merge, there was an issue setting
up the columnIndexes from the additional pageSegments,
which caused the extra columns to be ignored
Ext-ref: MB-67741
Change-Id: Id43277dc678ab6578c27d3cf114063acbcc849fb
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/20127
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: Peeyush Gupta <peeyush.gu...@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)
