[ 
https://issues.apache.org/jira/browse/SOLR-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man resolved SOLR-5594.
----------------------------

       Resolution: Fixed
    Fix Version/s: 4.7
                   5.0

Thanks Anshum!

Committed revision 1560412.
Committed revision 1560432.


> 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
>             Fix For: 5.0, 4.7
>
>         Attachments: SOLR-5594-branch_4x.patch, SOLR-5594.patch, 
> SOLR-5594.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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to