| commit | bd728afe9be8c245e1de24936f8084ba3f537d05 | [log] [tgz] |
|---|---|---|
| author | Murtadha Hubail <mhubail@apache.org> | Thu Sep 20 20:56:01 2018 +0300 |
| committer | Murtadha Hubail <mhubail@apache.org> | Thu Sep 20 12:30:12 2018 -0700 |
| tree | 1a2839b5bd1eb6dd98ebeb67493111d52b5c114f | |
| parent | f7d634c35c7d8827da22feff78896e4fdb16c195 [diff] |
[NO ISSUE][REPL] Ensure Valid Component ID is Initialized On Replica Sync - user model changes: no - storage format changes: no - interface changes: yes Details: - Currently, the first time a replica is synchronized from master, the valid component id on each replicated index's initial checkpoint will be the initial value of a component id (-1). This value is fixed when the the replica receives a flushed component from the index. However, if the master fails before any component is flushed to a replica and that replica is promoted to master, it will start from an invalid component id. This change ensures that the initial checkpoint of replicated indexes is initialized to the maximum component id that appears on master. This will ensure that if the replica is promoted, it will at least start from a component that wasn't previously used on master. - Replace assertion of component ids validation by illegal state. Change-Id: I85395ad823a630725c4cab4bead1c61546dc61ae Reviewed-on: https://asterix-gerrit.ics.uci.edu/2973 Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Reviewed-by: Michael Blow <mblow@apache.org> Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
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 documentation to learn the data model, query language, and how to create a cluster instance.