[teiid-issues] [JBoss JIRA] (TEIID-5916) Add indexes in generated protobuf
Ramesh Reddy (Jira)
issues at jboss.org
Thu Apr 30 22:36:00 EDT 2020
[ https://issues.redhat.com/browse/TEIID-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069388#comment-14069388 ]
Ramesh Reddy commented on TEIID-5916:
-------------------------------------
>From Infinispan Documentation
NOTE
{{@IndexedField}} is deprecated in Red Hat JBoss Data Grid 7.2. However, this version of JBoss Data Grid incorrectly throws a warning that the annotation is deprecated. You can ignore the warning and use @IndexedField.
Alternatively, you can use the {{@Field}} annotation that replaces the {{@IndexedField}} annotation. However, this version of JBoss Data Grid does not support the analyze attribute for the {{@Field}} annotation.
You can replace {{@IndexedField}} annotations with {{@Field}} annotations as follows:
@IndexedField is equivalent to @Field(store=Store.YES)
@IndexedField(store=false) is equivalent to @Field`
@IndexedField(index=false, store=false) is equivalent to @Field(index=Index.NO)
> Add indexes in generated protobuf
> ---------------------------------
>
> Key: TEIID-5916
> URL: https://issues.redhat.com/browse/TEIID-5916
> Project: Teiid
> Issue Type: Enhancement
> Components: Infinispan
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 14.0
>
>
> The protobuf logic will mark an entire table as indexed, but that may not line up to what we need.
> The usage of the Indexed annotation on the message indicates that custom IndexedField annotations will be used to selective enable indexes.
> This is true whether the cache is marked as indexed (which would be specified in the cache template) or not.
> If we auto-create an indexed cache, then all fields are automatically indexed and there's no need for the indexed annotation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
More information about the teiid-issues
mailing list