[NO-ISSUE][IDX] Adding support for array-indexes.

- user model changes: yes
- storage format changes: no
- interface changes: no

details:
- Users can now create indexes on array-valued fields, of the general
form "CREATE INDEX ... ON Dataset (UNNEST arrayField SELECT atomicField)".
- Metadata tuples for indexes has been updated to support a list
of "complex search keys", as well as multiple types for one key.
In the presence of a complex search key, all keys (even simple SKs)
will be placed inside this new list.
- Queries involving membership, UNNESTs, quantification
(existential and partially supported universal) will utilize an
applicable array index. Users must set the compiler option "arrayindex"
to true to enable this.
- SIDX maintenance operations now allow the use of nested plans, which
the aforementioned maintenance op will operate on from the end of the
nested plan(s).
- Indexes are now classified by different types in metadata, with a new
"array" index type.

Change-Id: Id0e9eee940cc94819e169a74ed180387b7a3093b
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/7684
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Dmitry Lychagin <dmitry.lychagin@couchbase.com>
698 files changed
tree: 303c83c5bb8208a1510fbb44e0b5ea1cc8357a46
  1. .gitattributes
  2. .gitignore
  3. README.md
  4. asterixdb/
  5. build.xml
  6. hyracks-fullstack/
  7. pom.xml
README.md

What is AsterixDB?

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.

Build from source

To build AsterixDB from source, you should have a platform with the following:

  • A Unix-ish environment (Linux, OS X, will all do).
  • git
  • Maven 3.3.9 or newer.
  • JDK 11 or newer.
  • Python 3.6+ with pip and venv

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
    

Run the build on your machine

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.

Documentation

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.

Community support