seems like you forgot to do facetsConfig.setMultiValued(`field`, true) too .
On Sat, Apr 25, 2015 at 7:37 AM, Gimantha Bandara wrote:
> Hi,
>
> I was able to fix the problem.. the issue was with my wrong usage of
> FacetConfig class. I was creating Document using facetConfig.build per each
> fac
Hi,
I was able to fix the problem.. the issue was with my wrong usage of
FacetConfig class. I was creating Document using facetConfig.build per each
facet field with new FacetConfig object per each facetfield.
Solution was to use one global FacetConfig per document add the facetfields
to the docu
Hello Uwe Schindler,
Ah, Yes.
You are right.
5.x removed that message file.
I am still in 4.x. ( 4.10.4 has this file ) so far.
Thanks for your kind consideration.
Youngho
2015-04-25 18:13 GMT+09:00 Uwe Schindler :
> Hi,
>
> I checked the source codes of Lucene, there is no such warning anym
Hi,
I checked the source codes of Lucene, there is no such warning anymore. Which
version do you use and in which file did you find the warning? In any case, for
older versions of Lucene you should really use the version mentioned there to
regenerate, to be sure the behavior of the Tokenizer is
Hi,
the documentation is this file is not really up-to-date.
If you want to regenerate the jflex files, it is recommended to use the build
script of Lucene. If you type "ant regenerate" or "ant jflex" (in the folder of
the analysis module), the build system will download the correct version of
I'll give it a try. Any plans for luke to support Lucene 5.x, too?
-Ursprüngliche Nachricht-
Von: Koji Sekiguchi [mailto:koji.sekigu...@rondhuit.com]
Gesendet: Freitag, 24. April 2015 08:23
An: java-user@lucene.apache.org
Betreff: Re: Luke for Lucene 5.x?
Hi Clemens,
NLP4L, which stands
