Re: start oak with file system storage

Hi Marco, I’d probably use data store classes instead (e.g. FileDataStore) and wrap them inside DataStoreBlobStore. -MR On October 5, 2017 at 7:51:58 AM, Marco Piovesana (pioves...@esteco.com) wrote: Hi all, I'm using Oak 1.6.1 with a file system storage (no migration from a previous version o

Waiting for an async index to be updated

Hi, In Sling we have some tests which validate that full text search is working. Occasionaly this test times out because the full-text lucene index is not updated and a traversal query is used. More details at [1]. We should probably add a way of waiting for the index to be updated, so my questio

start oak with file system storage

Hi all, I'm using Oak 1.6.1 with a file system storage (no migration from a previous version of the data). I think I kinda got lost between the options available to create the repository. I'm currently using a FileBlobStore with the following configuration: File repositoryFolder = new File(reposit

Re: Oak Bundle versioning.

Hi, On 5 October 2017 at 14:16, Julian Reschke wrote: > On 2017-10-05 14:33, Ian Boston wrote: > >> Hi, >> Currently the whole Oak source tree is synchronously versioned. Which is >> great for Oak and its releases, but problematic downstream. I assume this >> has been discussed before, and hope

Re: Oak Bundle versioning.

On 2017-10-05 14:33, Ian Boston wrote: Hi, Currently the whole Oak source tree is synchronously versioned. Which is great for Oak and its releases, but problematic downstream. I assume this has been discussed before, and hope it can be discussed again ? -- If it can, here is some supporting

Re: Oak Bundle versioning.

On 05/10/2017 13:33, Ian Boston wrote: > I am not saying all the problems are solved by independent bundle > versioning. There will be new problems. Perhaps, there would be less work > for Oak, and more flexibility downstream with independent versioning. > > wdyt? Probably when the Oak modularisat

Oak Bundle versioning.

Hi, Currently the whole Oak source tree is synchronously versioned. Which is great for Oak and its releases, but problematic downstream. I assume this has been discussed before, and hope it can be discussed again ? -- If it can, here is some supporting evidence, using Sling as an example.If i

Oak 1.7.9 release plan

Hello team, I'm planning to cut Oak on Monday 9th October. If there are any objections please let me know. Otherwise I will re-schedule any non-resolved issue for the next iteration. Thanks Davide

Re: Cold standby for oak-benchmarks: option vs fixture

2017-10-03 11:39 GMT+03:00 Chetan Mehrotra : > *Fixture* looks better *option* here! > Chetan Mehrotra Pun intended? :) Thanks for your feedback, Chetan! I'll go forward with the fixture.