You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Wail Y. Alkowaileet (Jira)" <ji...@apache.org> on 2024/07/07 21:14:00 UTC
[jira] [Updated] (ASTERIXDB-3453) Incompressible pages are not written as full pages
[ https://issues.apache.org/jira/browse/ASTERIXDB-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wail Y. Alkowaileet updated ASTERIXDB-3453:
-------------------------------------------
Summary: Incompressible pages are not written as full pages (was: Incompressible pages are not entirely)
> Incompressible pages are not written as full pages
> --------------------------------------------------
>
> Key: ASTERIXDB-3453
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3453
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: STO - Storage
> Affects Versions: 0.9.10
> Reporter: Wail Y. Alkowaileet
> Assignee: Wail Y. Alkowaileet
> Priority: Blocker
> Fix For: 0.9.10
>
>
> Incompressible pages are not written entirely. Although this won't impose an issue in a non-cloud deployment, but in a cloud deployment, this would mess up the file. The reason is that, in a cloud deployment, writes are "append-only". That means, writes' offsets cannot be used to determine the write position.
> Thus, if an incompressible page is written and the size of the page is smaller than a full page, this could write this page's content at the wrong position in the cloud storage – leading to have more bytes in local files than in the cloud.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)