[Oak origin/1.0] Apache Jackrabbit Oak matrix - Build # 769 - Still Failing

2016-02-26 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #769) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/769/ to view the results. Changes: [reschke] OAK-4033: RDBDocumentStore: refactor version check to

[Oak origin/1.2] Apache Jackrabbit Oak matrix - Build # 768 - Still Failing

2016-02-26 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #768) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/768/ to view the results. Changes: [reschke] OAK-4033: RDBDocumentStore: refactor version check to

[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 767 - Still Failing

2016-02-26 Thread Apache Jenkins Server
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #767) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/767/ to view the results. Changes: [chetanm] OAK-4031 - Clarify usage of includedPaths, excludedPa

R: info on queries and index

2016-02-26 Thread Ancona Francesco
Hello, so if Lucene or Solr have a problem or are busy for some reasons, we can't search anything, if i understand. So, i imagine, we have to be very careful to the search engine that is a potential single point of failure if it goes down or if loose index and so it has to make a full reindex.

Re: info on queries and index

2016-02-26 Thread Davide Giannella
On 25/02/2016 16:40, Ancona Francesco wrote: > > Hello, > > we’d like to study in deep queries and index. In particular is not so > clear, from documentation, what is indexed by default. > > For instance if i create a new type of document (IdentityCard with > name IDC) with 2 new properties (idCard

Re: Oak 1.3.17/1.4.0 release plan

2016-02-26 Thread Davide Giannella
On 25/02/2016 15:48, Alex Parvulescu wrote: >> If 1.3.17 contains the same as 1.4.0 then why do we even want to create a > 1.3.17 release? > I agree, if 1.3.17 == 1.4.0, cutting 2 releases makes very little sense. > Will go for this. It ease my game :) Cheers Davide