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

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

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

[MULTIPLE ISSUES][STO] Storage code clean ups

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

Details:
- ASTERIXDB-3360: Honor limit when writing
  compressed pages
- ASTERIXDB-3374: Clean up contexts java packages
- ASTERIXDB-3375: Rename ContextUtil
  to BufferCacheCloudReadContextUtil

Change-Id: Ice1ade6d00db8b6383d22e4f98314fc99df8a844
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18247
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