ElasticSearch Dot-two Branch

[ja...@apps4u.com.au]

Hi I have a quick question about the two-dot branch , it now has a dependancy on Elastic Search and from what I can see its used in test code. From what Ive ready about Elasticsearch its a database and REST engine and usergrid uses Cassandra for its data storage and has a REST api. So what is Elasticsearch being used for and why dose the AWS cloud formations package create Elasticsearch instances ??? 
Is it a replacement for Cassandra ??

 I posted this to user mailing list sorry for doing it twice not sure which list to ask questions on.

Re: ElasticSearch Dot-two Branch

[ja...@apps4u.com.au]

Thanks That make sense. I thought it was something like that.

Thanks agin.

September 9 2014 9:37 PM, "Dave" <sn...@gmail.com> wrote: 
> On Tue, Sep 9, 2014 at 12:44 AM, <ja...@apps4u.com.au> wrote:
> 
>> Hi I have a quick question about the two-dot branch , it now has a
>> dependancy on Elastic Search and from what I can see its used in test code.
>> From what Ive ready about Elasticsearch its a database and REST engine and
>> usergrid uses Cassandra for its data storage and has a REST api. So what is
>> Elasticsearch being used for and why dose the AWS cloud formations package
>> create Elasticsearch instances ???
>> Is it a replacement for Cassandra ??
> 
> What's new in the two-dot-o branch is a new module called Core Persistence
> that uses a Multi-version Concurrency Control (MVCC) approach instead of
> locking (which we found to be problematic in production). Core Persistence
> uses Cassandra for collections of entities and for graph connections
> between entities. It uses ElasticSearch for indexing and search of entities
> within collections and among connections.
> 
> This document (needs some update) explains some of the Core Persistence
> design:
> https://docs.google.com/document/d/1P0FJx4Q68IYaNsyEjD9XQQ_if6UK35UTEG9SkY_y2F4/edit?usp=sharing
> 
> In the two-dot-o branch, Usergrid still uses the same EntityManager
> interface for collections, graph and indexing but there is now a new Core
> Persistence-based implementation of that interface. The new EntityManager
> implementation is code-complete and we're working on getting it to pass
> 100% of the stack's roughly 900 JUnit tests (we're down to about 5 failing
> tests today).
> 
> - Dave

Re: ElasticSearch Dot-two Branch

[Dave <sn...@gmail.com>]

On Tue, Sep 9, 2014 at 12:44 AM, <ja...@apps4u.com.au> wrote:

> Hi I have a quick question about the two-dot branch , it now has a
> dependancy on Elastic Search and from what I can see its used in test code.
> From what Ive ready about Elasticsearch its a database and REST engine and
> usergrid uses Cassandra for its data storage and has a REST api. So what is
> Elasticsearch being used for and why dose the AWS cloud formations package
> create Elasticsearch instances ???
> Is it a replacement for Cassandra ??
>

What's new in the two-dot-o branch is a new module called Core Persistence
that uses a Multi-version Concurrency Control (MVCC) approach instead of
locking (which we found to be problematic in production). Core Persistence
uses Cassandra for collections of entities and for graph connections
between entities. It uses ElasticSearch for indexing and search of entities
within collections and among connections.

This document (needs some update) explains some of the Core Persistence
design:
https://docs.google.com/document/d/1P0FJx4Q68IYaNsyEjD9XQQ_if6UK35UTEG9SkY_y2F4/edit?usp=sharing

In the two-dot-o branch, Usergrid still uses the same EntityManager
interface for collections, graph and indexing but there is now a new Core
Persistence-based implementation of that interface. The new EntityManager
implementation is code-complete and we're working on getting it to pass
100% of the stack's roughly 900 JUnit tests (we're down to about 5 failing
tests today).

- Dave