You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2010/01/12 20:40:54 UTC
[jira] Created: (SOLR-1719) stock TokenFilterFactory for flattening
positions
stock TokenFilterFactory for flattening positions
-------------------------------------------------
Key: SOLR-1719
URL: https://issues.apache.org/jira/browse/SOLR-1719
Project: Solr
Issue Type: Wish
Reporter: Hoss Man
People seem to occasionally be confused by why certain inputs result in PhraseQueries instead of BooleanQueries...
http://old.nabble.com/Understanding-the-query-parser-to27071483.html
http://old.nabble.com/Tokenizer-question-to27099119.html
...it would probably be handy if there was a TokenFilterFactory provided out of the box that just set the positionIncrement of every token to "0" to deal with situations where people don't care about term positions at query time, and are just using tokenization/analysis as a way to split up some input string into multiple "SHOULD" clauses for a BooleanQuery
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-1719) stock TokenFilterFactory for
flattening positions
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-1719.
----------------------------
Resolution: Not A Problem
Indeed
I thought we had something like that, but overlooked it when i went looking, so i opened this issue.
> stock TokenFilterFactory for flattening positions
> -------------------------------------------------
>
> Key: SOLR-1719
> URL: https://issues.apache.org/jira/browse/SOLR-1719
> Project: Solr
> Issue Type: Wish
> Reporter: Hoss Man
>
> People seem to occasionally be confused by why certain inputs result in PhraseQueries instead of BooleanQueries...
> http://old.nabble.com/Understanding-the-query-parser-to27071483.html
> http://old.nabble.com/Tokenizer-question-to27099119.html
> ...it would probably be handy if there was a TokenFilterFactory provided out of the box that just set the positionIncrement of every token to "0" to deal with situations where people don't care about term positions at query time, and are just using tokenization/analysis as a way to split up some input string into multiple "SHOULD" clauses for a BooleanQuery
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1719) stock TokenFilterFactory for
flattening positions
Posted by "Otis Gospodnetic (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802342#action_12802342 ]
Otis Gospodnetic commented on SOLR-1719:
----------------------------------------
Does PositionFilterFactory fix the problem?
> stock TokenFilterFactory for flattening positions
> -------------------------------------------------
>
> Key: SOLR-1719
> URL: https://issues.apache.org/jira/browse/SOLR-1719
> Project: Solr
> Issue Type: Wish
> Reporter: Hoss Man
>
> People seem to occasionally be confused by why certain inputs result in PhraseQueries instead of BooleanQueries...
> http://old.nabble.com/Understanding-the-query-parser-to27071483.html
> http://old.nabble.com/Tokenizer-question-to27099119.html
> ...it would probably be handy if there was a TokenFilterFactory provided out of the box that just set the positionIncrement of every token to "0" to deal with situations where people don't care about term positions at query time, and are just using tokenization/analysis as a way to split up some input string into multiple "SHOULD" clauses for a BooleanQuery
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.