Re: Semantic version in Oak

Hi, I think the main difference between Oak and Sling is, AFAIK, that Sling is "forward only", and does not maintain branches, and does not backport things. In Oak, we add new features in trunk (changing the API), and backport some of those features, and not necessarily all of them, and not

Re: jackrabbit-oak build #6972: Broken

"Out of heap space" On 27/11/15 18:54, "Travis CI" wrote: >Build Update for apache/jackrabbit-oak >- > >Build: #6972 >Status: Broken > >Duration: 420 seconds >Commit: 3f083e0134aca930ed44bdb5a19ccff9794aef1f (trunk) >Author: Julian Reschke

Re: Test failures in o.a.j.o.plugins.document.persistentCache.BroadcastTest

Hi, I will disabled those tests. Even thought the unit tests always worked for me, I couldn't get UDP to work with two "real" repositories (two processes). Regards, Thomas On 24/11/15 13:33, "Francesco Mari" wrote: >broadcastUDP

Re: [VOTE] Release Apache Jackrabbit 2.11.2

[X] +1 Release this package as Apache Jackrabbit 2.11.2 Thomas

Re: Start multiple instances of Oak throws an CommitFailedException

Hi, I would say initializing the collections (or tables when using a relational database) is not expected to be done concurrently. Maybe we can somehow preven that in Oak (patches are welcome!), or we document that this is not supported. Regards, Thomas On 26/10/15 18:36, "Navarro, Gabriela

Re: Reindexing problems

OK, I think we (kind of) agree on how to ensure important indexes are available. >>Additionally, for "synchronous" indexes (property index and so on), I >>would like to always create and reindex them asynchronously by default, OK, I see that large branches are a problem. Instead of using

Reindexing problems

Hi, If an index provider is (temporarily) not available, the MissingIndexProviderStrategy resets the index so it is re-indexed. This is a problem (OAK-2024, OAK-2203, OAK-2429, OAK-3325, OAK-3366, OAK-3505, OAK-3512, OAK-3513), because re-indexing is slow and one transaction. It can also cause

Re: jackrabbit-oak build #6598: Broken

Hi, > some fix missing in the 1.2 branch? You are right, it looks like the cause is OAK-3432. This is fixed in the trunk but not in the branch, because I thought it doesn't affect the branch (because the branch doesn't contain OAK-3234). But, now I see it also affects the branch. Regards,

Re: [Oak] Lucene copyonread OOM

Hi, Is this a 32-bit or 64-bit JVM? Could you try ulimit -v unlimited See http://stackoverflow.com/questions/8892143/error-when-opening-a-lucene-index-map-failed and possibly http://stackoverflow.com/questions/11683850/how-much-memory-could-vm-use-in-linux Regards, Thomas From:

Re: Jackrabbit OAK property index never used ?

ged by my property index. How could i fix this >node count supposed to be stored into a ":count" property ? > >Regards > >2015-09-23 12:15 GMT+02:00 Thomas Mueller <muel...@adobe.com>: > >> Hi, >> >> I think you are hitting OAK-2852. >> >

Re: svn commit: r1704844 - in /jackrabbit/oak/trunk: oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/index/counter/jmx/ oak-core/src/main/java/org/apache/jackrabbit/oak/query/ oak-core/src/ma

Hi, Yes, makes sense... what about getIndexCostInfo? Regards, Thomas On 24/09/15 07:41, "Chetan Mehrotra" wrote: >Hi Thomas, > >On Wed, Sep 23, 2015 at 6:51 PM, wrote: >> /** >> + * Get the index cost. The query must already be

Re: Jackrabbit OAK property index never used ?

Hi, I think you are hitting OAK-2852. Regards, Thomas On 23/09/15 11:42, "Thomas Mueller" <muel...@adobe.com> wrote: >Hi, > >Do you have a node called /oak:index/counter ? Out of the-box, it should >be there (with a recent version of Oak). That is the approximate

Re: Jackrabbit OAK property index never used ?

Hi, Do you have a node called /oak:index/counter ? Out of the-box, it should be there (with a recent version of Oak). That is the approximate counter index that is used to estimate how many nodes to traverse. As a workaround, you probably have to re-index that one manually. I wonder why that

Re: Question about the Oak Query Index

Hi, I will change the documentation to "Oak does not index _as_much_ content by default as does Jackrabbit 2". Regards, Thomas On 21/09/15 10:11, "Michael Lemler" wrote: >Oak >does not index content by default as does Jackrabbit 2

Re: Jackrabbit OAK property index never used ?

Hi, Which version of Oak do you use? Could you get the estimated node count for the root node, and for this index? To get that, for example use the NodeCounter JMX bean (NodeCounterMBean), getEstimatedChildNodeCounts("/", 2) and getEstimatedChildNodeCounts("/oak:index", 3). Regards, Thomas On

Re: Repo Inconsistencies due to OAK-3169

Hi, Could someone please update OAK-3169 with a link to the new issue, or the resolution? Regards, Thomas On 24/08/15 08:46, "Davide Giannella" wrote: >On 22/08/2015 19:59, Manfred Baedke wrote: >> Hi, >> >> OAK-3169 caused inconsistencies that currently have to be repaired

Re: [VOTE] Release Apache Jackrabbit Oak 1.3.5

[X] +1 Release this package as Apache Jackrabbit Oak 1.3.5 On 01/09/15 15:49, "Julian Reschke" wrote: >On 2015-09-01 15:30, Davide Giannella wrote: >> ... >> [ ] +1 Release this package as Apache Jackrabbit Oak 1.3.5 >> [ ] -1 Do not release this package

Using of final for variables and parameters

Hi, I wonder what does the team think about using final for variables and parameters. In Oak, so far we didn't use it a lot. This question has come up with OAK-3148. The patch uses final for variables, but not for parameters. Lately, I have seens some code (I forgot where) that uses final for

Re: Using of final for variables and parameters

Hi, - I know that the variable ³state created at the beginning of the method is the same one I can access at the end. For short methods, it's easy to see this, by reading the code. In my view easier than using final, which makes the code less readable. For large methods,... well you should

SegmentStore: MultiStore Compaction

Hi, I thought about SegmentStore compaction and made a few slides: http://www.slideshare.net/ThomasMueller12/multi-store-compaction Feedback is welcome! The idea is at quite an early stage, so if you don't understand or agree with some items, I'm to blame. Regards, Thomas

Re: SegmentStore: MultiStore Compaction

Hi, AFAIK your tests re. restart have been done from within an OSGi container (AEM) restarting the repository bundle. Actually I restarted the JVM. But I probably didn't use the very latest version of Oak, checkpoints may also have played a role in my case (there were 2 checkpoints; probably

Re: SegmentStore: MultiStore Compaction

On 28.8.15 10:05 , Thomas Mueller wrote: Hi, I thought about SegmentStore compaction and made a few slides: http://www.slideshare.net/ThomasMueller12/multi-store-compaction Feedback is welcome! The idea is at quite an early stage, so if you don't understand or agree with some items, I'm

Re: Is the hashing of long paths still needed?

Hi, The DocumentStore doesn't really know the path, it only knows the key, and if the key is hashed you can't calculate the path. There are some options: (a) Each document that has a hashed path as the key also has a path property (with the real path). You could use that (cache it, read it if

Re: Modularization

Hi, I have nothing against modularization, I'm just against modularization = create many many Maven projects. I prefer modularization *within* one project. Why can't we do that instead? Ideally you have a ³root² project, e.g. /oak /security /api /implementationA /implementationB

Re: Modularization

Hi, In my view, modularization is not equal to creating many Maven projects. - Bundles that do one and only one thing are more cohesive in their implementation. Currently, oak-core does too many things and exposes a low degree of cohesion. OK, this is your opinion, but I don't agree. I don't

Re: Modularization

Hi, - Move NodeStore implementations into their own modules. I think the time spent on that would be better used trying to improve modularization *within* oak-core, and for example move the DocumentMK to the test package, improve javadocs, get rid of unused methods and classes, and so on. -

Re: Modularization

Hi, OTOH if one module does storage and indexing and access control and monitoring for example it's too much IMO, that should ideally be four modules. Again, what would be the benefit of having many Maven projects? Besides, I don't think we could easily move all of access control to one Maven

[jira] [Commented] (JCR-3870) Export SessionImpl#getItemOrNull in JackrabbitSession

[ https://issues.apache.org/jira/browse/JCR-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660076#comment-14660076 ] Thomas Mueller commented on JCR-3870: - +1 Not only makes the code faster, but also

Re: Modularization

Hi, we already have 2 modules for access control That's fine... What I meant is, we shouldn't try to move oak-core org.apache.jackrabbit.oak.security.** plus org.apache.jackrabbit.oak.spi.security.** to new Maven projects. Or should we? jcr (top-bread) core (meat with all the validation)

[jira] [Commented] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14644006#comment-14644006 ] Thomas Mueller commented on JCR-3226: - http://svn.apache.org/r1693011 (trunk

[jira] [Commented] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14635015#comment-14635015 ] Thomas Mueller commented on JCR-3226: - [~dpfister], [~stefan@jira], [~tripod], could you

[jira] [Commented] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634838#comment-14634838 ] Thomas Mueller commented on JCR-3226: - Potential patch to fix the problem. This requires

[jira] [Updated] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-3226: Attachment: JCR-3226-test-2.patch JCR-3226-test-2.patch - improved test case, with possible solution

[jira] [Assigned] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller reassigned JCR-3226: --- Assignee: Thomas Mueller stateCreated deadlock - Key

[jira] [Commented] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634831#comment-14634831 ] Thomas Mueller commented on JCR-3226: - Please note the repository.xml file in the patch

[jira] [Commented] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14628128#comment-14628128 ] Thomas Mueller commented on JCR-3226: - I have a much simpler test case now. 3 threads

[jira] [Commented] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622347#comment-14622347 ] Thomas Mueller commented on JCR-3226: - So the output of the test is for example: i: 0 i

[jira] [Updated] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-3226: Attachment: JCR-3226-test.patch JCR-3226-test.patch: test case to reproduce the problem

[jira] [Commented] (JCR-3226) stateCreated deadlock

[ https://issues.apache.org/jira/browse/JCR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622383#comment-14622383 ] Thomas Mueller commented on JCR-3226: - I'm not an expert in this area, maybe [~stefan

Re: /oak:index (DocumentNodeStore)

Hi, Using MongoDB indexes directly doesn't work because of the MVCC model. What we could do is add special collections (basically one collection per index). This would requires some work, which then would need to be repeated for RDBMK. It would be quite some work. I observe that 60% of the size

Re: LazyInputStream does not uses BufferedInputStream while creating stream from underlying File

:31 PM, Thomas Mueller muel...@adobe.com wrote: Yes, it would be better if we wrap it somewhere (not necessarily right there, but somewhere I think we can do that in DataStoreBlobStore. Right? Chetan Mehrotra

Re: LazyInputStream does not uses BufferedInputStream while creating stream from underlying File

Hi, Yes, it would be better if we wrap it somewhere (not necessarily right there, but somewhere), because the caller will not always do that. I thought that's already done, but I'm not sure. Regards, Thomas On 21/05/15 08:20, Chetan Mehrotra chetan.mehro...@gmail.com wrote: While having a look

Re: xpath backwards compatibility issue

Hi, Could you log a bug for Oak please? I think the correct query is (a), and that should also work for Oak. I implemented the XPath parser for Oak, and was not aware that true() and false() are functions... See also http://www.w3schools.com/xpath/xpath_functions.asp Regards, Thomas On

Re: [VOTE] retire oak-mk-remote into attic

+1 On 26/03/15 15:20, Angela Schreiber anch...@adobe.com wrote: Dear Oak Team During initial phase of building a new JCR content repository (OAK), we added an remoting layer for the original persistence layer (called MicroKernel) which since then has been part of the Oak project. In the mean

[jira] [Commented] (JCR-3858) NodeIterator.getSize(): compatibility with Jackrabbit 2.5

[ https://issues.apache.org/jira/browse/JCR-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14364714#comment-14364714 ] Thomas Mueller commented on JCR-3858: - I think by default it should be as secure

[jira] [Commented] (JCR-3858) NodeIterator.getSize(): compatibility with Jackrabbit 2.5

[ https://issues.apache.org/jira/browse/JCR-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14365263#comment-14365263 ] Thomas Mueller commented on JCR-3858: - To enable, the property sizeEstimate needs

[jira] [Resolved] (JCR-3858) NodeIterator.getSize(): compatibility with Jackrabbit 2.5

[ https://issues.apache.org/jira/browse/JCR-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-3858. - Resolution: Fixed Revision 1667317 (trunk) Revision 1667318 (2.6 branch) NodeIterator.getSize

Re: [RESULT][VOTE] Release Apache Jackrabbit Oak 1.0.12

Hi, OK, next time, I will vote -1 in such a situation. Regards, Thomas On 10/03/15 11:35, Marcel Reutegger mreut...@adobe.com wrote: Hi, the vote passes as follows: +1 Michael Dürig +1 Amit Jain +1 Alex Parvulescu +1 Davide Giannella +1 Julian Reschke +1 Thomas Mueller I'll push

[jira] [Created] (JCR-3858) NodeIterator.getSize(): compatibility with Jackrabbit 2.5

Thomas Mueller created JCR-3858: --- Summary: NodeIterator.getSize(): compatibility with Jackrabbit 2.5 Key: JCR-3858 URL: https://issues.apache.org/jira/browse/JCR-3858 Project: Jackrabbit Content

[jira] [Commented] (JCR-3858) NodeIterator.getSize(): compatibility with Jackrabbit 2.5

[ https://issues.apache.org/jira/browse/JCR-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14356682#comment-14356682 ] Thomas Mueller commented on JCR-3858: - Patch for review: {noformat} Index: src/main

Re: Active deletion of 'deleted' Lucene index files from DataStore without relying on full scale Blob GC

Hi, I think removing binaries directly without going though the GC logic is dangerous, because we can't be sure if there are other references. There is one exception, it is if each file is guaranteed to be unique. For that, we could for example append a unique UUID to each file. The Lucene file

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.12

Because of OAK-2576, I think Oak 1.0.12 it not usable. So I would stop work on it. At least we don't need to update the web page (to advertise it). On 04/03/15 20:58, Michael Dürig mdue...@apache.org wrote: On 4.3.15 8:51 , Marcel Reutegger wrote: Hi, I just identified a regression in the

Re: [VOTE] Release Apache Jackrabbit Oak 1.1.7

Hi, Because of OAK-2576, I think Oak 1.1.7 it not usable. So I would stop work on it. Regards, Thomas On 04/03/15 13:52, Julian Reschke julian.resc...@gmx.de wrote: On 2015-03-04 13:03, Davide Giannella wrote: A candidate for the Jackrabbit Oak 1.1.7 release is available at:

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.12

10:18, Thomas Mueller muel...@adobe.com wrote: Because of OAK-2576, I think Oak 1.0.12 it not usable. So I would stop work on it. At least we don't need to update the web page (to advertise it). On 04/03/15 20:58, Michael Dürig mdue...@apache.org wrote: On 4.3.15 8:51 , Marcel Reutegger wrote

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.12

+1 Release this package as Apache Jackrabbit Oak 1.0.12

Re: cleaning old Oak branches in svn

+1 clean up On 25/02/15 10:03, Alex Parvulescu alex.parvule...@gmail.com wrote: Hi, I noticed we have some old unused branches on our svn repo [0], some are candidates for cleanup: 0.6, 0.7, jackrabbit-oak-core-0.15, pre-0.4. what do others think, can we clean this up? thanks, alex [0]

Re: [DISCUSS] Atomic Counters on cluster

Hi, I would use the index approach, at least for now. By the way, I have used the same idea for the approximate node counter mechanism (OAK-1907). A generalisation of the atomic counter problem is the atomic sum problem. For that, you don't just want to support +1 and -1, but +x and -x, possibly

Re: Custom scorer for modifying score per documents

Hi, I wonder, do we only need to use the (custom) scorer if the query orders by the pseudo-property jcr:score? I mean, it's probably faster not to use any scorer, right? Regards, Thomas On 15/01/15 08:17, Rishabh Kumar Maurya mau...@adobe.com wrote: Hi, We have search enhancements requests

Re: oak-core vs JSON

Hi, 1) I feel uncomfortable about using something for JSON that has been written for a different purpose (JSOP), allowing certain extensions I definitively don't want to use. You'll need non-standard JSON if you want to use concatenation as follows: data = r1: {a: 1} update ... set data =

Re: oak-core vs JSON

Hi, FWIW, the persistent cache doesn't seem to use oak.commons.json... The persistend cache uses for example NodeDocument.asString and fromString, which use oak.commons.json. Regards, Thomas

Re: oak-core vs JSON

Hi, oak.commons.json is currently also used in MicroKernelImpl, and the persistent cache in the DocumentNodeStore. In my experience, the classes JsopBuilder, JsopTokenizer, and JsopStream are much faster and need less memory than org.json.simple, because they use low level streaming, and not a

Re: [discuss] IndexStoreStrategy API change

Hi, Sounds good to me. Regards, Thomas On 09/12/14 14:56, Davide Giannella dav...@apache.org wrote: Good afternoon everyone, while I was looking into other issues, I found that it would be useful if we pass to the IndexStoreStrategy.update() either the indexName, or even better a NodeState

Re: [VOTE] Release Apache Jackrabbit Oak 1.1.3

+1 Release this package as Apache Jackrabbit Oak 1.1.3 On 09/12/14 17:17, Davide Giannella dav...@apache.org wrote: A candidate for the Jackrabbit Oak 1.1.3 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.1.3/ The release candidate is a zip archive of

Re: [DISCUSS] supporting faceting in Oak query engine

Hi, I would like the counts. I agree. I guess this feature doesn't make much sense without the counts. 1, 2, and 4 seem like bad ideas 1 undercuts the idea that we'd use lucene/solr to get decent performance. Sorry I don't understand... This is just about the API to retrieve the data. It

Re: [DISCUSS] supporting faceting in Oak query engine

Hi, I think we should do: 1. conservative approach, do not touch JCR API select [jcr:path], [facet(jcr:primaryType)] from [nt:base] where contains([text, 'oak']); The column facet(jcr:primaryType) would return the facet data. I think that's a good approach. The question is, which rows

Re: Oak queries for a particular branch?

Hi, Oak internally branches in some cases, but this is not exposed in the JCR API (you can not enforce creating a branch). Regards, Thomas On 26/11/14 18:56, John Gretz jgre...@yahoo.com.INVALID wrote: Hey guys, a newbie Oak question: Since there is support for a single workspace only in Oak,

Re: Disable parsing of fulltext string in QueryEngine

Hi, I want to treat following two differently 1. FulltextExpression created out of simple string term passed to a single jcr:contains in a query 2. FulltextExpression by combining multiple jcr:contains For #1 it would be better to get access to raw string and pass it to Lucene analyzer for

Re: svn commit: r1634774 - 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/

Hi, I think using entryCount is ok. It's anyway only needed until we have proper cost estimation in the property index and ordered index. Regards, Thomas On 28/10/14 09:32, Davide Giannella dav...@apache.org wrote: On 28/10/2014 03:23, am...@apache.org wrote: Author: amitj Date: Tue Oct 28

Re: DocumentNodeStore backgroundRead

Hi, Changes from other cluster nodes are detected that way (if a cluster node changes anything, it writes to the root node once a second). Regards, Thomas On 25/10/14 13:08, Julian Reschke julian.resc...@gmx.de wrote: Hi again. I've been looking at what cache misses the RDBDocumentStore gets.

Re: Reindex and external indexes - Possibility of stale index data

and which data is old (by comparing the values). Regards, Thomas Later Lucene would make use of that time to create a directory as you suggested above and reclaim old directory Chetan Mehrotra On Mon, Oct 13, 2014 at 2:33 PM, Thomas Mueller muel...@adobe.com wrote: Hi, Then would use

Re: CopyInReadDirectory and local filesystem path

Hi, What about using the SHA-2 hash code of the JCR path? Regards, Thomas On 21/10/14 09:53, Chetan Mehrotra chetan.mehro...@gmail.com wrote: For implementing CopyOnReadDirectory (OAK-1724) I need to copy the Lucene index content to a local directory. However as there can be multiple Lucene

Re: Reindex and external indexes - Possibility of stale index data

, 2014 at 1:18 PM, Thomas Mueller muel...@adobe.com wrote: What we need is a distinction between the old and the new index *data*. Yes and that can be done by storing the index creation time. In the approach you suggested where two different nodes are used and later the nodes are renamed allows

Re: Reducing traversing log to DEBUG

Hi, Keeping it at WARN is very important. Otherwise, we don't have a way to see missing indexes / bad queries. I think setting it to 10'000 (instead of 1000) is probably a good idea. Making it configurable, if you really want then OK, if the default is 10'000. Regards, Thomas On 21/10/14

Re: Reindex and external indexes - Possibility of stale index data

to differentiate index state for a reindex call and that can be managed easily via storing the creation time in the index definition node which works easily with existing logic Chetan Mehrotra On Tue, Oct 21, 2014 at 1:51 PM, Thomas Mueller muel...@adobe.com wrote: Hi, The node doesn't need

Re: Does Lucene modifies existing file in an index

Hi, This blog post is interesting: they are using a physical switch (similar to a christmas light timer) to test a Lucene index doesn't get corrupt on power failure. It would be nice if we can do something similar with the Segment storage at some point. Regards, Thomas On 20/10/14 13:36,

Re: Oak documentation and features added in specific versions

+1 On 16/10/14 09:40, Davide Giannella dav...@apache.org wrote: On 16/10/2014 06:01, Chetan Mehrotra wrote: 2. OR Update in trunk and mention that its a 1.0.8+ feature +1 D.

DocumentStore: StableRevisionComparator ignored the branch flag

Hi, I wonder if there is a bug in the StableRevisionComparator. It uses Revision.compareRevisionTimeThenClusterId, which doesn't take the branch flag into account. I would probably use the following instead: /** * Compare all components of two revisions. * * @param other the other revision

Re: Execution stats for AsyncIndexUpdate

Hi, As for creating an index, I think it would make sense to know the number of nodes indexed so far. That way it can be used to predict (roughly) when it will be finished (based on the number of nodes that were indexed last time). Regards, Thomas On 14/10/14 09:13, Amit Jain am...@apache.org

Re: [VOTE] Release Apache Jackrabbit Oak 1.0.7

[X] +1 Release this package as Apache Jackrabbit Oak 1.0.7

Re: Reindex and external indexes - Possibility of stale index data

Hi, As for external Lucene indexes, what about this: * in the :data node, store a index creation time, in milliseconds since 1970 * use that as a path prefix for the actual index files So if the index is configured as follows: /oak:index/lucene { path: /quickstart/repo/lucenIndex } Then

Re: Reindex and external indexes - Possibility of stale index data

as well. Regards, Thomas On 13/10/14 10:45, Thomas Mueller muel...@adobe.com wrote: Hi, As for external Lucene indexes, what about this: * in the :data node, store a index creation time, in milliseconds since 1970 * use that as a path prefix for the actual index files So if the index

Command line tools documentation

Hi, I didn't find any official documentation about the command line tools. I have started documenting oak-run: http://jackrabbit.apache.org/oak/docs/command_line.html Regards, Thomas

[jira] [Created] (JCR-3812) Improvements to the GQL tools

Thomas Mueller created JCR-3812: --- Summary: Improvements to the GQL tools Key: JCR-3812 URL: https://issues.apache.org/jira/browse/JCR-3812 Project: Jackrabbit Content Repository Issue Type

[jira] [Updated] (JCR-3812) Improvements to the GQL tools

[ https://issues.apache.org/jira/browse/JCR-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller updated JCR-3812: Attachment: JCR-3812.patch Proposed patch Improvements to the GQL tools

[jira] [Resolved] (JCR-3812) Improvements to the GQL tools

[ https://issues.apache.org/jira/browse/JCR-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-3812. - Resolution: Fixed Revision 1627529 Improvements to the GQL tools

[jira] [Comment Edited] (JCR-3812) Improvements to the GQL tools

[ https://issues.apache.org/jira/browse/JCR-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147687#comment-14147687 ] Thomas Mueller edited comment on JCR-3812 at 9/25/14 1:03 PM

Re: blobs are not being retained when using MicroKernel interface, adds str: prefix to blobId property value

at 1:35 AM, Thomas Mueller muel...@adobe.com wrote: Hi, I'm not sure, maybe this is an XY problem: http://meta.stackexchange.com/questions/66377/what-is-the-xy-problem So... what problem do you want to solve? For example, are you looking for a scalable solution (if yes why), or do you want

Re: blobs are not being retained when using MicroKernel interface, adds str: prefix to blobId property value

Hi, I'm not sure, maybe this is an XY problem: http://meta.stackexchange.com/questions/66377/what-is-the-xy-problem So... what problem do you want to solve? For example, are you looking for a scalable solution (if yes why), or do you want multiple clients (from different machines or processes)

Re: buildbot failure in ASF Buildbot on oak-trunk

Sorry about that... Should be fixed now. On 17/09/14 19:53, build...@apache.org build...@apache.org wrote: The Buildbot has detected a new failure on builder oak-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk/builds/529 Buildbot URL:

Re: Jackrabbit GC on huge MySQL Database

Hi, In Jackrabbit Oak, we have a different (much, much faster) approach to do garbage collection, but there is no plan to backport that to Jackrabbit 2.x. The approach is: scan the repository (not traverse, but do a low level scan in the persistent storage) for blob ids. Then get the list of

Re: Using BlobStore by default with SegmentNodeStore

Hi, In addition or instead of using the BlobStore, we could store the Lucene index to the filesystem (persistence = file, path = ...). But I would probably only do that on a case-by-case basis. I think it would reduce, but not solve the compaction problem. Some numbers from a test repository I

[ANNOUNCE] Apache Jackrabbit Oak 1.0.5 released

The Apache Jackrabbit community is pleased to announce the release of Apache Jackrabbit Oak 1.0.5. The release is available for download at: http://jackrabbit.apache.org/downloads.html See the full release notes below for details about this release. Release Notes -- Apache Jackrabbit Oak --

[RESULT] [VOTE] Release Apache Jackrabbit Oak 1.0.5

Hi, On 26/08/14 08:42, Thomas Mueller wrote: Please vote on releasing this package as Apache Jackrabbit Oak 1.0.5. The vote is open for the next 72 hours and passes if a majority of at least three +1 Jackrabbit PMC votes are cast. The vote passes as follows: +1 Thomas Mueller +1 Michael

Re: OrderedIndex does not comply with JCR's compareTo semantics

Hi, Could we use a new index type for the new format? For example ordered2 instead of ordered. I know not very creative naming :-) This is a fix to the current index implementation. I think we should stay with the current index. Well, we need some way to know whether the data was migrated or

Re: NodeStore#checkpoint api reevaluation

Hi, I think we need to decide whether not beeing able to create checkpoint is an important and common case or not. * If it's an common case (if it uses tryAcquire which may or may not work), then I would prefer tryCheckpoint with a possible return value of null. * If it's not a common case,

Re: New Jackrabbit committer: Amit Jain

Hi, Welcome to the team! Regards, Thomas From: Alex Parvulescu alex.parvule...@gmail.commailto:alex.parvule...@gmail.com Reply-To: dev@jackrabbit.apache.orgmailto:dev@jackrabbit.apache.org dev@jackrabbit.apache.orgmailto:dev@jackrabbit.apache.org Date: Wednesday 27 August 2014 09:43 To:

Re: NodeStore#checkpoint api reevaluation

Hi, I would prefer if the checkpoint method is renamed to tryCheckpoint or similar, if it is a best effort method (which seems to be the case, as it uses commitSemaphore.tryAcquire()). If a checkpoint can't be created, then I would return null. This is the same as FileChannel.tryLock (returns

Re: OrderedIndex does not comply with JCR's compareTo semantics

Hi, Could we use a new index type for the new format? For example ordered2 instead of ordered. I know not very creative naming :-) I would prefer if the translation is done automatically on restart or re-index. I woudn't want to install Groovy and / or have to do manual steps if possible.

[VOTE] Release Apache Jackrabbit Oak 1.0.5

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

Re: Oak 1.0.4 release plan

Hi, Now that 1.0.4 is out, it's time to plan the next minor release. I'm planning to cut the 1.0.5 release today in about 30 minutes. Regards Thomas

<    1   2   3   4   5   6   7   8   9   10   >