[ 
https://issues.apache.org/jira/browse/ASTERIXDB-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014170#comment-18014170
 ] 

ASF subversion and git services commented on ASTERIXDB-3601:
------------------------------------------------------------

Commit acb36e62fccae5602f7e6fa343d42d37c419a626 in asterixdb's branch 
refs/heads/master from Ritik Raj
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=acb36e62fc ]

[ASTERIXDB-3601][STO] Remove unnecessary present column calculation for flush

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
1. present column calculation not needed during flush.
2. added log line for counting pages flushed in dense or sparse format.

Ext-ref: MB-66306
Change-Id: I70e3a7cddd1c744b651ff69cb0122b22ae60e0f1
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/20106
Integration-Tests: Jenkins <[email protected]>
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)

Reply via email to