Yes, of course. It's here: https://issues.apache.org/jira/browse/LUCENE-8723
Thanks.
El 12/3/19 a las 12:59, Michael McCandless escribió:
Hello Nicolás,
Can you please open an issue for this? Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Mar 7, 2019 at 10:08 PM Nicolás Li
I've created a Jira issue for this here:
https://issues.apache.org/jira/browse/LUCENE-8723
El 8/3/19 a las 00:08, Nicolás Lichtmaier escribió:
Oops, sorry... in that code there's a "camelCase" parameter that is
not implemented in normal Lucene. That is an option I've added for
better camel c
Hello Nicolás,
Can you please open an issue for this? Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Mar 7, 2019 at 10:08 PM Nicolás Lichtmaier
wrote:
> Oops, sorry... in that code there's a "camelCase" parameter that is not
> implemented in normal Lucene. That is an option
Oops, sorry... in that code there's a "camelCase" parameter that is not
implemented in normal Lucene. That is an option I've added for better
camel case support, but the bug happens without that option as well.
El 7/3/19 a las 20:33, Nicolás Lichtmaier escribió:
After a lot of time... Here's
After a lot of time... Here's an small example that triggers that assertion.
Builder builder = CustomAnalyzer.builder();
builder.withTokenizer(StandardTokenizerFactory.class);
builder.addTokenFilter(WordDelimiterGraphFilterFactory.class,
"camelCase", "1", "preserveOrigin
Hmm, that's not good! Clearly there is a bug somewhere.
Are you able to isolate a small example, e.g. text input and synonyms you
fed to SynonymGraphFilter, to show this assertion trip?
Are you using any custom analysis components before the FlattenGraphFilter?
Mike McCandless
http://blog.mike
Hi!
I was getting an exception in FlattenGraphFilter and, as I saw there was
assertion statements nearby, I reran everything with assertions enabled.
And I see it crashes here (FlattenGraphFilter.java:174)
At this point inputNode has all fields with -1 (except nextOut, which is
0).. and out
