| commit | 98b9d603e8531139a4668af48092e9c961ee41fb | [log] [tgz] |
|---|---|---|
| author | luochen01 <cluo8@uci.edu> | Wed Nov 22 18:25:22 2017 -0800 |
| committer | abdullah alamoudi <bamousaa@gmail.com> | Thu Nov 23 00:55:26 2017 -0800 |
| tree | aef19af75341341a8dbba248b4f20843ba4c4719 | |
| parent | 4dad5dfa87bd7e353f60a7889478a2966daa43ef [diff] |
[ASTERIXDB-2161] Fix component id manage lifecycle - user model changes: no - storage format changes: no - interface changes: yes. The interface of LMSIOOperationCallback is changed Details: - The current way of management component ids is not correct, in presence of that multiple partitions sharing the same primary op tracker. It's possible when a partition is empty/being flushed, the next flush is scheduled by another partition, which will disturb the partition. This patch fixes this by using the same logic of maintaining flushed LSNs to maintain component id. - Extend recycle memory component interface to indicate whether it switches the new component or not. - Also fixes [ASTERIXDB-2168] to ensure we do not miss latest flushed LSNs by advancing io callback before finishing flush Change-Id: Ifc35184c4d431db9af71cab302439e165ee55f54 Reviewed-on: https://asterix-gerrit.ics.uci.edu/2153 Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Reviewed-by: abdullah alamoudi <bamousaa@gmail.com>
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.