[infinispan-issues] [JBoss JIRA] (ISPN-3718) Select which protobuf fields to index
Sanne Grinovero (JIRA)
jira-events at lists.jboss.org
Tue Dec 10 05:51:06 EST 2013
[ https://issues.jboss.org/browse/ISPN-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929769#comment-12929769 ]
Sanne Grinovero commented on ISPN-3718:
---------------------------------------
The indexing option is not just a yes/no, we also need to specify if:
- if the value should be stored for projection capabilities
- keep in mind if range queries are to be supported (padding of numbers?)
- compression of stored fields
We probably want to keep it extensible, the day we want to expose full-text capabilities we'll need to know if:
- fuzzy vs exact matches are needed
- if a specific Analyzer (by name?) is needed
- boosting & co ?
> Select which protobuf fields to index
> -------------------------------------
>
> Key: ISPN-3718
> URL: https://issues.jboss.org/browse/ISPN-3718
> Project: Infinispan
> Issue Type: Feature Request
> Components: Querying
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
>
> Currently we index all fields. An interesting idea is to use a custom protobuf Option (see 'Custom Options' section here https://developers.google.com/protocol-buffers/docs/proto) to indicate which message types and specifically which fields should be indexed, similar to Hibernate Search annotations.
--
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
More information about the infinispan-issues
mailing list