February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-5517) JDBCBinaryStore size method should query count directly instead of iterating

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5517?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5517: -------------------------------- Fix Version/s: (was: 8.0.0.CR1) (was: 8.2.0.CR1) > JDBCBinaryStore size method should query count directly instead of iterating > ---------------------------------------------------------------------------- > > Key: ISPN-5517 > URL: https://issues.jboss.org/browse/ISPN-5517 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: William Burns > > JDBCBinaryStore size method iterates upon all of the rows in the database. We should instead use the getCountRowsSql from the table manipulation just like JDBCStringBasedStore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5514) Add test to verify entries are present when utilizing an AsyncStore

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-5514?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-5514: -------------------------------- Fix Version/s: (was: 8.2.0.CR1) > Add test to verify entries are present when utilizing an AsyncStore > ------------------------------------------------------------------- > > Key: ISPN-5514 > URL: https://issues.jboss.org/browse/ISPN-5514 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: William Burns > > The AsyncStore can keep entries in memory where they don't exist in the data container or the underlying store. We should verify the various methods of the CacheLoader/AdvancedCacheLoader all work properly when utilizing an AsyncStore. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6231) The workflow for submitting new task and seeing the result is not natural

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6231?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-6231: --------------------------------------- I wouldn't use a dialog, better use patternfly alert (https://www.patternfly.org/widgets/#alerts) > The workflow for submitting new task and seeing the result is not natural > ------------------------------------------------------------------------- > > Key: ISPN-6231 > URL: https://issues.jboss.org/browse/ISPN-6231 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 8.2.0.Beta2 > Reporter: Martin Gencur > Assignee: Pedro Zapata > Priority: Minor > > When I open "Launch new task" modal dialog, fill in all the details, and click "Launch task", the task is successfully executed. The problem I see is that, the screen remains open and for leaving this screen, the user has to click "Cancel" even though the task has been submitted and executed. > A more natural approach could be this: > After clicking "Launch task" the original modal dialog disappears and a new dialog appears. This new modal dialog would contain just two elements: > 1) A message about success and the link to show the result > 2) "OK" button (instead of cancel) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6181) # Stores shows incorrect value

by Martin Vrabel (JIRA)

[ https://issues.jboss.org/browse/ISPN-6181?page=com.atlassian.jira.plugin.... ] Martin Vrabel updated ISPN-6181: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/46 > # Stores shows incorrect value > ------------------------------ > > Key: ISPN-6181 > URL: https://issues.jboss.org/browse/ISPN-6181 > Project: Infinispan > Issue Type: Bug > Components: Console > Reporter: Martin Vrabel > Assignee: Vladimir Blagojevic > > Page: Caches -> select cache container -> select cache. > Configuration of the cache: > <replicated-cache name="replicatedCacheForStatisticsTesting" mode="SYNC" remote-timeout="30000" start="EAGER"> > <transaction mode="NONE"/> > <eviction strategy="FIFO" size="10"/> > <locking isolation="READ_COMMITTED" acquire-timeout="30000" concurrency-level="1000" striping="false"/> > <file-store path="replicatedCacheForStatisticsTestingFileStore" purge="true" passivation="true"/> > </replicated-cache> > When I put 10 entries in the cache , this field #stores show 10 but should be 0. When I insert another 10 entries the number is still 0 but should be 20 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6226) Deprecate InfinispanCollections.emptySet/Map/List

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6226?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6226: -------------------------------- Fix Version/s: 8.2.0.CR1 > Deprecate InfinispanCollections.emptySet/Map/List > ------------------------------------------------- > > Key: ISPN-6226 > URL: https://issues.jboss.org/browse/ISPN-6226 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.CR1, 8.2.0.Final > > > These were introduced in the time of jdk 1.6 which had poor implementations for Collections.empty*() which allocated new iterator instances on each iterator() call. These can go away now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6226) Deprecate InfinispanCollections.emptySet/Map/List

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6226?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6226: -------------------------------- Summary: Deprecate InfinispanCollections.emptySet/Map/List (was: InfinispanCollections.EMPTY_SET/MAP/LIST are no longer needed) > Deprecate InfinispanCollections.emptySet/Map/List > ------------------------------------------------- > > Key: ISPN-6226 > URL: https://issues.jboss.org/browse/ISPN-6226 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.CR1, 8.2.0.Final > > > These were introduced in the time of jdk 1.6 which had poor implementations for Collections.empty*() which allocated new iterator instances on each iterator() call. These can go away now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6226) Deprecate InfinispanCollections.emptySet/Map/List

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6226?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6226: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4021 > Deprecate InfinispanCollections.emptySet/Map/List > ------------------------------------------------- > > Key: ISPN-6226 > URL: https://issues.jboss.org/browse/ISPN-6226 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.CR1, 8.2.0.Final > > > These were introduced in the time of jdk 1.6 which had poor implementations for Collections.empty*() which allocated new iterator instances on each iterator() call. These can go away now. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6231) The workflow for submitting new task and seeing the result is not natural

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-6231?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-6231: ------------------------------------- OK. Makes sense. > The workflow for submitting new task and seeing the result is not natural > ------------------------------------------------------------------------- > > Key: ISPN-6231 > URL: https://issues.jboss.org/browse/ISPN-6231 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 8.2.0.Beta2 > Reporter: Martin Gencur > Assignee: Pedro Zapata > Priority: Minor > > When I open "Launch new task" modal dialog, fill in all the details, and click "Launch task", the task is successfully executed. The problem I see is that, the screen remains open and for leaving this screen, the user has to click "Cancel" even though the task has been submitted and executed. > A more natural approach could be this: > After clicking "Launch task" the original modal dialog disappears and a new dialog appears. This new modal dialog would contain just two elements: > 1) A message about success and the link to show the result > 2) "OK" button (instead of cancel) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5830) Manage state transfer actions

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5830?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-5830: ------------------------------- Status: Open (was: New) > Manage state transfer actions > ----------------------------- > > Key: ISPN-5830 > URL: https://issues.jboss.org/browse/ISPN-5830 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Pedro Zapata > Assignee: Vladimir Blagojevic > Labels: jdg7 > > As an administrator, I want to control Cross site state transfer (when replica sites go offline and come back online) conveniently from the Management Console. > At its core, this is a cache level operation. However, we need a Cache container level operation that will transfer state for all cache that are replicated to the affected data-center(s). > The following actions will be added to the Cache container action menu > - Take site offline > - Bring site online > Another 2 additional options will also be added: > - Force state transfer > - Stop state transfer > Those options will be only enabled if cross site replication is enabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5830) Manage state transfer actions

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-5830?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-5830: ---------------------------------- Assignee: Pedro Zapata (was: Vladimir Blagojevic) > Manage state transfer actions > ----------------------------- > > Key: ISPN-5830 > URL: https://issues.jboss.org/browse/ISPN-5830 > Project: Infinispan > Issue Type: Sub-task > Components: Console > Reporter: Pedro Zapata > Assignee: Pedro Zapata > Labels: jdg7 > > As an administrator, I want to control Cross site state transfer (when replica sites go offline and come back online) conveniently from the Management Console. > At its core, this is a cache level operation. However, we need a Cache container level operation that will transfer state for all cache that are replicated to the affected data-center(s). > The following actions will be added to the Cache container action menu > - Take site offline > - Bring site online > Another 2 additional options will also be added: > - Force state transfer > - Stop state transfer > Those options will be only enabled if cross site replication is enabled -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016