Cassandra as NodeStore

Hello guys, I'm currently assessing Oak as an alternative for content management on my cloud product. However, I already have a Cassandra cluster as the main persistence technology and to go additionally with Mongo would turn out in more complexity in terms of manteinance and support. So, have

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.38

On 2017-03-28 14:33, Dominique Jaeggi wrote: ... [X] +1 Release this package as Apache Jackrabbit Oak 1.0.38 Best regards, Julian

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.38

[X] +1 Release this package as Apache Jackrabbit Oak 1.0.38 all checks pass. Regards, Tommaso Il giorno mar 28 mar 2017 alle ore 15:13 Alex Parvulescu < alex.parvule...@gmail.com> ha scritto: > [X] +1 Release this package as Apache Jackrabbit Oak 1.0.38 > > all checks ok, > > alex > > > On

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.38

[X] +1 Release this package as Apache Jackrabbit Oak 1.0.38 all checks ok, alex On Tue, Mar 28, 2017 at 2:33 PM, Dominique Jaeggi wrote: > A candidate for the Jackrabbit Oak 1.0.38 release is available at: > >

Re: Backport of OAK-4933 to 1.6

Hi, I wasn’t aware that “releasing independently” is an option, and maybe even desired for future modules. This is currently proposed on https://issues.apache.org/jira/browse/OAK-4933. If you have input on how to make it successful, please add your input there (I’d be interested in the

[VOTE] Release Apache Jackrabbit Oak 1.0.38

A candidate for the Jackrabbit Oak 1.0.38 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.0.38/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.0.38/ The SHA1 checksum of the

Re: problem on oak jcr sql2 query

Hi Francesco, do you have other indexes within your Oak repo ? It might be that the query engine selects a different index which only acts on [nt:file] nodes. You can try checking the plan [1] for your query and compare with the [nt:base] version. It might also be useful to enable debug logging

R: problem on oak jcr sql2 query

We have wrapped oak jcr implementation with our data model, so it's not so easy give you our unit test (our sw is not yet open sourece :-)) Besides we know the documenti is correctly indexed, cause we see it in solr; so you can use any type of pdf: oak manage full text correctly. Anyway we

Re: Backport of OAK-4933 to 1.6

i was about to write pretty much the same thing :-) regards angela On 28/03/17 09:09, "Michael Dürig" wrote: > >As this is a new feature I would be interested in the motivation for >having to backport this. Generally we should only backport fixes for >defects. > >As Marcel

Re: problem on oak jcr sql2 query

Hi Francesco, Il giorno lun 27 mar 2017 alle ore 08:59 Ancona Francesco < francesco.anc...@siav.it> ha scritto: Sorry. We are using Oak 1.4.10 and solr 4.10.4 i send you also a pdf example: the searched word is "sezione" attachments do not usually get through the mailing list therefore we

Re: Documenting enhancements done in Oak 1.6

hi chetan On 24/03/17 07:11, "Chetan Mehrotra" wrote: >On Thu, Mar 23, 2017 at 10:19 PM, Angela Schreiber >wrote: >> i have been working on should already >> be included in the documentation because i try to do that before i >>resolve >> the

Re: Backport of OAK-4933 to 1.6

As this is a new feature I would be interested in the motivation for having to backport this. Generally we should only backport fixes for defects. As Marcel mentions on the issue a better approach would be to release this independently. If this is blocked by dependencies we should make an

Re: New JIRA component for observation

i agree with marcel. in general i would rather move forward with the modularisation and then adjust jira accordingly. kind regards angela On 27/03/17 09:26, "Marcel Reutegger" wrote: >Hi, > >I'm wondering if this is the best approach. Initially we used the JIRA >component