On 20/02/17 15:27, Alex Parvulescu wrote:
What about walking the revision history in smaller chunks?
Given a repository history of revisions: r0, r1, , r100, the indexer
would now diff [r0, r100] which can be resource intensive. What if it diffs
by a window of size 10: [r0, r9] (mark), [r10,
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1440)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1440/ to view
the results.
Changes:
[tommaso] OAK-5705 - no negative cost for Solr index
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1439)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1439/ to view
the results.
Changes:
[tomekr] OAK-5703: The replica set info gets invalid cluster
Good morning everyone,
focusing on Apache Sling, Apache Felix and Apache Jackrabbit, the adaptTo()
conference in Berlin is aimed at developers using some or all if this stack.
If you are not familiar with our event yet, you might find something
interesting in the sessions from last year
Hi Stefan,
Thanks for the response.
>>* Another commit Cn+1 comes - this marks Cn as "external" and itself
>>gets dropped
>
> Cn is not marked as external though, but yes, Cn+1 is dropped.
>
Ah!, I see now how that's working.
>>* The listener can consume all events till Cn, but Cn+1 and future
On 2017-02-20 14:49, Julian Reschke wrote:
On 2017-02-20 12:38, Marcel Reutegger wrote:
On 16/02/17 17:58, Julian Reschke wrote:
while running the checks for Oak 1.0.37 I got failures because I
happened to run MongoDB 3.2, not 2.6.
To answer your question in the subject: 2.6 is the only
On 20/02/2017 13:44, Marcel Reutegger wrote:
>
> Instead of the revision, the implementation can also rely on a
> checkpoint that marks the snapshot of the repository as the basis of
> the large-tree-operation.
I was thinking the same. We may rely on checkpoints and then store
additional info the
