Skip to content
SnappyData - The Spark Database. Stream, Transact, Analyze, Predict in one cluster
Branch: master
Clone or download
ashetkar * Versioning related changes for upcoming 1.1.0 release. (#1291)
* Versioning related changes for upcoming 1.1.0 release.
Latest commit 8f2a173 Apr 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
cluster
codeStyles Add IDEA code style settings for versions >= 2017.3 Oct 21, 2018
compatibilityTests
core
docs Corrected broken links. (#1274) Mar 20, 2019
dtests fix an occasional exception string match failure Apr 15, 2019
dunit Update gradle to version 5.0 Dec 28, 2018
encoders
examples streaming example code cleanup (#1283) Apr 8, 2019
gradle/wrapper Update gradle to version 5.0 Dec 28, 2018
jdbc Branch 1.0.2.2 (#1231) Feb 13, 2019
launcher Slight modification in the replace script. Nov 4, 2018
python Slight modification in the replace script. Nov 4, 2018
release * Versioning related changes for upcoming 1.1.0 release. (#1291) Apr 19, 2019
spark @ 4f01cd4 * Versioning related changes for upcoming 1.1.0 release. (#1291) Apr 19, 2019
spark-jobserver @ 9f180fe sync with spark-jobserver Mar 29, 2019
store @ 9133ebf
tests added bug test to reproduce issue SNAP-2718. Could not reproduce the … Feb 4, 2019
.gitignore Added some more directories to git ignore and vm_* directories as well. Apr 27, 2018
.gitmodules
LICENSE Slight modification in the replace script. Nov 4, 2018
NOTICE Update gradle to version 5.0 Dec 28, 2018
README.md
ReleaseNotes.txt * Version 1.0.2.1 Nov 2, 2018
build.gradle * Versioning related changes for upcoming 1.1.0 release. (#1291) Apr 19, 2019
codeStyleSettings.xml [SNAP-1743] Compress column batches when storing to disk or sending o… Dec 15, 2017
gradle.properties [SNAP-2818] trim the JOB_DESCRIPTION property in Spark jobs (#1227) Dec 28, 2018
gradlew
gradlew.bat Docv1.0.2.1 temp (#1236) Jan 10, 2019
mkdocs.yml
publish-site.sh Added an echo statement to remind the user to run gradle docs task. Sep 10, 2018
scalastyle-config.xml Slight modification in the replace script. Nov 4, 2018
settings.gradle

README.md

SnappyData fuses Apache Spark with an in-memory database to deliver a data engine capable of processing streams, transactions and interactive analytics in a single cluster.

The Challenge with Spark and Remote Data Sources

Apache Spark is a general purpose parallel computational engine for analytics at scale. At its core, it has a batch design center and is capable of working with disparate data sources. While this provides rich unified access to data, this can also be quite inefficient and expensive. Analytic processing requires massive data sets to be repeatedly copied and data to be reformatted to suit Spark. In many cases, it ultimately fails to deliver the promise of interactive analytic performance. For instance, each time an aggregation is run on a large Cassandra table, it necessitates streaming the entire table into Spark to do the aggregation. Caching within Spark is immutable and results in stale insight.

The SnappyData Approach

At SnappyData, we take a very different approach. SnappyData fuses a low latency, highly available in-memory transactional database (GemFireXD) into Spark with shared memory management and optimizations. Data in the highly available in-memory store is laid out using the same columnar format as Spark (Tungsten). All query engine operators are significantly more optimized through better vectorization and code generation.
The net effect is, an order of magnitude performance improvement when compared to native Spark caching, and more than two orders of magnitude better Spark performance when working with external data sources.

Essentially, we turn Spark into an in-memory operational database capable of transactions, point reads, writes, working with Streams (Spark) and running analytic SQL queries. Or, it is an in-memory scale out Hybrid Database that can execute Spark code, SQL or even Objects.

If you are already using Spark, experience 20x speed up for your query performance. Try out this test.

Snappy Architecture

SnappyData Architecture

Getting Started

We provide multiple options to get going with SnappyData. The easiest option is, if you are already using Spark 2.1.1. You can simply get started by adding SnappyData as a package dependency. You can find more information on options for running SnappyData here.

Downloading and Installing SnappyData

You can download and install the latest version of SnappyData from the SnappyData Download Page. Refer to the documentation for installation steps.

If you would like to build SnappyData from source, refer to the documentation on building from source.

SnappyData in 5 Minutes!

Refer to the 5 minutes guide which is intended for both first time and experienced SnappyData users. It provides you with references and common examples to help you get started quickly!

Documentation

To understand SnappyData and its features refer to the documentation.

Community Support

We monitor channels listed below for comments/questions.

Stackoverflow Stackoverflow SlackSlack Gitter Gitter Mailing List Mailing List Reddit Reddit JIRA JIRA

Link with SnappyData Distribution

Using Maven Dependency

SnappyData artifacts are hosted in Maven Central. You can add a Maven dependency with the following coordinates:

groupId: io.snappydata
artifactId: snappydata-core_2.11
version: 1.0.2.1

groupId: io.snappydata
artifactId: snappydata-cluster_2.11
version: 1.0.2.1

Using SBT Dependency

If you are using SBT, add this line to your build.sbt for core SnappyData artifacts:

libraryDependencies += "io.snappydata" % "snappydata-core_2.11" % "1.0.2.1"

For additions related to SnappyData cluster, use:

libraryDependencies += "io.snappydata" % "snappydata-cluster_2.11" % "1.0.2.1"

You can find more specific SnappyData artifacts here

Note: If your project fails when resolving the above dependency (that is, it fails to download javax.ws.rs#javax.ws.rs-api;2.1), it may be due an issue with its pom file.
As a workaround, you can add the below code to your build.sbt:

val workaround = {
  sys.props += "packaging.type" -> "jar"
  ()
}

For more details, refer https://github.com/sbt/sbt/issues/3618.

Ad Analytics using SnappyData

Here is a stream + Transactions + Analytics use case example to illustrate the SQL as well as the Spark programming approaches in SnappyData - Ad Analytics code example. Here is a screencast that showcases many useful features of SnappyData. The example also goes through a benchmark comparing SnappyData to a Hybrid in-memory database and Cassandra.

Contributing to SnappyData

If you are interested in contributing, please visit the community page for ways in which you can help.

You can’t perform that action at this time.