[
https://issues.apache.org/jira/browse/ASTERIXDB-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325370#comment-16325370
]
ASF subversion and git services commented on ASTERIXDB-2184:
------------------------------------------------------------
Commit 73d9acaf764b4a6a18875b7a0ebe7f816cafdb15 in asterixdb's branch
refs/heads/master from [~luochen01]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=73d9aca ]
[ASTERIXDB-2184] Add Immutable DiskBTree
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Add a immutable DiskBTree to for LSM disk components. This DiskBTree
only supports two operations, i.e., search and bulkload. No concurrency
control is performed at all, since it's immutable.
- Change LSMBTree/InvertedIndex to use this DiskBTree
- Add a DiskBTree point search cursor to optimize point lookups
Change-Id: I8f2a9281478c4b8665589dc695769d0497af9961
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2193
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: abdullah alamoudi <[email protected]>
> Immutable disk version of BTree
> -------------------------------
>
> Key: ASTERIXDB-2184
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2184
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: HYR - Hyracks, STO - Storage
> Reporter: Chen Luo
> Assignee: Chen Luo
>
> BTree is currently heavily used in our codebase, e.g., for primary index,
> deleted keys, inverted index etc. Most of BTrees of a dataset are immutable,
> as they are from disk components. However, our current codebase only has one
> version of mutable BTree, which has quite a number of overhead on
> locking/concurrency control during normal operations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
