[
https://issues.apache.org/jira/browse/SOLR-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118078#comment-14118078
]
Alexander S. commented on SOLR-6468:
------------------------------------
Correct, but isn't this behavior deprecated? I mean matchVersion="4.3"? I was
told this could get removed from 5.0 as well.
If I do understand the problem correctly enablePositionIncrements="false" could
generate wrong tokens for those who do not know how to use this option
correctly? It seems it requires a custom tokenizer and
solr.PatternTokenizerFactory in my example should work properly. So instead of
removing the option the problem with wrong tokens could be explained in the
readme and the option could be kept for those who really needs it. That makes
more sense to me than simply removing it.
Anyway, is there any chance the option could be restored? My usecase should
clearly show how useful it might be. And I was trying to google the problem,
there's a lot of complaints about this, but no solutions.
> Regression: StopFilterFactory doesn't work properly without
> enablePositionIncrements="false"
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-6468
> URL: https://issues.apache.org/jira/browse/SOLR-6468
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.8.1, 4.9
> Reporter: Alexander S.
>
> Setup:
> * Schema version is 1.5
> * Field config:
> {code}
> <fieldType name="words_ngram" class="solr.TextField" omitNorms="false"
> autoGeneratePhraseQueries="true">
> <analyzer>
> <tokenizer class="solr.PatternTokenizerFactory" pattern="[^\w]+" />
> <filter class="solr.StopFilterFactory" words="url_stopwords.txt"
> ignoreCase="true" />
> <filter class="solr.LowerCaseFilterFactory" />
> </analyzer>
> </fieldType>
> {code}
> * Stop words:
> {code}
> http
> https
> ftp
> www
> {code}
> So very simple. In the index I have:
> * twitter.com/testuser
> All these queries do match:
> * twitter.com/testuser
> * com/testuser
> * testuser
> But none of these does:
> * https://twitter.com/testuser
> * https://www.twitter.com/testuser
> * www.twitter.com/testuser
> Debug output shows:
> "parsedquery_toString": "+(url_words_ngram:\"? twitter com testuser\")"
> But we need:
> "parsedquery_toString": "+(url_words_ngram:\"twitter com testuser\")"
> Complete debug outputs:
> * a valid search:
> http://pastie.org/pastes/9500661/text?key=rgqj5ivlgsbk1jxsudx9za
> * an invalid search:
> http://pastie.org/pastes/9500662/text?key=b4zlh2oaxtikd8jvo5xaww
> The complete discussion and explanation of the problem is here:
> http://lucene.472066.n3.nabble.com/Help-with-StopFilterFactory-td4153839.html
> I didn't find a clear explanation how can we upgrade Solr, there's no any
> replacement or a workarround to this, so this is not just a major change but
> a major disrespect to all existing Solr users who are using this feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
