| commit | 282a79198af022563c3d93c51e0d9a052e140ab2 | [log] [tgz] |
|---|---|---|
| author | Abdullah Alamoudi <bamousaa@gmail.com> | Thu Mar 15 22:52:53 2018 -0700 |
| committer | abdullah alamoudi <bamousaa@gmail.com> | Fri Mar 16 10:08:33 2018 -0700 |
| tree | 46663ea223ad2de5abe448635ec35114dfb975a5 | |
| parent | 8798c324aa7e99a92356df2a8567be35fcbd9efe [diff] |
[NO ISSUE][RT] Fix wait for IO operations - user model changes: no - storage format changes: no - interface changes: no Details: - Some operations such as close dataset, delete components, and drop index need to wait for IO operations. - Before this change, the wait for IO operation would just check the count of IO operations on the dataset info. This is not enough as a flush might have started by writing the flush log to the log tail but only on the flush of that log, we trigger the flush operation and the count of IO operation increases. - To address this problem, we write a wait log before we check the IO operation count ensuring that any flush logs in the log tail have been flushed and counts incremented. Change-Id: Ibfa883410cd24e0af54732f7ea6f1b4eb2184e8e Reviewed-on: https://asterix-gerrit.ics.uci.edu/2495 Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Reviewed-by: Murtadha Hubail <mhubail@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.