[JBoss JIRA] (ISPN-6947) Indexing mode not compatible with multiple entities per cache
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-6947?page=com.atlassian.jira.plugin... ]
Nistor Adrian edited comment on ISPN-6947 at 5/4/20 4:23 AM:
-------------------------------------------------------------
This issue is no longer relevant starting with version 11, after ISPN-11241.
Also, ISPN-11757 no longer allows multiple indexing providers per cache.
was (Author: anistor):
This issue is no longer relevant starting with version 11, after ISPN-11241
> Indexing mode not compatible with multiple entities per cache
> -------------------------------------------------------------
>
> Key: ISPN-6947
> URL: https://issues.redhat.com/browse/ISPN-6947
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> Consider a cache composed of two entities A and B, entity A is stored on RAM and entity B on Infinispan itself. The configuration to achieve that is below:
> {noformat}
> cacheCfg.indexing()
> .index(Index.ALL)
> .addIndexedEntity(A.class)
> .addIndexedEntity(B.class)
> .addProperty("A.directory_provider", "ram")
> .addProperty("A.indexmanager", "org.infinispan.query.indexmanager.InfinispanIndexManager")
> {noformat}
> The configuration Index.ALL only makes sense to RAM directory, while for InfinispanIndexManager it'd cause redundant indexing. The indexing mode should not be at cache level but at "index" level
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-6947) Indexing mode not compatible with multiple entities per cache
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-6947?page=com.atlassian.jira.plugin... ]
Nistor Adrian resolved ISPN-6947.
---------------------------------
Fix Version/s: 11.0.0.Dev05
Resolution: Out of Date
This issue is no longer relevant starting with version 11, after ISPN-11241
> Indexing mode not compatible with multiple entities per cache
> -------------------------------------------------------------
>
> Key: ISPN-6947
> URL: https://issues.redhat.com/browse/ISPN-6947
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Fix For: 11.0.0.Dev05
>
>
> Consider a cache composed of two entities A and B, entity A is stored on RAM and entity B on Infinispan itself. The configuration to achieve that is below:
> {noformat}
> cacheCfg.indexing()
> .index(Index.ALL)
> .addIndexedEntity(A.class)
> .addIndexedEntity(B.class)
> .addProperty("A.directory_provider", "ram")
> .addProperty("A.indexmanager", "org.infinispan.query.indexmanager.InfinispanIndexManager")
> {noformat}
> The configuration Index.ALL only makes sense to RAM directory, while for InfinispanIndexManager it'd cause redundant indexing. The indexing mode should not be at cache level but at "index" level
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-11763) Make cache authorization roles declaration implicit
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11763:
--------------------------------------
Summary: Make cache authorization roles declaration implicit
Key: ISPN-11763
URL: https://issues.redhat.com/browse/ISPN-11763
Project: Infinispan
Issue Type: Enhancement
Components: Security
Affects Versions: 11.0.0.Dev05
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 11.0.0.CR1
Specifying cache authorization roles is a chore because a user must declare which global roles apply to each individual cache.
By making the cache roles implicit, we can apply all roles declared in the global config to caches automatically:
{code:xml}
<cache-container>
<security>
<authorization>
<identity-role-mapper/>
<role name="AdminRole" permissions="ALL"/>
<role name="ReaderRole" permissions="READ"/>
<role name="WriterRole" permissions="WRITE"/>
<role name="SupervisorRole" permissions="READ WRITE EXEC BULK_READ"/>
</authorization>
</security>
<distributed-cache name="secure-implicit">
<security><authorization/></security>
</distributed-cache>
<distributed-cache name="secure-explicit">
<security><authorization roles="AdminRole ReaderRole WriterRole SupervisorRole"/></security>
</distributed-cache>
</cache-container>
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-11717) Deprecate ConsistentHashFactory customization
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11717?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11717:
-----------------------------------
Sprint: DataGrid Sprint #43, DataGrid Sprint #44 (was: DataGrid Sprint #43)
> Deprecate ConsistentHashFactory customization
> ---------------------------------------------
>
> Key: ISPN-11717
> URL: https://issues.redhat.com/browse/ISPN-11717
> Project: Infinispan
> Issue Type: Task
> Components: Configuration, Core
> Affects Versions: 11.0.0.Dev04
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.CR1, 11.0.0.Final
>
>
> There aren't any good reasons to use a {{ConsistentHashFactory}} implementation different than the default selected by {{StateTransferManagerImpl#pickConsistentHashFactory}}.
> The configuration attribute made sense when the default was {{DefaultConsistentHashFactory}}, but {{SyncConsistentHashFactory}} is much better nowadays, and it's pretty much impossible to come up with an implementation that works in more than one cache mode with the current API.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (ISPN-11758) QueryCache is a global component but should scope all cached queries per cache
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11758?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11758:
-----------------------------------
Sprint: DataGrid Sprint #43, DataGrid Sprint #44 (was: DataGrid Sprint #43)
> QueryCache is a global component but should scope all cached queries per cache
> ------------------------------------------------------------------------------
>
> Key: ISPN-11758
> URL: https://issues.redhat.com/browse/ISPN-11758
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.CR1
>
>
> The query might execute differently depending on the configuration of each cache. This will be an issue starting with HSearch 6.
> All entries will be keyed also based on cache name. QueryCache must be cleared when a cache stops. Also, all caches must have a configured stop dependency on the QueryCache.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months