buildbot failure in ASF Buildbot on oak-trunk-win7

2014-08-12 Thread buildbot
The Buildbot has detected a new failure on builder oak-trunk-win7 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/oak-trunk-win7/builds/463 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-win7 Build Reason: scheduler Build Source

Re: buildbot failure in ASF Buildbot on oak-trunk-win7

2014-08-12 Thread Chetan Mehrotra
Test failed is in oak-pojosr for TokenAuthenticationTest. It passes locally but has been seen failing few times on build bot. Would have a look at that. However the failure is not related to changes done in last commit Running org.apache.jackrabbit.oak.run.osgi.TokenAuthenticationTest Tests run:

Re: Confusions about API's and Flavours in the documentation ...

2014-08-12 Thread Thomas Mueller
Hi, I think the documentation shouldn't talk about SegmentMK, specially because such a class doesn't exist. Instead, I think it should talk about the high level concepts segment storage and document storage, plus concrete implementations tar file persistence (based on the segment storage), and

Re: Confusions about API's and Flavours in the documentation ...

2014-08-12 Thread Michael Dürig
On 12.8.14 1:24 , KÖLL Claus wrote: Hi, After looking more and more into the oak codebase i feel sometimes a little bit confused with the documentation. I think the documentation doesn't reflect the reality in the codebase regarding the Microkernel API and NodeStore API for the two flavours

AW: Confusions about API's and Flavours in the documentation ...

2014-08-12 Thread KÖLL Claus
Hi, Ok thanks for your feedback ... And yes, it's confusing. .. so I'm not alone here :-) I would change the documentation to better fit the right terms. greets claus

Re: AW: Confusions about API's and Flavours in the documentation ...

2014-08-12 Thread Angela Schreiber
hi claus And yes, it's confusing. .. so I'm not alone here :-) no... nobody gets it... in particular as one term is also the marketing term for the other... just makes the mess a complete mess. as far as i am concerned i don't know any good reason for keeping two APIs for the same thing. IMO we

Re: AW: Confusions about API's and Flavours in the documentation ...

2014-08-12 Thread Michael Dürig
On 12.8.14 4:08 , Angela Schreiber wrote: hi claus And yes, it's confusing. .. so I'm not alone here :-) no... nobody gets it... in particular as one term is also the marketing term for the other... just makes the mess a complete mess. as far as i am concerned i don't know any good

Re: Speeding-up the OrderedIndex

2014-08-12 Thread Davide Giannella
On 11/08/2014 21:07, Justin Edelson wrote: In my experience, you would use minute precision for range queries and second precision for ordering. So I guess this means that second precision would be the best default and then allowing minute precision to be used as an optimization for an index

Cleanup NodeStore and MK implementations (was: Re: AW: Confusions about API's and Flavours in the documentation ...)

2014-08-12 Thread Angela Schreiber
hi all i recently had another look at the oak-core module and was thinking if it wouldn't be better if we would move the NodeStore implementations into separate modules. to begin with i just tried 2 separate modules: - oak-ns-document: everything below oak.plugins.document -