July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8058) The org.infinispan.tasks.Task interface should be in the tasks-api package

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8058?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8058: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5282 > The org.infinispan.tasks.Task interface should be in the tasks-api package > -------------------------------------------------------------------------- > > Key: ISPN-8058 > URL: https://issues.jboss.org/browse/ISPN-8058 > Project: Infinispan > Issue Type: Task > Components: Tasks > Affects Versions: 9.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.1.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8058) The org.infinispan.tasks.Task interface should be in the tasks-api package

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-8058: ------------------------------------- Summary: The org.infinispan.tasks.Task interface should be in the tasks-api package Key: ISPN-8058 URL: https://issues.jboss.org/browse/ISPN-8058 Project: Infinispan Issue Type: Task Components: Tasks Affects Versions: 9.1.0.CR1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.1.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8057) AdminOperation task engine does not adhere to API

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-8057: ------------------------------------- Summary: AdminOperation task engine does not adhere to API Key: ISPN-8057 URL: https://issues.jboss.org/browse/ISPN-8057 Project: Infinispan Issue Type: Bug Components: Server, Tasks Affects Versions: 9.1.0.CR1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.1.0.Final The AdminOperation task engine returns a Set<Class> instead of Set<Task> for getTasks() -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7865) Distributed Stream thread usage for key aware operations can be improved

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7865?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7865: -------------------------------- Fix Version/s: 9.2.0.Final > Distributed Stream thread usage for key aware operations can be improved > ------------------------------------------------------------------------ > > Key: ISPN-7865 > URL: https://issues.jboss.org/browse/ISPN-7865 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Final > > > Currently iterator will block a thread on the remote server when it is trying to send back a response. It would be better if we used full async API to instead request blocks of values as the iterator consumes them. We should make sure we always maintain a distributed batch size worth. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7865) Distributed Stream thread usage for key aware operations can be improved

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7865?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7865: -------------------------------- Status: Open (was: New) > Distributed Stream thread usage for key aware operations can be improved > ------------------------------------------------------------------------ > > Key: ISPN-7865 > URL: https://issues.jboss.org/browse/ISPN-7865 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > > Currently iterator will block a thread on the remote server when it is trying to send back a response. It would be better if we used full async API to instead request blocks of values as the iterator consumes them. We should make sure we always maintain a distributed batch size worth. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7865) Distributed Stream thread usage for key aware operations can be improved

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7865?page=com.atlassian.jira.plugin.... ] Work on ISPN-7865 started by William Burns. ------------------------------------------- > Distributed Stream thread usage for key aware operations can be improved > ------------------------------------------------------------------------ > > Key: ISPN-7865 > URL: https://issues.jboss.org/browse/ISPN-7865 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > > Currently iterator will block a thread on the remote server when it is trying to send back a response. It would be better if we used full async API to instead request blocks of values as the iterator consumes them. We should make sure we always maintain a distributed batch size worth. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8056) Batching support for persistence

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-8056: ---------------------------------- Summary: Batching support for persistence Key: ISPN-8056 URL: https://issues.jboss.org/browse/ISPN-8056 Project: Infinispan Issue Type: Enhancement Reporter: Pedro Zapata Assignee: Ryan Emerson -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8055) Upsert support for JDBC stores

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-8055: ---------------------------------- Summary: Upsert support for JDBC stores Key: ISPN-8055 URL: https://issues.jboss.org/browse/ISPN-8055 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores, Transactions Reporter: Pedro Zapata Assignee: Ryan Emerson Fix For: 9.0.0.Alpha2, 8.2.6.Final, 9.0.0.Final Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8054) Move memcached and websocket connectors out of the default configs

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-8054: ---------------------------------- Summary: Move memcached and websocket connectors out of the default configs Key: ISPN-8054 URL: https://issues.jboss.org/browse/ISPN-8054 Project: Infinispan Issue Type: Task Components: Server Affects Versions: 9.0.0.CR2 Reporter: Pedro Zapata Assignee: Tristan Tarrant Fix For: 9.0.0.CR4 The memcached and websocket connectors are not as popular, so remove them from the default server config and ship additional examples. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8053) Supply a default VoidCallback when the SASL mech on the Hot Rod client is EXTERNAL

by Pedro Zapata (JIRA)

Pedro Zapata created ISPN-8053: ---------------------------------- Summary: Supply a default VoidCallback when the SASL mech on the Hot Rod client is EXTERNAL Key: ISPN-8053 URL: https://issues.jboss.org/browse/ISPN-8053 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols Affects Versions: 9.0.0.Final Reporter: Pedro Zapata Assignee: Tristan Tarrant Fix For: 9.1.0.Final The EXTERNAL SASL mech doesn't need any special callback handlers. We already package a VoidCallbackHandler, so we can implicitly set it when EXTERNAL is configured -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2017