Re: svn commit: r1656394 - in /jackrabbit/oak/trunk/oak-lucene/src: main/java/org/apache/jackrabbit/oak/plugins/index/lucene/ test/java/org/apache/jackrabbit/oak/plugins/index/lucene/

2015-02-02 Thread Julian Sedding
Thanks! On Mon, Feb 2, 2015 at 10:37 AM, Chetan Mehrotra chetan.mehro...@gmail.com wrote: Hi Julian, On Mon, Feb 2, 2015 at 2:17 PM, Julian Sedding jsedd...@gmail.com wrote: Would it not make sense to give the configuration node an extension, i.e. tika/config.xml

Re: Initial work for the specification of a remote API

2015-02-02 Thread Michael Dürig
Hi, I finally found some time to read your draft: * what about large number of child nodes? I think we need some kind of support for paging/chunking to avoid reading millions of children in one go. * the write operations all fail if the operation has been done already: E.g. the remove

Re: Initial work for the specification of a remote API

2015-02-02 Thread Michael Dürig
On 23.1.15 6:09 , Francesco Mari wrote: since I don't have access to the wiki, I started to write down a draft for the remote API in a public GitHub repository [1]. Let me know the desired user name and I'll grant you access. Michael

Re: svn commit: r1656394 - in /jackrabbit/oak/trunk/oak-lucene/src: main/java/org/apache/jackrabbit/oak/plugins/index/lucene/ test/java/org/apache/jackrabbit/oak/plugins/index/lucene/

2015-02-02 Thread Chetan Mehrotra
Hi Julian, On Mon, Feb 2, 2015 at 2:17 PM, Julian Sedding jsedd...@gmail.com wrote: Would it not make sense to give the configuration node an extension, i.e. tika/config.xml (tika/config.xml/jcr:content/@jcr:data)? Makes sense!. Done with http://svn.apache.org/r1656425 Chetan Mehrotra

Re: Initial work for the specification of a remote API

2015-02-02 Thread Axel Hanikel
Hi, I’m not sure if I have enough background to participate in the discussion, so bear with me... I think it wouldn’t be too hard to translate oak operations to an HTTP-based API, if we just define some URLs as “special”, i.e. they don’t represent the corresponding node in the repo but have

Re: Initial work for the specification of a remote API

2015-02-02 Thread Julian Reschke
On 2015-02-02 15:33, Axel Hanikel wrote: Hi, I’m not sure if I have enough background to participate in the discussion, so bear with me... I think it wouldn’t be too hard to translate oak operations to an HTTP-based API, if we just define some URLs as “special”, i.e. they don’t represent the

Re: Initial work for the specification of a remote API

2015-02-02 Thread Michael Dürig
On 2.2.15 3:33 , Axel Hanikel wrote: Hi, I’m not sure if I have enough background to participate in the discussion, so bear with me... I think it wouldn’t be too hard to translate oak operations to an HTTP-based API, if we just define some URLs as “special”, i.e. they don’t represent the

Re: Initial work for the specification of a remote API

2015-02-02 Thread Lukas Kahwe Smith
Aloha, BTW .. I have not used their API but https://www.contentful.com/developers/ is a content repository as a service. Not sure how they deal with concurrency and multi step changes but maybe worth a look. regards, Lukas Kahwe Smith sm...@pooteeweet.org signature.asc Description:

Re: Initial work for the specification of a remote API

2015-02-02 Thread Francesco Mari
I am currently working on a REST API, that looks similar to what you are proposing. I should have something to show really soon. 2015-02-02 15:33 GMT+01:00 Axel Hanikel ahani...@gmail.com: Hi, I’m not sure if I have enough background to participate in the discussion, so bear with me... I

Re: Initial work for the specification of a remote API

2015-02-02 Thread Francesco Mari
I agree that a mechanism to cope with children is needed, other than filtering by name. I partially agree when you say that the end result of a single operation can be either successful, skipped or failed. I am not really sure if we need the skipped result, because a set of operations is supposed

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.11

2015-02-02 Thread Marcel Reutegger
Hi, The vote passes as follows: +1 Alex Parvulescu +1 Julian Reschke +1 Davide Giannella +1 Marcel Reuteggger Thanks for voting. I'll push the release out. Regards Marcel On 26/01/15 16:27, Marcel Reutegger mreut...@adobe.com wrote: Hi, A candidate for the Jackrabbit Oak 1.0.11 release is

jackrabbit-oak build #5132: Broken

2015-02-02 Thread Travis CI
Build Update for apache/jackrabbit-oak - Build: #5132 Status: Broken Duration: 5988 seconds Commit: 5f2803973cadbfd8584aaadfc21f8de2cfdf8af3 (trunk) Author: Chetan Mehrotra Message: OAK-2463 - Provide support for providing custom Tika config Move Tika related

Re: svn commit: r1656394 - in /jackrabbit/oak/trunk/oak-lucene/src: main/java/org/apache/jackrabbit/oak/plugins/index/lucene/ test/java/org/apache/jackrabbit/oak/plugins/index/lucene/

2015-02-02 Thread Julian Sedding
Hi Chetan Would it not make sense to give the configuration node an extension, i.e. tika/config.xml (tika/config.xml/jcr:content/@jcr:data)? That way tika configs that are edited via WebDAV (or installed as part of a content-package) could benefit from the XML support of text-editors. Regards

Re: jackrabbit-oak build #5132: Broken

2015-02-02 Thread Chetan Mehrotra
Failure with exit code 137. /home/travis/build.sh: line 41: 3348 Killed mvn verify -P${PROFILE} ${FIXTURES} ${SUREFIRE_SKIP} The command mvn verify -P${PROFILE} ${FIXTURES} ${SUREFIRE_SKIP} exited with 137. --- Chetan Mehrotra On Mon, Feb 2, 2015 at 2:14 PM, Travis CI

[RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.10

2015-02-02 Thread Amit Jain
Vote passes as follows: +1 Amit Jain +1 Julian Reschke +1 Alex Parvulescu +1 Davide Giannella Thanks for voting. I'll push the release out. -- Forwarded message -- From: Amit Jain am...@apache.org Date: Fri, Jan 23, 2015 at 12:33 PM Subject: [VOTE] Release Apache Jackrabbit Oak