[hibernate-dev] providing AnalyzerUtils in Hibernate Search
emmanuel at hibernate.org
Thu May 12 10:56:16 EDT 2011
Sorry I replied too fast, I see the usecase.
Do you think proper logging in our part (of the analyzer work) could solve the issue without people having to use AnalyzerUtils?
For example I'm not a big fan of the fact that AnalyzerUtils plays at the string level whereas HSearch plays at the object property level.
On 12 mai 2011, at 16:54, Emmanuel Bernard wrote:
> In which case do you recommend people to write something like that?
> Is that related to any use of Hibernate Search?
> Also it seems not all methods as they are make sense, for example display pushing to log is not likely going to be something users want in this form necessarily.
> On 11 mai 2011, at 17:45, Sanne Grinovero wrote:
>> We're using AnalyzerUtils in some of the tests in Hibernate Search,
>> but I'm finding myself recommending people to "write something like
>> that" quite often lately, it seems that otherwise people have an hard
>> time to figure if their analyzer definitions make any sense.
>> What do you think in moving this class into the main jar, polish the
>> javadoc a bit and add a note on how to check your analyzer in the
>> hibernate-dev mailing list
>> hibernate-dev at lists.jboss.org
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
More information about the hibernate-dev