[hibernate-dev] Deprecating configurability of "hibernate.search.worker.scope" ?

Sanne Grinovero sanne at hibernate.org
Thu Jul 11 10:47:55 EDT 2013


On 11 July 2013 15:29, Hardy Ferentschik <hardy at hibernate.org> wrote:
> I find them confusing as well and cannot thing of an actual use case.
> I assume you are removing the hibernate.search.worker.* settings as well, right?

Partly: we still need the options which apply to our "one and only"
implementation, the TransactionalWorker

To be clear, those defined in

    Table 3.3. Execution configuration

should stay.

Right?

Sanne


>
> if so +1
>
> --Hardy
>
>
> On 11 Jan 2013, at 4:04 PM, Sanne Grinovero <sanne at hibernate.org> wrote:
>
>> I'm wondering if this property is really useful. Someone has a
>> practical example in which he would need it?
>>
>> http://docs.jboss.org/hibernate/search/4.3/reference/en-US/html_single/#table-worker-configuration
>>
>> I'm tempted to deprecate it and remove the description from the
>> documentation as so far I've only seen people asking clarifications
>> about it, to then conclude they don't need this (or more likely didn't
>> understand it and decide to stay away from it).
>>
>> We could technically leave the loading code in place, it's just the
>> documentation which is troubling me.
>>
>> Cheers,
>> Sanne
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>


More information about the hibernate-dev mailing list