[jira] [Commented] (SOLR-4834) Surround QParser should enable query text analysis

2014-03-16 Thread Ahmet Arslan (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13937223#comment-13937223
 ] 

Ahmet Arslan commented on SOLR-4834:


Hey [~isaachebsh], did you check LUCENE-5205 ? [~paul.elsc...@xs4all.nl] says :
bq. I think this has a lot more possibilities than the surround parser. So much 
more that this might actually replace the surround parser.

 Surround QParser should enable query text analysis
 --

 Key: SOLR-4834
 URL: https://issues.apache.org/jira/browse/SOLR-4834
 Project: Solr
  Issue Type: Improvement
  Components: query parsers
Affects Versions: 4.3
Reporter: Isaac Hebsh
  Labels: analysis, qparserplugin, surround
 Fix For: 4.8


 When using surround query parser, the query terms are not being analyzed. The 
 basic example is lower case, of course. This is probably an intended 
 behaviour, not a bug.
 I suggest one more query parameter, which determines whether to do analysis 
 or not. something like this:
 {code}
 _query_:{!surround df=myfield analyze=true}SpinPoint 7n GB18030
 {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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



[jira] [Commented] (SOLR-4834) Surround QParser should enable query text analysis

2013-05-21 Thread Isaac Hebsh (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13663306#comment-13663306
 ] 

Isaac Hebsh commented on SOLR-4834:
---

Hi [~paul.elsc...@xs4all.nl].
I understand that this is not a bug, and that it's documented.
Thank you for the advice, I'll try it soon...

 Surround QParser should enable query text analysis
 --

 Key: SOLR-4834
 URL: https://issues.apache.org/jira/browse/SOLR-4834
 Project: Solr
  Issue Type: Improvement
  Components: query parsers
Affects Versions: 4.3
Reporter: Isaac Hebsh
  Labels: analysis, qparserplugin, surround
 Fix For: 5.0, 4.4


 When using surround query parser, the query terms are not being analyzed. The 
 basic example is lower case, of course. This is probably an intended 
 behaviour, not a bug.
 I suggest one more query parameter, which determines whether to do analysis 
 or not. something like this:
 {code}
 _query_:{!surround df=myfield analyze=true}SpinPoint 7n GB18030
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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



[jira] [Commented] (SOLR-4834) Surround QParser should enable query text analysis

2013-05-20 Thread Paul Elschot (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662263#comment-13662263
 ] 

Paul Elschot commented on SOLR-4834:


From the Lucene In Action book, 2nd edition:

{quote}
Unlike the standard QueryParser, the Surround parser doesn’t use an analyzer.
This means that the user will have to know precisely how terms are indexed. For
indexing texts to be queried by the Surround language, we recommend that you 
use a
lowercasing analyzer that removes only the most frequently occurring 
punctuations.
{quote}

Nevertheless, to use an analyzer for the queries, one can override some of the 
protected methods of the Surround QueryParser to use the analyzer.

 Surround QParser should enable query text analysis
 --

 Key: SOLR-4834
 URL: https://issues.apache.org/jira/browse/SOLR-4834
 Project: Solr
  Issue Type: Improvement
  Components: query parsers
Affects Versions: 4.3
Reporter: Isaac Hebsh
  Labels: analysis, qparserplugin, surround
 Fix For: 5.0, 4.4


 When using surround query parser, the query terms are not being analyzed. The 
 basic example is lower case, of course. This is probably an intended 
 behaviour, not a bug.
 I suggest one more query parameter, which determines whether to do analysis 
 or not. something like this:
 {code}
 _query_:{!surround df=myfield analyze=true}SpinPoint 7n GB18030
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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