[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6162?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6162:
----------------------------------
Fix Version/s: 9.4.1.Final
(was: 9.4.0.Final)
> 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
> Priority: Major
> Fix For: 9.4.1.Final
>
>
> 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
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ISPN-6094) Use security actions to read system properties for configuration
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6094?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6094:
----------------------------------
Fix Version/s: 9.4.1.Final
(was: 9.4.0.Final)
> Use security actions to read system properties for configuration
> ----------------------------------------------------------------
>
> Key: ISPN-6094
> URL: https://issues.jboss.org/browse/ISPN-6094
> Project: Infinispan
> Issue Type: Task
> Components: Core, Embedded Querying
> Affects Versions: 8.1.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.1.Final
>
>
> Infinispan uses system properties for out-of-band settings that weren't deemed important enough to have a proper configuration attribute:
> * infinispan.arrays.debug
> * infinispan.unsafe.force_multicast
> * infinispan.compat (obsolete?)
> * infinispan.debugDependencies
> * infinispan.stagger.delay (introduced with ISPN-825)
> * org.infinispan.query.indexmanager.LockAcquiringBackend.MAX_QUEUE_SIZE
> We should use a {{SecurityActions}} class to access these properties instead of {{Boolean.getBoolean()}} and {{Integer.getInteger()}}. We should also document these system properties, and evaluate moving them to the proper configuration.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months
[JBoss JIRA] (ISPN-6367) HotRod client unmarshalling ignores configured classloader
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6367?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6367:
----------------------------------
Fix Version/s: 9.4.1.Final
(was: 9.4.0.Final)
> HotRod client unmarshalling ignores configured classloader
> ----------------------------------------------------------
>
> Key: ISPN-6367
> URL: https://issues.jboss.org/browse/ISPN-6367
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols, Server
> Affects Versions: 8.2.0.Final
> Reporter: Dan Berindei
> Priority: Major
> Fix For: 9.4.1.Final
>
>
> The {{RemoteCacheManager}}'s {{ConfigurationBuilder}} allows you to set a classloader, but the client ignores that classloader when unmarshalling values received from the server.
> This leads to problems when the client doesn't have a flat classpath (e.g. in an OSGi or JBoss Modules-based container).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 6 months