[
https://issues.apache.org/jira/browse/ASTERIXDB-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17758287#comment-17758287
]
ASF subversion and git services commented on ASTERIXDB-3250:
------------------------------------------------------------
Commit d399e65f7697d9be783e0ad36c2e9f3f67d6e640 in asterixdb's branch
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=d399e65f76 ]
[ASTERIXDB-3250][STO] Ensure writing indexes' empty files to S3
- user model changes: no
- storage format changes: no
- interface changes: yes
Details:
Empty indexes files are not written to S3.
This patch fixes this issue.
Interface changes:
- Add isEmpty() in ICloudBufferedWriter
Change-Id: I740c0d9e82bd0f933a37c4f68c3d95dc715cb46b
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17737
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Murtadha Al Hubail <[email protected]>
Tested-by: Jenkins <[email protected]>
> Ensure writing indexes' empty files to S3
> -----------------------------------------
>
> Key: ASTERIXDB-3250
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3250
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: STO - Storage
> Affects Versions: 0.9.9
> Reporter: Wail Y. Alkowaileet
> Assignee: Wail Y. Alkowaileet
> Priority: Major
> Fix For: 0.9.9
>
>
> When flushing empty components, empty files are not written to S3 (but
> written on local disk). When adding a new node (or removing a new node). The
> following error was observed:
> {noformat}
> Unequal number of trees and filters found in
> ..../storage/partition_64/Test/MyDataset/0/MyDataset {noformat}
> This happened as the boomfilter size was 0 bytes and not written to S3 during
> the flush operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
