[Red Hat JIRA] (ISPN-12534) CacheConfigurationException message ISPN028021 should return that it is missing an annotation in the field
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-12534?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-12534:
--------------------------------
Fix Version/s: 12.0.0.Final
Resolution: Done
Status: Resolved (was: Pull Request Sent)
> CacheConfigurationException message ISPN028021 should return that it is missing an annotation in the field
> ----------------------------------------------------------------------------------------------------------
>
> Key: ISPN-12534
> URL: https://issues.redhat.com/browse/ISPN-12534
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 12.0.0.CR1
> Reporter: Diego Lovison
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 12.0.0.Final
>
> Attachments: query.diff
>
>
> When creating a cache with an indexed entity with the wrong configuration. Infinispan is returning the wrong message.
> If the java class has the following content.
> {code:java}
> @Indexed
> @ProtoDoc("@Indexed")
> public static final class User {
> @ProtoField(number = 1)
> Long id;
> @ProtoField(number = 2)
> String name;
> }
> {code}
> When creating a cache, the server is returning
> {noformat}
> Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=10 returned server error (status=0x85): org.infinispan.commons.CacheConfigurationException: ISPN028021: The configured indexed-entity type 'black_friday.User' must be indexed. Please annotate it with @Indexed or remove it from the configuration.
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:335)
> {noformat}
> As you can see, the entity has the @Indexed annotation.
> What is missing is the @ProtoDoc annotation in the field, as the following
> {code:java}
> @Indexed
> @ProtoDoc("@Indexed")
> public static final class User {
> @ProtoDoc("@Field(index=Index.YES, analyze = Analyze.YES, store = Store.NO)")
> @ProtoField(number = 1)
> Long id;
> @ProtoField(number = 2)
> String name;
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12612) Remove recent activity table
by Katia Aresti (Jira)
Katia Aresti created ISPN-12612:
-----------------------------------
Summary: Remove recent activity table
Key: ISPN-12612
URL: https://issues.redhat.com/browse/ISPN-12612
Project: Infinispan
Issue Type: Enhancement
Components: Console
Affects Versions: 12.0.0.CR1
Reporter: Katia Aresti
Assignee: Katia Aresti
Remove unnecessary recent activity table for the cache
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12610) Fix protobuf display and modification
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-12610?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-12610:
--------------------------------
Description:
Some changes introduced in the console make protobuf entities not be able to be displayed
When we add an entity that is not a simple data type (protoschema associated object) the entries list won't display because this is not correctly handled in the console.
with this fix, entries are listed and we can edit and delete them
was:Some changes introduced in the console make protobuf entities not be able to be displayed
> Fix protobuf display and modification
> -------------------------------------
>
> Key: ISPN-12610
> URL: https://issues.redhat.com/browse/ISPN-12610
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 12.0.0.CR1
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Blocker
>
> Some changes introduced in the console make protobuf entities not be able to be displayed
> When we add an entity that is not a simple data type (protoschema associated object) the entries list won't display because this is not correctly handled in the console.
> with this fix, entries are listed and we can edit and delete them
>
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months