[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method
by Vittorio Rigamonti (JIRA)
[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ]
Vittorio Rigamonti updated ISPN-6162:
-------------------------------------
Fix Version/s: 9.0.0.Alpha2
(was: 9.0.0.Alpha1)
> Drop Query.getResultSize() method
> ---------------------------------
>
> Key: ISPN-6162
> URL: https://issues.jboss.org/browse/ISPN-6162
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Adrian Nistor
> Fix For: 9.0.0.Alpha2
>
>
> Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (ISPN-6328) Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)
by Vittorio Rigamonti (JIRA)
[ https://issues.jboss.org/browse/ISPN-6328?page=com.atlassian.jira.plugin.... ]
Vittorio Rigamonti updated ISPN-6328:
-------------------------------------
Fix Version/s: 9.0.0.Alpha2
(was: 9.0.0.Alpha1)
> Improper configuration of marshalling can lead to com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-6328
> URL: https://issues.jboss.org/browse/ISPN-6328
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 8.2.0.CR1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 9.0.0.Alpha2
>
>
> Running queries on a remote cache that was previously populated by an app that did not use protobuf marshalling should be allowed, and all those entities that were not encoded using protobuf should be ignored by the query engine and a warning should be logged instructing the user about the potential issue and how to fix the configuration.
> The current behaviour in this case is not user friendly, especially in case of non-indexed query. An error is thrown during query evaluation: "com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)." which indicates the unmarshalling of the queried entities is not possible. The actual cause of the bad encoding should be explained to the user and no exception should be thrown as if the type of entities does not match the requested type.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months