[Red Hat JIRA] (ISPN-12605) REST event listeners
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12605?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12605:
-----------------------------------
Description:
Add event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
h3. Cache listeners:
{{GET /v2/caches/cacheName?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of cache events.
Each event follows the following structure:
{noformat}
event: [created|modified|removed|expired]
data: [json representantion of event]
{noformat}
the data field will contain a JSON representation of the event:
{code:json}
{
key: {},
value: {},
metadata: {}
}
{code}
was:
Add event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
For cache listeners:
{{GET /v2/caches/cacheName?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of cache events.
Each event follows the following structure:
{noformat}
event: [created|modified|removed|expired]
data: [json representantion of event]
{noformat}
the data field will contain a JSON representation of the event:
{code:json}
{
key: {},
value: {},
metadata: {}
}
{code}
> REST event listeners
> --------------------
>
> Key: ISPN-12605
> URL: https://issues.redhat.com/browse/ISPN-12605
> Project: Infinispan
> Issue Type: Feature Request
> Components: Listeners, REST, Server
> Reporter: Tristan Tarrant
> Priority: Major
>
> Add event listeners to the REST endpoint.
> These should use HTTP Server-Sent-Events
> [https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
> h3. Cache listeners:
> {{GET /v2/caches/cacheName?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
> This will result in a response with content-type text/event-stream followed by a stream of cache events.
> Each event follows the following structure:
> {noformat}
> event: [created|modified|removed|expired]
> data: [json representantion of event]
> {noformat}
> the data field will contain a JSON representation of the event:
> {code:json}
> {
> key: {},
> value: {},
> metadata: {}
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12605) REST event listeners
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12605?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12605:
-----------------------------------
Description:
Add event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
For cache listeners:
{{GET /v2/caches/cacheName?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of cache events.
Each event follows the following structure:
{noformat}
event: [created|modified|removed|expired]
data: [json representantion of event]
{noformat}
the data field will contain a JSON representation of the event:
{code:json}
{
key: {},
value: {},
metadata: {}
}
{code}
was:
Add event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
For cache listeners:
{{GET /v2/caches/{cacheName}?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of cache events.
Each event follows the following structure:
{noformat}
event: [created|modified|removed|expired]
data: [json representantion of event]
{noformat}
the data field will contain a JSON representation of the event:
{code:json}
{
key: {},
value: {},
metadata: {}
}
{code}
> REST event listeners
> --------------------
>
> Key: ISPN-12605
> URL: https://issues.redhat.com/browse/ISPN-12605
> Project: Infinispan
> Issue Type: Feature Request
> Components: Listeners, REST, Server
> Reporter: Tristan Tarrant
> Priority: Major
>
> Add event listeners to the REST endpoint.
> These should use HTTP Server-Sent-Events
> [https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
> For cache listeners:
> {{GET /v2/caches/cacheName?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
> This will result in a response with content-type text/event-stream followed by a stream of cache events.
> Each event follows the following structure:
> {noformat}
> event: [created|modified|removed|expired]
> data: [json representantion of event]
> {noformat}
> the data field will contain a JSON representation of the event:
> {code:json}
> {
> key: {},
> value: {},
> metadata: {}
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12605) REST event listeners
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12605?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12605:
-----------------------------------
Description:
Add event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
For cache listeners:
{{GET /v2/caches/{cacheName}?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of cache events.
Each event follows the following structure:
{noformat}
event: [created|modified|removed|expired]
data: [json representantion of event]
{noformat}
the data field will contain a JSON representation of the event:
{code:json}
{
key: {},
value: {},
metadata: {}
}
{code}
was:
Add event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
For cache listeners:
{{GET /v2/caches/{cacheName}?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]
}}
This will result in a response with content-type text/event-stream followed by a stream of cache events.
Each event follows the following structure:
{noformat}
event: [created|modified|removed|expired]
data: [json representantion of event]
{noformat}
the data field will contain a JSON representation of the event:
{code:json}
{
key: {},
value: {},
metadata: {}
}
{code}
> REST event listeners
> --------------------
>
> Key: ISPN-12605
> URL: https://issues.redhat.com/browse/ISPN-12605
> Project: Infinispan
> Issue Type: Feature Request
> Components: Listeners, REST, Server
> Reporter: Tristan Tarrant
> Priority: Major
>
> Add event listeners to the REST endpoint.
> These should use HTTP Server-Sent-Events
> [https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
> For cache listeners:
> {{GET /v2/caches/{cacheName}?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]}}
> This will result in a response with content-type text/event-stream followed by a stream of cache events.
> Each event follows the following structure:
> {noformat}
> event: [created|modified|removed|expired]
> data: [json representantion of event]
> {noformat}
> the data field will contain a JSON representation of the event:
> {code:json}
> {
> key: {},
> value: {},
> metadata: {}
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12605) REST event listeners
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-12605:
--------------------------------------
Summary: REST event listeners
Key: ISPN-12605
URL: https://issues.redhat.com/browse/ISPN-12605
Project: Infinispan
Issue Type: Feature Request
Components: Listeners, REST, Server
Reporter: Tristan Tarrant
Add event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
For cache listeners:
{{GET /v2/caches/{cacheName}?action=listen[&includeCurrentState=true|false][&filterFactoryName=...][&converterFactoryName=...][&includeMetadata=true|false]
}}
This will result in a response with content-type text/event-stream followed by a stream of cache events.
Each event follows the following structure:
{noformat}
event: [created|modified|removed|expired]
data: [json representantion of event]
{noformat}
the data field will contain a JSON representation of the event:
{code:json}
{
key: {},
value: {},
metadata: {}
}
{code}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12533) Infinispan is registering Query interceptor when the client cache creation is invalid
by Diego Lovison (Jira)
[ https://issues.redhat.com/browse/ISPN-12533?page=com.atlassian.jira.plugi... ]
Diego Lovison commented on ISPN-12533:
--------------------------------------
Thanks for the details.
Cheers
> Infinispan is registering Query interceptor when the client cache creation is invalid
> -------------------------------------------------------------------------------------
>
> Key: ISPN-12533
> URL: https://issues.redhat.com/browse/ISPN-12533
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 12.0.0.Dev07
> Reporter: Diego Lovison
> Assignee: Gustavo Fernandes
> Priority: Major
> Attachments: query.diff
>
>
> Build the Infinispan and run {{server.sh}}
> Run the client. It will fail because there is a missing configuration.
> {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}
> Check the server console ( or the server log )
> {noformat}
> the server is registering
> 11:46:34,952 INFO (blocking-thread--p3-t1) [org.infinispan.CONTAINER] ISPN014003: Registering Query interceptor for cache user
> {noformat}
> Stop the server with ctrl + c
> {noformat}
> 11:48:44,318 WARN (Thread-0) [org.infinispan.CONTAINER] ISPN000189: While stopping a cache or cache manager, one of its components failed to stop java.util.concurrent.CompletionException: 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 java.base/java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:412)
> at java.base/java.util.concurrent.CompletableFuture.join(CompletableFuture.java:2044)
> at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:780)
> at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:841)
> at org.infinispan.manager.DefaultCacheManager.internalStop(DefaultCacheManager.java:817)
> at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:793)
> at org.infinispan.server.SecurityActions.lambda$stopCacheManager$2(SecurityActions.java:75)
> at org.infinispan.security.Security.doPrivileged(Security.java:45)
> at org.infinispan.server.SecurityActions.doPrivileged(SecurityActions.java:38)
> at org.infinispan.server.SecurityActions.stopCacheManager(SecurityActions.java:81)
> at java.base/java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:608)
> at org.infinispan.server.Server.localShutdown(Server.java:484)
> at org.infinispan.server.Server.lambda$run$1(Server.java:410)
> at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at org.infinispan.server.DefaultExitHandler.exit(DefaultExitHandler.java:13)
> at org.infinispan.server.ShutdownHook.run(ShutdownHook.java:16)
> Caused by: org.infinispan.commons.Cac^CheManager.internalGetCache(DefaultCacheManager.java:532)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:510)
> at org.infinispan.security.actions.GetCacheAction.run(GetCacheAction.java:26)
> at org.infinispan.security.actions.GetCacheAction.run(GetCacheAction.java:14)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12533) Infinispan is registering Query interceptor when the client cache creation is invalid
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12533?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes commented on ISPN-12533:
------------------------------------------
No, because it is always registered in the query module (loaded first), and we can only know if it's valid after the remote-query module is activated.
Regarding rollback, it can't be done unless it is yet registered again. Imagine a cache where the protobuf entity is incomplete, so it errors, we don't install the QueryInterceptor, but then the protobuf is fixed: we would somehow need to trigger the reinstallation of the interceptor. TL,DR: let's not bother about it :)
> Infinispan is registering Query interceptor when the client cache creation is invalid
> -------------------------------------------------------------------------------------
>
> Key: ISPN-12533
> URL: https://issues.redhat.com/browse/ISPN-12533
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 12.0.0.Dev07
> Reporter: Diego Lovison
> Assignee: Gustavo Fernandes
> Priority: Major
> Attachments: query.diff
>
>
> Build the Infinispan and run {{server.sh}}
> Run the client. It will fail because there is a missing configuration.
> {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}
> Check the server console ( or the server log )
> {noformat}
> the server is registering
> 11:46:34,952 INFO (blocking-thread--p3-t1) [org.infinispan.CONTAINER] ISPN014003: Registering Query interceptor for cache user
> {noformat}
> Stop the server with ctrl + c
> {noformat}
> 11:48:44,318 WARN (Thread-0) [org.infinispan.CONTAINER] ISPN000189: While stopping a cache or cache manager, one of its components failed to stop java.util.concurrent.CompletionException: 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 java.base/java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:412)
> at java.base/java.util.concurrent.CompletableFuture.join(CompletableFuture.java:2044)
> at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:780)
> at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:841)
> at org.infinispan.manager.DefaultCacheManager.internalStop(DefaultCacheManager.java:817)
> at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:793)
> at org.infinispan.server.SecurityActions.lambda$stopCacheManager$2(SecurityActions.java:75)
> at org.infinispan.security.Security.doPrivileged(Security.java:45)
> at org.infinispan.server.SecurityActions.doPrivileged(SecurityActions.java:38)
> at org.infinispan.server.SecurityActions.stopCacheManager(SecurityActions.java:81)
> at java.base/java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:608)
> at org.infinispan.server.Server.localShutdown(Server.java:484)
> at org.infinispan.server.Server.lambda$run$1(Server.java:410)
> at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at org.infinispan.server.DefaultExitHandler.exit(DefaultExitHandler.java:13)
> at org.infinispan.server.ShutdownHook.run(ShutdownHook.java:16)
> Caused by: org.infinispan.commons.Cac^CheManager.internalGetCache(DefaultCacheManager.java:532)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:510)
> at org.infinispan.security.actions.GetCacheAction.run(GetCacheAction.java:26)
> at org.infinispan.security.actions.GetCacheAction.run(GetCacheAction.java:14)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12604) Remove HR 1.0 from reference doc
by Donald Naro (Jira)
Donald Naro created ISPN-12604:
----------------------------------
Summary: Remove HR 1.0 from reference doc
Key: ISPN-12604
URL: https://issues.redhat.com/browse/ISPN-12604
Project: Infinispan
Issue Type: Enhancement
Components: Documentation
Affects Versions: 12.0.0.Dev07
Reporter: Donald Naro
Assignee: Donald Naro
HR 1.0 was deprecated in 9.4.x. Need to remove this from the docs for 10.0.x +
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12533) Infinispan is registering Query interceptor when the client cache creation is invalid
by Diego Lovison (Jira)
[ https://issues.redhat.com/browse/ISPN-12533?page=com.atlassian.jira.plugi... ]
Diego Lovison commented on ISPN-12533:
--------------------------------------
Could we register only if it is valid or Could we unregister if it is invalid ( like rollback )?
> Infinispan is registering Query interceptor when the client cache creation is invalid
> -------------------------------------------------------------------------------------
>
> Key: ISPN-12533
> URL: https://issues.redhat.com/browse/ISPN-12533
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 12.0.0.Dev07
> Reporter: Diego Lovison
> Assignee: Gustavo Fernandes
> Priority: Major
> Attachments: query.diff
>
>
> Build the Infinispan and run {{server.sh}}
> Run the client. It will fail because there is a missing configuration.
> {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}
> Check the server console ( or the server log )
> {noformat}
> the server is registering
> 11:46:34,952 INFO (blocking-thread--p3-t1) [org.infinispan.CONTAINER] ISPN014003: Registering Query interceptor for cache user
> {noformat}
> Stop the server with ctrl + c
> {noformat}
> 11:48:44,318 WARN (Thread-0) [org.infinispan.CONTAINER] ISPN000189: While stopping a cache or cache manager, one of its components failed to stop java.util.concurrent.CompletionException: 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 java.base/java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:412)
> at java.base/java.util.concurrent.CompletableFuture.join(CompletableFuture.java:2044)
> at org.infinispan.manager.DefaultCacheManager.terminate(DefaultCacheManager.java:780)
> at org.infinispan.manager.DefaultCacheManager.stopCaches(DefaultCacheManager.java:841)
> at org.infinispan.manager.DefaultCacheManager.internalStop(DefaultCacheManager.java:817)
> at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:793)
> at org.infinispan.server.SecurityActions.lambda$stopCacheManager$2(SecurityActions.java:75)
> at org.infinispan.security.Security.doPrivileged(Security.java:45)
> at org.infinispan.server.SecurityActions.doPrivileged(SecurityActions.java:38)
> at org.infinispan.server.SecurityActions.stopCacheManager(SecurityActions.java:81)
> at java.base/java.util.LinkedHashMap$LinkedValues.forEach(LinkedHashMap.java:608)
> at org.infinispan.server.Server.localShutdown(Server.java:484)
> at org.infinispan.server.Server.lambda$run$1(Server.java:410)
> at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
> at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837)
> at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506)
> at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2073)
> at org.infinispan.server.DefaultExitHandler.exit(DefaultExitHandler.java:13)
> at org.infinispan.server.ShutdownHook.run(ShutdownHook.java:16)
> Caused by: org.infinispan.commons.Cac^CheManager.internalGetCache(DefaultCacheManager.java:532)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:510)
> at org.infinispan.security.actions.GetCacheAction.run(GetCacheAction.java:26)
> at org.infinispan.security.actions.GetCacheAction.run(GetCacheAction.java:14)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
4 years, 8 months
[Red Hat JIRA] (ISPN-12534) CacheConfigurationException message ISPN028021 should return that it is missing an annotation in the field
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12534?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12534:
-------------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/8968
Status: Pull Request Sent (was: Open)
> 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
> Reporter: Diego Lovison
> Assignee: Gustavo Fernandes
> Priority: Major
> 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-12534) CacheConfigurationException message ISPN028021 should return that it is missing an annotation in the field
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12534?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12534:
-------------------------------------
Affects Version/s: 12.0.0.CR1
> 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
> 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