On Thu, Mar 1, 2012 at 2:59 PM, Sanne Grinovero wrote:
> I understood you where doing something crazy like that :D
> My question is, this additional API would be pointless assuming we fix
> HSEARCH-598?
>
> Or we add an option like:
>
> fullTextSession.createIndexer().processTypesSequentially().st
On 1 March 2012 13:46, Guillaume Smet wrote:
> Hi Sanne,
>
> On Thu, Mar 1, 2012 at 1:09 PM, Sanne Grinovero wrote:
>> I'm aware of the issue, and I wouldn't mind some help on it: it would
>> be better to fix the MassIndexer design to use a limited set of
>> threads than to expose more metadata i
Hi Sanne,
On Thu, Mar 1, 2012 at 1:09 PM, Sanne Grinovero wrote:
> I'm aware of the issue, and I wouldn't mind some help on it: it would
> be better to fix the MassIndexer design to use a limited set of
> threads than to expose more metadata information, don't you agree?
>
> The reason for me to
Hi Guillaume,
I'm aware of the issue, and I wouldn't mind some help on it: it would
be better to fix the MassIndexer design to use a limited set of
threads than to expose more metadata information, don't you agree?
The reason for me to not have given a high priority to HSEARCH-598 are
1) there a
