[
https://issues.apache.org/jira/browse/ASTERIXDB-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18003554#comment-18003554
]
ASF subversion and git services commented on ASTERIXDB-3601:
------------------------------------------------------------
Commit c324495e255e9de9c02363a3405dd60063a8f916 in asterixdb's branch
refs/heads/master from Ritik Raj
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=c324495e25 ]
[ASTERIXDB-3601][STO] Removing warn log
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
In ColumnRanges, there can be case
where columnOffset is zero, if the columns
are present in the pageZerosegment which is
not being projected.
Ext-ref: MB-66306
Change-Id: Iee50eb4d305fa6d2bab0cbc33f3b859e4f316605
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/20008
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Peeyush Gupta <[email protected]>
Tested-by: Jenkins <[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)
