July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8113) Querying via Rest endpoint

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-8113: --------------------------------------- Summary: Querying via Rest endpoint Key: ISPN-8113 URL: https://issues.jboss.org/browse/ISPN-8113 Project: Infinispan Issue Type: Feature Request Components: Server Affects Versions: 9.1.0.Final Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Fix For: 9.2.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8112) Remove QueryKnownClasses

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8112?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8112: -------------------------------- Fix Version/s: 10.0.0.Final > Remove QueryKnownClasses > ------------------------ > > Key: ISPN-8112 > URL: https://issues.jboss.org/browse/ISPN-8112 > Project: Infinispan > Issue Type: Sub-task > Components: Embedded Querying > Reporter: Radim Vansa > Assignee: Adrian Nistor > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8112) Remove QueryKnownClasses

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8112?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8112: -------------------------------- Status: Open (was: New) > Remove QueryKnownClasses > ------------------------ > > Key: ISPN-8112 > URL: https://issues.jboss.org/browse/ISPN-8112 > Project: Infinispan > Issue Type: Sub-task > Components: Embedded Querying > Reporter: Radim Vansa > Assignee: Adrian Nistor > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8112) Remove QueryKnownClasses

by Radim Vansa (JIRA)

Radim Vansa created ISPN-8112: --------------------------------- Summary: Remove QueryKnownClasses Key: ISPN-8112 URL: https://issues.jboss.org/browse/ISPN-8112 Project: Infinispan Issue Type: Sub-task Components: Embedded Querying Reporter: Radim Vansa Assignee: Adrian Nistor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7806) QueryInterceptor should not load entries from DC but context

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-7806?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-7806: ----------------------------------- I've created reproducers: https://github.com/rvansa/infinispan/tree/ISPN-7806 > QueryInterceptor should not load entries from DC but context > ------------------------------------------------------------ > > Key: ISPN-7806 > URL: https://issues.jboss.org/browse/ISPN-7806 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.0.Final > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > > Currently in {{visitPrepareCommand}} the query interceptor is loading data directly from data container. That's wrong - if the entry is passivated/evicted, the previous value is incorrect. > As the data is not loaded (from DC/persistence) at current QI position, we should move QueryInterceptor after EntryWrappingInterceptor, CacheLoaderInterceptor -and xDistributionInterceptor (which may load the data from remote node),- and load the previous entry from context instead. The same approach should be taken for non-tx command, rather than relying on their return value. > **EDIT**: we should not move it below xDistributionInterceptor because on backup owner (which may be write-owner but not a read-owner) we would retrieve the updated value (affected by the current command), not the previous one. > There will still be issues if the command has SKIP_CACHE_LOAD flag: I suggest warning message if it doesn't have SKIP_INDEXING flag as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7971: ------------------------------------------- Right, I agree [~ryanemerson]. In that case, I would say we postpone this issue until we have Openshift detection API. > Display a warning that changes in standalone mode are not persisted > ------------------------------------------------------------------- > > Key: ISPN-7971 > URL: https://issues.jboss.org/browse/ISPN-7971 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > Attachments: Screen Shot 2017-07-26 at 9.45.27 AM.png > > > The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7971) Display a warning that changes in standalone mode are not persisted

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7971?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-7971: ------------------------------------ [~vblagojevic] The problem is that it is valid for a cache container's configuration to be updated in local standalone mode in non-openshift environments. So we don't want to tell users they can't perform a valid operation when they can, especially considering that our users at the moment will most likely be using infinispan on premise. > Display a warning that changes in standalone mode are not persisted > ------------------------------------------------------------------- > > Key: ISPN-7971 > URL: https://issues.jboss.org/browse/ISPN-7971 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > Attachments: Screen Shot 2017-07-26 at 9.45.27 AM.png > > > The Infinispan Management Console can also operate in Standalone mode. We would like to make it accessible in OpenShift. However we should probably display a warning that the console should be used only for monitoring and none of the changes are persisted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8109) Upgrade RocksDB to 5.6.1

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8109?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8109: ---------------------------------- Summary: Upgrade RocksDB to 5.6.1 (was: Upgrade RocksDB to 5.5.1) > Upgrade RocksDB to 5.6.1 > ------------------------ > > Key: ISPN-8109 > URL: https://issues.jboss.org/browse/ISPN-8109 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Affects Versions: 9.0.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.1.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8109) Upgrade RocksDB to 5.6.1

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8109?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8109: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade RocksDB to 5.6.1 > ------------------------ > > Key: ISPN-8109 > URL: https://issues.jboss.org/browse/ISPN-8109 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Affects Versions: 9.0.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.1.1.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7649) Administration console - transaction tab allows to set invalid options

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7649?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7649. -------------------------------- Fix Version/s: 9.1.1.Final Resolution: Done > Administration console - transaction tab allows to set invalid options > ---------------------------------------------------------------------- > > Key: ISPN-7649 > URL: https://issues.jboss.org/browse/ISPN-7649 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 9.0.0.CR3 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.1.1.Final > > > If a cache is set to distributed async mode, setting transactions to FULL_XA mode results in error after the cluster restart. The console shouldn't allow this combination. > Suggested solution - dropdown should display only valid options for transaction mode for the given cache. > (I'm not sure if this is the only invalid combination) > Server error: > ... > org.infinispan.commons.CacheConfigurationException: ISPN000441: Unsupported async cache mode 'DIST_ASYNC' for transactional caches > ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 July 2017