disabling nodetype index

2017-03-29 Thread Alex Benenson
Hi all Is it safe to disable nodetype index? We do not have any custom queries that needed it. Is it used for any oak internals? Assuming it is safe to disable, can I follow that by deleting every node under /oak:index/nodetype/:index ? db.nodes.remove({_id: /^\d+:\/oak:index\/nodetype\/:index/}

Re: problem on oak jcr sql2 query

2017-03-29 Thread Davide Giannella
On 28/03/2017 12:34, Tommaso Teofili wrote: > It might also be useful to enable debug logging > for org.apache.jackrabbit.oak.query, +1 and provide the output somewhere on the web for easy reading. For example gist.github.com works perfectly for this. Davide

Re: Improving Oak Documentation

2017-03-29 Thread Konrad Windszus
I linked some related JIRA issues to [2]. They mostly refer to lack of OSGi configuration description (especially in the field of blob stores). Konrad > On 29 Mar 2017, at 11:55, Chetan Mehrotra wrote: > > Hi, > > As a user of Oak or someone exploring Oak you might find certain > aspects which

Re: Cassandra as NodeStore

2017-03-29 Thread Ian Boston
Hi Juanjo, For Cassandra to work as a DocumentStore for Oak it needs to be configured with a Quorum high enough to ensure that all writes are sequentially eventually consistent. That might kill Cassandras write performance. RDB backends have this behaviour because they are single instance. MongoDB

Improving Oak Documentation

2017-03-29 Thread Chetan Mehrotra
Hi, As a user of Oak or someone exploring Oak you might find certain aspects which are not documented properly in our Oak documentation [1]. To improve that we have created OAK-5998 [2] Kindly add via comments the topics which you think need more clarity along with some details on what is missing

Re: oak-benchmarks and oak-run

2017-03-29 Thread Davide Giannella
On 24/03/2017 16:24, Davide Giannella wrote: > I've attached in the ticket the patch for review. > > https://issues.apache.org/jira/browse/OAK-3342 > > I don't really know about backports though. The fact that in the past we > split into separate commands will mean that if backporting anything from

Re: Cassandra as NodeStore

2017-03-29 Thread Chetan Mehrotra
Adding to that below are few features I think any new store would have to support 1. Sorted primary key access - For now required to find children of any parent path 2. secondary indexes apart from _id field 3. compare-and-set (CAS) operations for sub fields Chetan Mehrotra On Wed, Mar 29, 2017

Re: Cassandra as NodeStore

2017-03-29 Thread Marcel Reutegger
Hi Juanjo, I don't know Cassandra that well, but I'd say this is feasible. Though, you would probably not implement a NodeStore but a backend for the DocumentNodeStore. That is, you need to implement a DocumentStore [0]. There are currently implementations for MongoDB [1] and RDB [2]. Consis