commit | 198ffbca2eac15d542ea46ea863cebde1fa29138 | [log] [tgz] |
---|---|---|
author | Yingyi Bu <yingyi@couchbase.com> | Tue Jun 20 23:34:59 2017 -0700 |
committer | Yingyi Bu <buyingyi@gmail.com> | Wed Jun 21 08:23:01 2017 -0700 |
tree | 9ea25bfa2acaf31f6533e3ee55f89ff31964b1fd | |
parent | a7fa05bb014503609d1b6287fa08b0a296098088 [diff] |
[ASTERIXDB-1945][STO] Cleanup Buffer Cache API - user model changes: no - storage format changes: no - interface changes: yes INcApplicationContext - removed IFileMapProvider getFileMapManager(); to hide FileMapManager from other components; IStorageManager - IFileMapProvider getFileMapProvider(INCServiceContext ctx); to hide FileMapManager from other components; IFileHandle - added FileReference getFileReference(); to avoid unnecessary casts; IIOManager - public void deleteWorkspaceFiles() throws HyracksDataException; added throws; ILSMIndexFileManager - void createDirs() throws HyracksDataException; added throws; IInvertedIndex - added void purge() throws HyracksDataException; a. InvertedIndexes don't implement the ITreeIndex interface. b. when we deactivate a disk component, we need to purge it so the buffer cache doesn't go through each page. c. this need to be revisited, ASTERIXDB-1944 IFileMapManager - int registerFile(FileReference fileRef) throws HyracksDataException; return value added for future reference of the index file inside BufferCache or VirtualBufferCache; - FileReference unregisterFile(int fileId) throws HyracksDataException; return value added for future refernece of the file; IBufferCache - int createFile(FileReference fileRef) throws HyracksDataException; return value added for future reference of the index file inside BufferCache or VirtualBufferCache; - void deleteFile(int fileId) throws HyracksDataException; remove the dirty page flag since there's no dirty page; - int openFile(FileReference fileRef) throws HyracksDataException; return value added for future reference of the index file inside BufferCache or VirtualBufferCache; - added void deleteFile(FileReference file) throws HyracksDataException; we used to have this public methods in both BufferCache and VirtualBufferCache. Now we lifted it into the interface. AbstractLSMIndex - removed protected abstract void destroyMemoryComponent(ILSMMemoryComponent c) throws HyracksDataException; It is because turned out when we deactivate, we actually destroy them. However, because of the not well defined API, double destroy was okay and so we used to do double destroy. Details: This change fixes the buffer cache to follow the API such that: 1. createFile creates the file. 2. deleteFile deletes the file. 3. openFile opens the file. 4. closeFile closes the file. 5. creates existing file is not allowed. 6. deletes deleted file is not allowed. 7. open non existing file is not allowed. In addition, we hide the file map from all other components. Change-Id: I0a973c2adb2e7fdcbbf18c7b888af3de5f0acc74 Reviewed-on: https://asterix-gerrit.ics.uci.edu/1843 Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu> BAD: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Reviewed-by: Till Westmann <tillw@apache.org>
AsterixDB is a BDMS (Big Data Management System) with a rich feature set that sets it apart from other Big Data platforms. Its feature set makes it well-suited to modern needs such as web data warehousing and social data storage and analysis. AsterixDB has:
Data model
A semistructured NoSQL style data model (ADM) resulting from extending JSON with object database ideas
Query languages
Two expressive and declarative query languages (SQL++ and AQL) that support a broad range of queries and analysis over semistructured data
Scalability
A parallel runtime query execution engine, Apache Hyracks, that has been scale-tested on up to 1000+ cores and 500+ disks
Native storage
Partitioned LSM-based data storage and indexing to support efficient ingestion and management of semistructured data
External storage
Support for query access to externally stored data (e.g., data in HDFS) as well as to data stored natively by AsterixDB
Data types
A rich set of primitive data types, including spatial and temporal data in addition to integer, floating point, and textual data
Indexing
Secondary indexing options that include B+ trees, R trees, and inverted keyword (exact and fuzzy) index types
Transactions
Basic transactional (concurrency and recovery) capabilities akin to those of a NoSQL store
Learn more about AsterixDB at its website.
To build AsterixDB from source, you should have a platform with the following:
Instructions for building the master:
Checkout AsterixDB master:
$git clone https://github.com/apache/asterixdb.git
Build AsterixDB master:
$cd asterixdb $mvn clean package -DskipTests
Here are steps to get AsterixDB running on your local machine:
Start a single-machine AsterixDB instance:
$cd asterixdb/asterix-server/target/asterix-server-*-binary-assembly/ $./opt/local/bin/start-sample-cluster.sh
Good to go and run queries in your browser at:
http://localhost:19001
Read more documentations to learn the data model, query language, and how to create a cluster instance.