[JBoss JIRA] (ISPN-10829) CacheIgnoreManager unable to persist data
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10829?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10829:
--------------------------------
Sprint: (was: DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> CacheIgnoreManager unable to persist data
> -----------------------------------------
>
> Key: ISPN-10829
> URL: https://issues.jboss.org/browse/ISPN-10829
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> The IgnoredCache test failures are due to a MarshallingException being thrown by the PersistenceMarshallerImpl. This is because no protostream marshaller is able to serialize the ConcurrentHashMap.KeySetView used to store values. Therefore, it's neccesssary to wrap this Set in a Java entity, so that a .proto message and associated marshaller can be generated by ProtoStream.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10699) Add Transcoder name to log statements to aid debugging
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10699?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10699:
--------------------------------
Sprint: (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> Add Transcoder name to log statements to aid debugging
> ------------------------------------------------------
>
> Key: ISPN-10699
> URL: https://issues.jboss.org/browse/ISPN-10699
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 10.0.0.CR2
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR3
>
>
> Currently the error message returned to the client when a transcoding exception occurs is not very detailed as the stack trace is where the `HotRodClientException` is thrown and the server error message does not detail the transcoder that encountered the issue.
> We should include the name of the transcoder in the server exception to aid debugging.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10419) RocksDB purge should not utilise ArrayList to store multiple expired keys
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10419?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10419:
--------------------------------
Sprint: (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> RocksDB purge should not utilise ArrayList to store multiple expired keys
> -------------------------------------------------------------------------
>
> Key: ISPN-10419
> URL: https://issues.jboss.org/browse/ISPN-10419
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> Currently the RocksDB purge method stores multiple keys that expire at the same time in a ArrayList associated with the expiry time. This is currently marshallable because ArrayList is serializable and we utilise Jboss-marshalling, however ISPN-10354 means this is no longer possible in embedded mode when `infinispan-jboss-marshalling` is not present. Therefore, we should create a `ExpiryBucket` that can be marshalled via the persistence marshaller i.e. protobuf based.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-9843) RocksDBStore should not write entire MarshalledEntry as store value
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9843?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9843:
-------------------------------
Sprint: (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> RocksDBStore should not write entire MarshalledEntry as store value
> -------------------------------------------------------------------
>
> Key: ISPN-9843
> URL: https://issues.jboss.org/browse/ISPN-9843
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha2
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha3
>
>
> Currently the RocksDBStore implementation writes an entire MarshalledEntry as the db's value. This is inefficient as it means the key is stored twice. Instead, a KeyValuePair of an entries value and metadata should be stored.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-9915) JDBC publish Flowable should explicitly rollback connection
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9915?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-9915:
-------------------------------
Sprint: (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> JDBC publish Flowable should explicitly rollback connection
> -----------------------------------------------------------
>
> Key: ISPN-9915
> URL: https://issues.jboss.org/browse/ISPN-9915
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Alpha3, 9.4.6.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.7.Final, 10.0.0.Beta1
>
>
> The Flowable for the JDBC store publisher sets `autoCommit(false)` in order for pagination to work as expected, however we never explicitly call commit or rollback on the connection, therefore the exact behaviour is determined by the underlying connection pool. Instead we should explicitly call rollback() on the connection after the publisher has finished, because the operation is read only.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10422) Deprecate MediaType::parse in favour of MediaType::fromString
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-10422?page=com.atlassian.jira.plugin... ]
Ryan Emerson updated ISPN-10422:
--------------------------------
Sprint: (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37)
> Deprecate MediaType::parse in favour of MediaType::fromString
> -------------------------------------------------------------
>
> Key: ISPN-10422
> URL: https://issues.jboss.org/browse/ISPN-10422
> Project: Infinispan
> Issue Type: Enhancement
> Components: API
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> Currently {{org.infinispan.commons.dataconversion.MediaType}} exposes both {{fromString}} and {{parse}} methods to create an instance from a String. We should deprecate the latter in favour of the former and update all internal code references.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month