| commit | fd2c99e97664c8c098eabd603e209027351abdb8 | [log] [tgz] |
|---|---|---|
| author | Ali Alsuliman <ali.al.solaiman@gmail.com> | Wed Aug 21 18:07:44 2024 -0700 |
| committer | Ali Alsuliman <ali.al.solaiman@gmail.com> | Fri Aug 23 17:55:46 2024 +0000 |
| tree | 4e9edde6f22154ec14a5dc0d9e744750358ef3ed | |
| parent | 205de9112a0142908c19a18d07e9ae11cac6d482 [diff] |
[ASTERIXDB-3472][HYR] Use CleanupUtils.fail/close in ProbeAndJoinActivityNode - user model changes: no - storage format changes: no - interface changes: no Details: In the close() of the hash-join ProbeAndJoinActivityNode, use CleanupUtils.fail()/close() when closing the next writer. The reason is if all the build partitions are spilled, pushing the frames from the ProbeAndJoinActivityNode to the next writer will happen in the close(), not nextFrame(). In such cases, any exception that happens in the next writer is caught in ProbeAndJoinActivityNode.close(). After that, it calls fail()/close() on the next writer. Those fail()/close() should be done using CleanupUtils so that the original caught exception is not lost. Ext-ref: MB-62949 Change-Id: I1cdee5ed457b72b4f6b3731fba3542898dec9bf3 Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/18707 Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu> Reviewed-by: Michael Blow <mblow@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
An expressive and declarative query language (SQL++ that supports 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/apache-asterixdb-*-SNAPSHOT $./opt/local/bin/start-sample-cluster.sh
Good to go and run queries in your browser at:
http://localhost:19006
Read more documentation to learn the data model, query language, and how to create a cluster instance.
To generate the documentation, run asterix-doc with the generate.rr profile in maven, e.g mvn -Pgenerate.rr ... Be sure to run mvn package beforehand or run mvn site in asterix-lang-sqlpp to generate some resources that are used in the documentation that are generated directly from the grammar.