You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2018/01/22 07:37:00 UTC

[jira] [Commented] (LUCENE-8132) HyphenationDecompoundTokenFilter does not set position/offset attributes correctly

    [ https://issues.apache.org/jira/browse/LUCENE-8132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333962#comment-16333962 ] 

Adrien Grand commented on LUCENE-8132:
--------------------------------------

I agree this sounds wrong. Unfortunately, inserting positions in a token filter is hard to do right if the analysis chain has a preceding token filter that sets synonyms, as you need to fix positions on all paths. This issue touches this problem a bit: LUCENE-5012.

> HyphenationDecompoundTokenFilter does not set position/offset attributes correctly
> ----------------------------------------------------------------------------------
>
>                 Key: LUCENE-8132
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8132
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/analysis
>    Affects Versions: 6.6.1, 7.2.1
>            Reporter: Holger Bruch
>            Priority: Major
>
> HyphenationDecompoundTokenFilter and DictionaryDecompoundTokenFilter set positionIncrement to 0 for all subwords, reuse start/endoffset of the original token and ignore positionLength completly.
> In consequence, the QueryBuilder generates a SynonymQuery comprising all subwords, which should rather treated as individual terms.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org