May 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11878) GlobalState should automatically be enabled when attributes configured

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11878?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11878: -------------------------------- Status: Open (was: New) > GlobalState should automatically be enabled when attributes configured > ---------------------------------------------------------------------- > > Key: ISPN-11878 > URL: https://issues.redhat.com/browse/ISPN-11878 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 11.0.0.Dev05 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > > Currently it's neccessary for a user to do the following to configure the global state: > {{globalBuilder.globalState().enable().persistentLocation(location)}} > However the configuration of {{persistentLocation}} should be sufficient to enable the global state, i.e. the following should result in enabled(true) being called: > {{globalBuilder.globalState().persistentLocation(location);}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11800) Convert BackupReceiver to component

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11800?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11800: ------------------------------- Sprint: DataGrid Sprint #44 > Convert BackupReceiver to component > ----------------------------------- > > Key: ISPN-11800 > URL: https://issues.redhat.com/browse/ISPN-11800 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Cross-Site Replication > Affects Versions: 11.0.0.Dev05 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.CR1 > > > The {{BackupReceiver}} instance is created by {{BackupReceiverRepository}} and it needs access to the {{Cache}} instance for its dependencies. > However, with the latest changes in Cross-Site Replication, it needs to be accessed by commands and the only way to do it is by doing: > {code:java} > BackupReceiver backupReceiver = registry.getGlobalComponentRegistry() > .getComponent(BackupReceiverRepository.class) > .getBackupReceiver(cache); > {code} > Bottom line: tt should be converted to a component. > Another alternative would be to merge it with {{PerCacheInboundInvocationHandler}}... but it doesn't sound too good since it will increase the complexity and size of {{PerCacheInboundInvocationHandler}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11879) client-id for LoginResource

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11879: -------------------------------------- Summary: client-id for LoginResource Key: ISPN-11879 URL: https://issues.redhat.com/browse/ISPN-11879 Project: Infinispan Issue Type: Enhancement Components: Security Reporter: Tristan Tarrant Assignee: Tristan Tarrant -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11878) GlobalState should automatically be enabled when attributes configured

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-11878: ----------------------------------- Summary: GlobalState should automatically be enabled when attributes configured Key: ISPN-11878 URL: https://issues.redhat.com/browse/ISPN-11878 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 11.0.0.Dev05 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 11.0.0.CR1 Currently it's neccessary for a user to do the following to configure the global state: {{globalBuilder.globalState().enable().persistentLocation(location)}} However the configuration of {{persistentLocation}} should be sufficient to enable the global state, i.e. the following should result in enabled(true) being called: {{globalBuilder.globalState().persistentLocation(location);}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11799) Deprecate SearchManager

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11799?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11799: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Merged in master. Thanks [~gustavonalle]! > Deprecate SearchManager > ----------------------- > > Key: ISPN-11799 > URL: https://issues.redhat.com/browse/ISPN-11799 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev05 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: query-ispn11 > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1087) QueryFactory Object does not exist

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-1087?page=com.atlassian.jira.plugin... ] Tristan Tarrant closed ISPN-1087. --------------------------------- Resolution: Done > QueryFactory Object does not exist > ---------------------------------- > > Key: ISPN-1087 > URL: https://issues.redhat.com/browse/ISPN-1087 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.0.0.CR1 > Environment: Infinispan infinispan-5.0.0.CR1-bin.zip > Reporter: Jeff LaFrate > Assignee: Sanne GRINOVERO > Priority: Minor > Labels: docs, wiki > > I am trying to query the infinispan cache using your documentation at http://community.jboss.org/wiki/QueryingInfinispan/diff?secondVersionNumb... > See section "usage with Infinispan 5": > When using Infinispan 5, it's a bit simpler: you don't need the QueryHelper, and just create a QueryFactory directly from the cache: > > QueryFactory qf = new QueryFactory(cache); > CacheQuery cacheQuery = qf.getQuery( any org.apache.lucene.search.Query ); > List<Object> found = cacheQuery.list(); > Problem: > org.infinispan.query.QueryFactory; does not exist in infinispan-query.jar from the Infinispan infinispan-5.0.0.CR1-bin.zip download. > It exists in infinispan-query.jar from infinispan-4.2.1.FINAL > and in the 5.0 API javadoc but not in the infinispan-query.jar from the Infinispan infinispan-5.0.0.CR1-bin.zip download. > Thoughts? > Thanks > Jeff > 5/9/11 > I would like an example of querying infinispan, using the latest APIs. > org.infinispan.query.impl.CacheQueryImpl;...? > org.apache.lucene.search.Query etc... > Thanks > Jeff -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1087) QueryFactory Object does not exist

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-1087?page=com.atlassian.jira.plugin... ] Tristan Tarrant reopened ISPN-1087: ----------------------------------- > QueryFactory Object does not exist > ---------------------------------- > > Key: ISPN-1087 > URL: https://issues.redhat.com/browse/ISPN-1087 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.0.0.CR1 > Environment: Infinispan infinispan-5.0.0.CR1-bin.zip > Reporter: Jeff LaFrate > Assignee: Sanne GRINOVERO > Priority: Minor > Labels: docs, wiki > Fix For: 5.0.0.CR4 > > > I am trying to query the infinispan cache using your documentation at http://community.jboss.org/wiki/QueryingInfinispan/diff?secondVersionNumb... > See section "usage with Infinispan 5": > When using Infinispan 5, it's a bit simpler: you don't need the QueryHelper, and just create a QueryFactory directly from the cache: > > QueryFactory qf = new QueryFactory(cache); > CacheQuery cacheQuery = qf.getQuery( any org.apache.lucene.search.Query ); > List<Object> found = cacheQuery.list(); > Problem: > org.infinispan.query.QueryFactory; does not exist in infinispan-query.jar from the Infinispan infinispan-5.0.0.CR1-bin.zip download. > It exists in infinispan-query.jar from infinispan-4.2.1.FINAL > and in the 5.0 API javadoc but not in the infinispan-query.jar from the Infinispan infinispan-5.0.0.CR1-bin.zip download. > Thoughts? > Thanks > Jeff > 5/9/11 > I would like an example of querying infinispan, using the latest APIs. > org.infinispan.query.impl.CacheQueryImpl;...? > org.apache.lucene.search.Query etc... > Thanks > Jeff -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1087) QueryFactory Object does not exist

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-1087?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-1087: ---------------------------------- Labels: docs wiki (was: docs, wiki) > QueryFactory Object does not exist > ---------------------------------- > > Key: ISPN-1087 > URL: https://issues.redhat.com/browse/ISPN-1087 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.0.0.CR1 > Environment: Infinispan infinispan-5.0.0.CR1-bin.zip > Reporter: Jeff LaFrate > Assignee: Sanne GRINOVERO > Priority: Minor > Labels: docs, wiki > Fix For: 5.0.0.CR4 > > > I am trying to query the infinispan cache using your documentation at http://community.jboss.org/wiki/QueryingInfinispan/diff?secondVersionNumb... > See section "usage with Infinispan 5": > When using Infinispan 5, it's a bit simpler: you don't need the QueryHelper, and just create a QueryFactory directly from the cache: > > QueryFactory qf = new QueryFactory(cache); > CacheQuery cacheQuery = qf.getQuery( any org.apache.lucene.search.Query ); > List<Object> found = cacheQuery.list(); > Problem: > org.infinispan.query.QueryFactory; does not exist in infinispan-query.jar from the Infinispan infinispan-5.0.0.CR1-bin.zip download. > It exists in infinispan-query.jar from infinispan-4.2.1.FINAL > and in the 5.0 API javadoc but not in the infinispan-query.jar from the Infinispan infinispan-5.0.0.CR1-bin.zip download. > Thoughts? > Thanks > Jeff > 5/9/11 > I would like an example of querying infinispan, using the latest APIs. > org.infinispan.query.impl.CacheQueryImpl;...? > org.apache.lucene.search.Query etc... > Thanks > Jeff -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11877) Remove PartitionHandling.ENABLED

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11877?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11877: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8360 > Remove PartitionHandling.ENABLED > -------------------------------- > > Key: ISPN-11877 > URL: https://issues.redhat.com/browse/ISPN-11877 > Project: Infinispan > Issue Type: Sub-task > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11877) Remove PartitionHandling.ENABLED

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11877?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11877: -------------------------------- Fix Version/s: 11.0.0.CR1 > Remove PartitionHandling.ENABLED > -------------------------------- > > Key: ISPN-11877 > URL: https://issues.redhat.com/browse/ISPN-11877 > Project: Infinispan > Issue Type: Sub-task > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2020