A regular Spark/Yarn/Mesos or any other non-snappy cluster.
This is for the "old-way" of starting GemFireXD inside an existing Spark/Yarn cluster where cluster nodes themselves boot up as GemXD cluster.
The local mode which hosts the data, executor, driver (and optionally even jobserver) all in the same node.
Base parsing facilities for all SnappyData SQL parsers.
Main entry point for SnappyData extensions to Spark.
Main entry point for SnappyData extensions to Spark. A SnappyContext extends Spark's org.apache.spark.sql.SQLContext to work with Row and Column tables. Any DataFrame can be managed as SnappyData tables and any table can be accessed as a DataFrame. This integrates the SQLContext functionality with the Snappy store.
When running in the embedded mode (i.e. Spark executor collocated with Snappy data store), Applications typically submit Jobs to the Snappy-JobServer (provide link) and do not explicitly create a SnappyContext. A single shared context managed by SnappyData makes it possible to re-use Executors across client connections or applications.
SnappyContext uses a HiveMetaStore for catalog , which is persistent. This enables table metadata info recreated on driver restart.
User should use obtain reference to a SnappyContext instance as below val snc: SnappyContext = SnappyContext.getOrCreate(sparkContext)
Provide links to above descriptions
,document describing the Job server API
https://github.com/SnappyDataInc/snappydata#interacting-with-snappydata
https://github.com/SnappyDataInc/snappydata#step-1---start-the-snappydata-cluster
The regular snappy cluster where each node is both a Spark executor as well as GemFireXD data store.
The regular snappy cluster where each node is both a Spark executor as well as GemFireXD data store. There is a "lead node" which is the Spark driver that also hosts a job-server and GemFireXD accessor.
This is for the two cluster mode: one is the normal snappy cluster, and this one is a separate local/Spark/Yarn/Mesos cluster fetching data from the snappy cluster on demand that just remains like an external datastore.
Manages a time epoch and how to index into it.
Implicit conversions used by Snappy.