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

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

Commit aa3167d2ea534b55ab9226da25a7be7d8d82fd81 in asterixdb's branch 
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=aa3167d2ea ]

[ASTERIXDB-3463] Revert ASTERIXDB-3360

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

Details:
Revert ASTERIXDB-3360 as it has caused several
issues. This can be revesited in the future and
can be eneabled again.

Ext-ref: MB-62736
Change-Id: I24b4e7bcd5790b04d0db7b3c2796ca09f0206040
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18493
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Wail Alkowaileet <[email protected]>
Reviewed-by: Murtadha Hubail <[email protected]>


> Honor ByteBuffer position and limit when writing compressed B-Tree pages
> ------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-3360
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3360
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: STO - Storage
>    Affects Versions: 0.9.9
>            Reporter: Wail Y. Alkowaileet
>            Assignee: Wail Y. Alkowaileet
>            Priority: Major
>              Labels: triaged
>             Fix For: 0.9.9
>
>
> Compressed page writer always clear the to-be-written ByteBuffer position and 
> limit to be the entire buffer. This could be fine for writing pages in row 
> format. However, in columnar format, this might incur compressing and writing 
> unrelated data (as the ByteBuffer may contain data from a previous write). 
> Instead of clearing the ByteBuffer position and limit at the compressed page 
> writer, it should be done during the call to BufferCache#confiscatePage(), 
> which is the case currently. The compressed page writer, however, should not 
> re-clear whatever limit is provided.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to