In my first draft for HSEARCH-1296 I was automatically enabling the
blocking behaviour on JGroups if the worker backend was configured to
be synchronous (which is the default for workers),
but Emmanuel didn't like that and I think he has a good point:
The JGroups behaviour and the workers behaviou
There's been several complaints about ORM's use of Gradle not generating
Eclipse projects correctly. This was recently cleaned up in HHH-7617 [1].
FYI, there's a quick blog post [2] about how to quickly get up-and-running.
Please let me know if there are any further ways we could streamline t
Hi Brett,
That's good news, thanks for your efforts. Based on step 3 from your blog
post it seems as there still is a circular dependency between some of the
modules/projects. Just out of interest, could you give some more details
why this kind of setup is required?
--Gunnar
2013/4/15 Brett Me
I am not touching this :)
I think I have explained this 198,052 times thus far lol
https://community.jboss.org/wiki/GradleWhy see #4
On 04/15/2013 04:10 PM, Gunnar Morling wrote:
> Hi Brett,
>
> That's good news, thanks for your efforts. Based on step 3 from your blog
> post it seems as there st
What's (again) the magic property to set all indexes backends in a cache to
async?
-Ales
On Apr 15, 2013, at 7:00 PM, Sanne Grinovero wrote:
> In my first draft for HSEARCH-1296 I was automatically enabling the
> blocking behaviour on JGroups if the worker backend was configured to
> be synchr
Applies to all backends:
"hibernate.search.default.worker.execution" "async"
Then override the above per specific index which needs to be sync :
"hibernate.search.books.worker.execution" "sync"
On 15 April 2013 22:37, Ales Justin wrote:
> What's (again) the magic property to set all indexes bac
