Hi Michael,
Sorry for the confusion. I didn't mean System, but various types of
locales i am indexing till that point :).
Regards.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Handling-multiple-locale-tp4297805p4298170.html
Sent from the Lucene - Java Users mailing
Hi,
in my opinion your system locales have nothing to do with the analyzers
that you want to apply. I would not rely on system locales as that makes
application very unportable.
Regarding any other way - there are none. You may apply regex query and
create custom queries, but not dynamically refer
1 more question :). Are numbers analyzed ? Like IntField, LongField, etc. ?
Regards.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Handling-multiple-locale-tp4297805p4297949.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
--
Hi Michael,
Thanks for the reply. Yeah, that's one brute force way of doing it. But
then one has to find all the locales in the system. Is there any other way ?
Regards.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Handling-multiple-locale-tp4297805p4297948.html
Sent f
Hi,
please explain I get it correctly: do you want to search your query within
all possible locales? If yes then my personal pattern in such case would be
to create multiple BooleanClause (with Occur.SHOULD, one clause per each
locale) and add them to one BooleanQuery.
MW
On Sun, Sep 25, 2016 at
Hi all,
Any suggestions from the experts ? I assume, this problem is not coming
for the first time.
Regards.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Handling-multiple-locale-tp4297805p4297927.html
Sent from the Lucene - Java Users mailing list archive at Nabb
