On 2014-03-06 23:30, Tobias Bocanegra wrote:
Hi,
I think you need to use a higher clock-drift interval. IIUC, you
currently use 1 second. but on some machines, the
System.getTimeMillis() can be as inaccurate than 2 seconds.
Such as?
I don't think that was caused by my change.
regards Toby
On Thursday, March 6, 2014, 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/4605
>
> Buildbot URL: http
Hi,
On Thu, Mar 6, 2014 at 5:30 PM, Tobias Bocanegra wrote:
> I think you need to use a higher clock-drift interval. IIUC, you
> currently use 1 second. but on some machines, the
> System.getTimeMillis() can be as inaccurate than 2 seconds.
The intention is to remain in sync with currentTimeMill
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/4605
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
Hi,
I think you need to use a higher clock-drift interval. IIUC, you
currently use 1 second. but on some machines, the
System.getTimeMillis() can be as inaccurate than 2 seconds.
however, since a long can hold up to more than 200 years of
nano-seconds, I don't think we need an accurate system tim
Hi,
On Thu, Mar 6, 2014 at 9:13 AM, Chetan Mehrotra
wrote:
> Proposal
> -
>
> To enable ease of both configuration and modularity we already support
> OSGi. With PojoSR (as explained in other mail [1]) we can support both
>
> 1. Have a PojoSR based RepositoryFactory to provide access
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4598
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
Hi,
On Wed, Mar 5, 2014 at 6:52 PM, Tobias Bocanegra wrote:
> I recently encountered a bug where someone created an index definition
> in the initial content, that contains a property name with a namespace
> that was never registered.
The NameValidator is not run against the initial content, sin
Hi,
On Thu, Mar 6, 2014 at 1:00 AM, Davide Giannella
wrote:
> On 05/03/2014 23:52, Tobias Bocanegra wrote:
>> ...
>> the index was created, but then later, accessing the index node
>> through JCR failed.
>> I wanted to create a test and an issue, but have difficulties to find
>> an existing test
Hi,
On Thu, Mar 6, 2014 at 12:54 PM, wrote:
> Full details are available at:
> http://ci.apache.org/builders/oak-trunk/builds/4597
Running org.apache.jackrabbit.oak.jcr.ConcurrentAddReferenceTest
Tests run: 6, Failures: 1, Errors: 1, Skipped: 1, Time elapsed: 9.449
sec <<< FAILURE!
addReferenc
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/4597
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
Build Update for apache/jackrabbit-oak
-
Build: #3604
Status: Broken
Duration: 1841 seconds
Commit: 705227f2da9d34a108a04d4f191166ad791ec31e (trunk)
Author: Davide Giannella
Message: OAK-1263 disabled the OrderedIndex by providing INFINITE in the cost
View the
Hi,
Till JR2 the repository was configured via repository.xml which served
two purposes
1. Support for DI
2. Configuring the service properties
>From the end user perspective this used to prove useful from usability
point of view.
1. One can see what all components are involved
2. Easy to speci
Hi Davide,
2014-03-06 15:43 GMT+01:00 Davide Giannella :
> Hello Tommaso,
>
> On 06/03/2014 14:32, Tommaso Teofili wrote:
> > Hi all,
> >
> > for my Solr (indexing) resiliency use case [1] I've implemented an
> > extension of Solr client which is able to cache requests if Solr goes
> down
> > and
Hi,
2014-03-06 15:46 GMT+01:00 Jukka Zitting :
> Hi,
>
> On Thu, Mar 6, 2014 at 9:32 AM, Tommaso Teofili
> wrote:
> > for my Solr (indexing) resiliency use case [1] I've implemented an
> > extension of Solr client which is able to cache requests if Solr goes
> down
> > and execute them back once
The Buildbot has detected a restored build on builder oak-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk/builds/4592
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stam
Hi,
On Thu, Mar 6, 2014 at 9:32 AM, Tommaso Teofili
wrote:
> for my Solr (indexing) resiliency use case [1] I've implemented an
> extension of Solr client which is able to cache requests if Solr goes down
> and execute them back once the Solr instance comes back.
>
> Now if the repository goes do
Hello Tommaso,
On 06/03/2014 14:32, Tommaso Teofili wrote:
> Hi all,
>
> for my Solr (indexing) resiliency use case [1] I've implemented an
> extension of Solr client which is able to cache requests if Solr goes down
> and execute them back once the Solr instance comes back.
>
> Now if the reposit
Hi all,
for my Solr (indexing) resiliency use case [1] I've implemented an
extension of Solr client which is able to cache requests if Solr goes down
and execute them back once the Solr instance comes back.
Now if the repository goes down during the Solr downtime we loose the
cached requests as t
the build failure:
addReferences[2](org.apache.jackrabbit.oak.jcr.ConcurrentAddReferenceTest):
OakState0001: Unresolved conflicts in /
i don't know how that relates to my changes.
regards
angela
On 06/03/14 15:00, "build...@apache.org" wrote:
>The Buildbot has detected a new failure on bu
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/4591
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source Stamp:
On 6.3.14 11:26 , thom...@apache.org wrote:
Author: thomasm
Date: Thu Mar 6 10:26:06 2014
New Revision: 1574837
URL: http://svn.apache.org/r1574837
Log:
OAK-1263 Optimize oak index to support 'fast ORDER BY' queries
Credits due to Davide Giannella for this patch. Great stuff!
Michael
Build Update for apache/jackrabbit-oak
-
Build: #3598
Status: Fixed
Duration: 2493 seconds
Commit: aae9e5242551491c5d8ee694870253fb7d32d9fa (trunk)
Author: Tommaso Teofili
Message: OAK-1286 - added missing tests for MLT feature in Solr
git-svn-id: https://svn.
Build Update for apache/jackrabbit-oak
-
Build: #3597
Status: Fixed
Duration: 2749 seconds
Commit: 9391f658c32f199c6db48f5d8d635a97b54cd950 (trunk)
Author: Thomas Mueller
Message: OAK-1263 Optimize oak index to support 'fast ORDER BY' queries
git-svn-id: https
Build Update for apache/jackrabbit-oak
-
Build: #3596
Status: Fixed
Duration: 2614 seconds
Commit: 9b43b8c6aff3af6d60fe28b7cefac4f2cec67657 (trunk)
Author: Angela Schreiber
Message: OAK-1434: readme
git-svn-id: https://svn.apache.org/repos/asf/jackrabbit/oak/t
Build Update for apache/jackrabbit-oak
-
Build: #3595
Status: Broken
Duration: 1700 seconds
Commit: a5e90804911b4c09cad35060ec31557e2b12c145 (trunk)
Author: Michael Duerig
Message: OAK-1491: ObservationTest failure on Windows
Better naming
git-svn-id: https://
Hi Toby,
On 05/03/2014 23:52, Tobias Bocanegra wrote:
> ...
> the index was created, but then later, accessing the index node
> through JCR failed.
> I wanted to create a test and an issue, but have difficulties to find
> an existing test to copy from :-)
>
didn't really understand what you want t
The Buildbot has detected a restored build on builder oak-trunk-win7 while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/oak-trunk-win7/builds/4769
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: bb-win7
Build Reason: scheduler
Build Source
28 matches
Mail list logo
