>
> [1]
> @AnalyzerDef(name = "entityAnalyser",
> tokenizer = @TokenizerDef(factory = StandardTokenizerFactory.class),
> filters = { @TokenFilterDef(factory = StandardFilterFactory.class),
> @TokenFilterDef(factory = LowerCaseFilterFactory.class),
> @TokenFilt
2011/5/12 Emmanuel Bernard :
> 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?
yes actually some people on the forum where asking about how to enable
logging on tokeni
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
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, a
2011/5/11 Hardy Ferentschik :
> +1 - this thought crossed my mind before as well.
Created HSEARCH-749
> As a continuation I thought about it would be nice to be able analyze a
> sentence in the JMX console. This ties a little in with the ability of
> a meta data api which would allow to get more
+1 - this thought crossed my mind before as well.
As a continuation I thought about it would be nice to be able analyze a
sentence in the JMX console. This ties a little in with the ability of
a meta data api which would allow to get more information about the
indexed fields. Anyways, just day dre
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 thi
