[
https://issues.apache.org/jira/browse/LUCENE-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928198#comment-15928198
]
Jim Ferenczi commented on LUCENE-7708:
--------------------------------------
[~elyograg] one shingle filter problem is fixed in LUCENE-7708 and appears in
6.3 when the support for graph analysis has been added to the QueryBuilder.
The other shingle filter problem I can think of is when the number of paths is
gigantic and produces an OOM. I opened LUCENE-7747 to fix this.
Although I think that the workaround for now is to be disable graph query
analysis when the analyzer contains a shingle filter that produces shingles of
different size. The graph analysis in this case builds all possible path since
each position has different side paths.
> Track PositionLengthAttribute abuse
> -----------------------------------
>
> Key: LUCENE-7708
> URL: https://issues.apache.org/jira/browse/LUCENE-7708
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/queryparser, modules/analysis
> Reporter: Jim Ferenczi
> Attachments: LUCENE-7708.patch, LUCENE-7708.patch
>
>
> Some token filters uses the position length attribute of the token stream to
> encode the number of terms they put in a single token.
> This breaks the query parsing because it creates disconnected graph.
> I've tracked down the abusive case to 2 candidates:
> * ShingleFilter which sets the position length attribute to the length of the
> shingle.
> * CJKBigramFilter which always sets the position length attribute to 2.
> I don't think these filters should set the position length at all so the best
> would be to remove the attribute from these token filters but this could
> break BWC.
> Though this is a serious bug since shingles and cjk bigram now produce
> invalid queries.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
