[
https://issues.apache.org/jira/browse/ASTERIXDB-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840186#comment-17840186
]
ASF subversion and git services commented on ASTERIXDB-3374:
------------------------------------------------------------
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]>
> Contextualize the BufferCache's pin, upin, and write operations
> ---------------------------------------------------------------
>
> Key: ASTERIXDB-3374
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3374
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: STO - Storage
> Affects Versions: 0.9.10
> Reporter: Wail Y. Alkowaileet
> Assignee: Wail Y. Alkowaileet
> Priority: Major
> Labels: triaged
> Fix For: 0.9.10
>
>
> The buffer cache's pin, unpin, and write operations are not exposed to the
> context of the overall on going operation. To some extent, the pin operation
> have some context (e.g., not incrementing a stat). Changing the buffer cache
> interface every time we want to incorporate contextual information is not
> sustainable. Instead, a user of the buffer cache should provide a context
> object that can hold all the necessary information of a given buffer cache
> operation (e.g., incrementing stats or processing the header when reading a
> page in a pin operation).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
