[ https://issues.apache.org/jira/browse/SOLR-5594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anshum Gupta updated SOLR-5594: ------------------------------- Attachment: SOLR-5594.patch * randomized the doc counts more (more like a 2:1 distribution). * Checked for query equality across qparsers. I haven't been able to run ant precommit yet so have just fixed "new Random()" for now. Once I figure out (or know) how to fix the EOL issue, I'll run ant precommit to fix any further issues on that front. > 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, 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org