with the test configuration changed (as per r1666100) I could see the
suggester being updated continuously only within SuggestTest, while for
e.g. QueryJcrTest it did the update only once upon the first commit.
Regards,
Tommaso
2015-03-12 10:18 GMT+01:00 Chetan Mehrotra :
> Thanks Tommaso!. Let
Thanks Tommaso!. Let see how the next build runs
http://ci.apache.org/builders/oak-trunk/builds/1144
Chetan Mehrotra
On Thu, Mar 12, 2015 at 2:36 PM, Tommaso Teofili
wrote:
> I've created https://issues.apache.org/jira/browse/OAK-2611 to track the
> mentioned issue.
>
> Regards,
> Tommaso
>
> 20
I've created https://issues.apache.org/jira/browse/OAK-2611 to track the
mentioned issue.
Regards,
Tommaso
2015-03-12 9:36 GMT+01:00 Tommaso Teofili :
> Hi Chetan,
>
> there are 2 things at play there I think.
> First thing is that for testing purposes the suggester was configured to
> be update
Hi Chetan,
there are 2 things at play there I think.
First thing is that for testing purposes the suggester was configured to be
updated upon each commit [1], the other thing, which is a bug, is that the
code you mentioned [2] should actually check if the the "useInSuggest"
property is set before
Hi Tommaso,
Last couple of builds on Apache CI are failing in oak-lucene [1] [2].
Running the system locally reveals that quite a bit of time is being
spent in building up suggestor [3]. QueryJcrTest taking some time and
its the test which probably gets hanged in the CI build
Running org.apache.j
