July 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9377) Enhance JdbcStringBasedStore to support segmentation

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9377?page=com.atlassian.jira.plugin.... ] Work on ISPN-9377 started by William Burns. ------------------------------------------- > Enhance JdbcStringBasedStore to support segmentation > ---------------------------------------------------- > > Key: ISPN-9377 > URL: https://issues.jboss.org/browse/ISPN-9377 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Final > > > Now with the introduction of segmented store interface, we can convert the RemoteStore to support segmentation. > We should be able to do this by adding a new int column named segment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9376) Enhance RemoteStore to support segmentation

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9376?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9376: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/6171 > Enhance RemoteStore to support segmentation > ------------------------------------------- > > Key: ISPN-9376 > URL: https://issues.jboss.org/browse/ISPN-9376 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Beta1, 9.4.0.Final > > > Now with the introduction of segmented store interface, we can convert the RemoteStore to support segmentation. > One thing to note is that this only works if the remote cache and the local one have the same number of segments. Otherwise data will appear missing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9376) Enhance RemoteStore to support segmentation

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9376?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9376: -------------------------------- Fix Version/s: 9.4.0.Beta1 > Enhance RemoteStore to support segmentation > ------------------------------------------- > > Key: ISPN-9376 > URL: https://issues.jboss.org/browse/ISPN-9376 > Project: Infinispan > Issue Type: Sub-task > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Beta1, 9.4.0.Final > > > Now with the introduction of segmented store interface, we can convert the RemoteStore to support segmentation. > One thing to note is that this only works if the remote cache and the local one have the same number of segments. Otherwise data will appear missing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9182) Remove compat mode from Tasks and Scripts

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9182?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9182: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6170 > Remove compat mode from Tasks and Scripts > ----------------------------------------- > > Key: ISPN-9182 > URL: https://issues.jboss.org/browse/ISPN-9182 > Project: Infinispan > Issue Type: Sub-task > Components: Tasks > Reporter: Gustavo Fernandes > > Both script and tasks hardcode GenericJbossMarshaller in several places, and use it to unmarshall parameters and user data when executing code. If the client uses a different marshaller, it breaks. > Both should rely instead on the MediaType sent by the Hot Rod client in order to convert from and to the storage format. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9182) Remove compat mode from Tasks and Scripts

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-9182?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-9182: ------------------------------------ Status: Open (was: New) > Remove compat mode from Tasks and Scripts > ----------------------------------------- > > Key: ISPN-9182 > URL: https://issues.jboss.org/browse/ISPN-9182 > Project: Infinispan > Issue Type: Sub-task > Components: Tasks > Reporter: Gustavo Fernandes > > Both script and tasks hardcode GenericJbossMarshaller in several places, and use it to unmarshall parameters and user data when executing code. If the client uses a different marshaller, it breaks. > Both should rely instead on the MediaType sent by the Hot Rod client in order to convert from and to the storage format. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9398) Hot Rod configuration properties should have setters to ease Spring Boot configurator

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9398?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9398: ---------------------------------- Sprint: Sprint 9.4.0.Beta1 > Hot Rod configuration properties should have setters to ease Spring Boot configurator > ------------------------------------------------------------------------------------- > > Key: ISPN-9398 > URL: https://issues.jboss.org/browse/ISPN-9398 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Spring Integration > Affects Versions: 9.3.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Final > > > https://github.com/infinispan/infinispan-spring-boot/issues/48 > n order to reduce the amount of boilerplate code and centralize this kind of thing I think we should enhance the https://github.com/infinispan/infinispan/blob/master/client/hotrod-client... class with setters for all properties. At this point, https://github.com/infinispan/infinispan-spring-boot/blob/master/infinisp... can just extend it while adding the @ConfigurationProperties annotation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9398) Hot Rod configuration properties should have setters to ease Spring Boot configurator

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9398: ------------------------------------- Summary: Hot Rod configuration properties should have setters to ease Spring Boot configurator Key: ISPN-9398 URL: https://issues.jboss.org/browse/ISPN-9398 Project: Infinispan Issue Type: Enhancement Components: Hot Rod, Spring Integration Affects Versions: 9.3.1.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.4.0.Final https://github.com/infinispan/infinispan-spring-boot/issues/48 n order to reduce the amount of boilerplate code and centralize this kind of thing I think we should enhance the https://github.com/infinispan/infinispan/blob/master/client/hotrod-client... class with setters for all properties. At this point, https://github.com/infinispan/infinispan-spring-boot/blob/master/infinisp... can just extend it while adding the @ConfigurationProperties annotation -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-65) WrappedMessage.writeMessage does not handle instances of Short, Byte, Character

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-65?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-65: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master and 4.2.x > WrappedMessage.writeMessage does not handle instances of Short, Byte, Character > ------------------------------------------------------------------------------- > > Key: IPROTO-65 > URL: https://issues.jboss.org/browse/IPROTO-65 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Ryan Emerson > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1, 4.2.1.Final > > > Attempts to marshall instances of Short results in an IllegalArgumentException being thrown: > {code} > java.lang.IllegalArgumentException: No marshaller registered for java.lang.Short > at org.infinispan.protostream.impl.SerializationContextImpl.getMarshallerDelegate(SerializationContextImpl.java:288) > at org.infinispan.protostream.WrappedMessage.writeMessage(WrappedMessage.java:192) > at org.infinispan.protostream.ProtobufUtil.toWrappedByteArray(ProtobufUtil.java:167) > ... > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-65) WrappedMessage.writeMessage does not handle instances of Short, Byte, Character

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/IPROTO-65?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated IPROTO-65: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/41 > WrappedMessage.writeMessage does not handle instances of Short, Byte, Character > ------------------------------------------------------------------------------- > > Key: IPROTO-65 > URL: https://issues.jboss.org/browse/IPROTO-65 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Ryan Emerson > Assignee: Adrian Nistor > Fix For: 4.3.0.Alpha1, 4.2.1.Final > > > Attempts to marshall instances of Short results in an IllegalArgumentException being thrown: > {code} > java.lang.IllegalArgumentException: No marshaller registered for java.lang.Short > at org.infinispan.protostream.impl.SerializationContextImpl.getMarshallerDelegate(SerializationContextImpl.java:288) > at org.infinispan.protostream.WrappedMessage.writeMessage(WrappedMessage.java:192) > at org.infinispan.protostream.ProtobufUtil.toWrappedByteArray(ProtobufUtil.java:167) > ... > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9397) Check TX support for remote caches

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-9397?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9397: ------------------------------ Description: The {{RemoteCacheManager.getCache()}} methods would fail to return a transactional cache if the cache in server isn't transactional. It would throw an exception! {{NotTransactionalException}}? The user can fallback to the non transaction case, example {code:java} try { cache = remoteCacheManager.getCache("some-cache", TransactionMode.NON_XA); } catch(NotTransactionalException e) { cache = remoteCacheManager.getCache("some-cache", TransactionMode.NONE); } {code} In addition, some helper method can be added to the {{RemoteCacheManager}} to avoid dealing with exceptions: {code:java} boolean supportsTransactions(String cacheName); {code} simple example: {code:java} boolean txCache = remoteCacheManager.supportsTransactions("some-cache"); remoteCacheManager.getCache("some-cache", txCache ? TransactionMode.NON_XA : TransactionMode.NONE); {code} was: The {{RemoteCacheManager.getCache()}} methods would fail to return a transactional cache if the cache in server isn't transactional. It would throw an exception! {{NotTransactionalException}}? The user can fallback to the non transaction case, example {code:java} try { cache = remoteCacheManager.getCache("some-cache", TransactionMode.NON_XA); } catch(NotTransactionalException e) { cache = remoteCacheManager.getCache("some-cache", TransactionMode.NONE); } {code} In addition, some helper method can be added to the {{RemoteCacheManager}} to avoid dealing with exceptions: {code:java} boolean supportsTransactions(String cacheName); {code} > Check TX support for remote caches > ---------------------------------- > > Key: ISPN-9397 > URL: https://issues.jboss.org/browse/ISPN-9397 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Remote Protocols, Transactions > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.4.0.Beta1 > > > The {{RemoteCacheManager.getCache()}} methods would fail to return a transactional cache if the cache in server isn't transactional. It would throw an exception! {{NotTransactionalException}}? > The user can fallback to the non transaction case, example > {code:java} > try { > cache = remoteCacheManager.getCache("some-cache", TransactionMode.NON_XA); > } catch(NotTransactionalException e) { > cache = remoteCacheManager.getCache("some-cache", TransactionMode.NONE); > } > {code} > In addition, some helper method can be added to the {{RemoteCacheManager}} to avoid dealing with exceptions: > {code:java} > boolean supportsTransactions(String cacheName); > {code} > simple example: > {code:java} > boolean txCache = remoteCacheManager.supportsTransactions("some-cache"); > remoteCacheManager.getCache("some-cache", txCache ? TransactionMode.NON_XA : TransactionMode.NONE); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2018