You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Anshum Gupta (JIRA)" <ji...@apache.org> on 2014/01/21 16:17:20 UTC
[jira] [Comment Edited] (SOLR-5594) Enable using extended field
types with prefix queries for non-default encoded strings
[ https://issues.apache.org/jira/browse/SOLR-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877521#comment-13877521 ]
Anshum Gupta edited comment on SOLR-5594 at 1/21/14 3:15 PM:
-------------------------------------------------------------
Hoss: Thanks for taking that up before I got back.
bq. Yes, this would also be identical to range query behaviour: newRangeQuery also delegates to the field type, and the protected method is there for subclasses.
My changes are Solr specific. I'm not sure how would it play with the Solr QParsers (Solr extended fields) if I moved the changes to Lucene instead of Solr.
was (Author: anshumg):
Thanks for taking that up before I got back.
bq. Yes, this would also be identical to range query behaviour: newRangeQuery also delegates to the field type, and the protected method is there for subclasses.
My changes are Solr specific. I'm not sure how would it play with the Solr QParsers (Solr extended fields) if I moved the changes to Lucene instead of Solr.
> Enable using extended field types with prefix queries for non-default encoded strings
> -------------------------------------------------------------------------------------
>
> Key: SOLR-5594
> URL: https://issues.apache.org/jira/browse/SOLR-5594
> Project: Solr
> Issue Type: Improvement
> Components: query parsers, Schema and Analysis
> Affects Versions: 4.6
> Reporter: Anshum Gupta
> Assignee: Anshum Gupta
> Priority: Minor
> Attachments: SOLR-5594-branch_4x.patch, SOLR-5594.patch, SOLR-5594.patch, SOLR-5594.patch, SOLR-5594.patch
>
>
> Enable users to be able to use prefix query with custom field types with non-default encoding/decoding for queries more easily. e.g. having a custom field work with base64 encoded query strings.
> Currently, the workaround for it is to have the override at getRewriteMethod level. Perhaps having the prefixQuery also use the calling FieldType's readableToIndexed method would work better.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org