[infinispan-issues] [JBoss JIRA] (ISPN-3718) Select which protobuf fields to index

[Sanne Grinovero (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12944765#comment-12944765 ] 

Sanne Grinovero commented on ISPN-3718:
---------------------------------------

yes it's looking like a valid approach.
It's definitely interesting for the more advanced use cases, but I think our priority is to minimize indexing cost for the simple (most common) use cases.

I've written some thoughts on the mailing list about a no-metadata approach which would infer what needs to be indexed from a set of pre-defined queries. Imagine the user has to list all "SQL" queries it intends to run upfront, and from there we simply infer what kinds of indexing options are needed.
My aim is of course simplification of developers experience.

Having this metadata in protobuf would of course still be needed, but would be less of a priority.

http://lists.jboss.org/pipermail/infinispan-dev/2014-February/014537.html
                
> Select which protobuf fields to index
> -------------------------------------
>
>                 Key: ISPN-3718
>                 URL: https://issues.jboss.org/browse/ISPN-3718
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Embedded 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