[
https://issues.apache.org/jira/browse/ASTERIXDB-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18000571#comment-18000571
]
ASF subversion and git services commented on ASTERIXDB-3601:
------------------------------------------------------------
Commit f2ef282cc6396f84a8870b6045a1394c617a36d7 in asterixdb's branch
refs/heads/master from Ritik Raj
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=f2ef282cc6 ]
[ASTERIXDB-3601][STO] Properly unpinning segment files
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
Properly unpinning the segment files, in case
of failure. Otherwise it might cause resource
leak.
Ext-ref: MB-66306
Change-Id: I1dec880871008fc6b9be6662df9fa034992858c9
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19990
Reviewed-by: Peeyush Gupta <[email protected]>
Integration-Tests: Jenkins <[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)
