[JBoss JIRA] (ISPN-9915) JDBC publish Flowable should explicitly rollback connection
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9915?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9915:
----------------------------------
Sprint: 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 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> 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-9322) Remove all usages of @IndexedField protostream annotation
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9322?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9322:
----------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Remove all usages of @IndexedField protostream annotation
> ---------------------------------------------------------
>
> Key: ISPN-9322
> URL: https://issues.jboss.org/browse/ISPN-9322
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> This annotation is deprecated and should be replaced with @Field but we still have several usages in our test suite.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-9876) Commons and embedded feature-packs should utilise 1.3 schema for backwards-compatibility
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9876?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9876:
----------------------------------
Sprint: 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 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Commons and embedded feature-packs should utilise 1.3 schema for backwards-compatibility
> --------------------------------------------------------------------------------------------
>
> Key: ISPN-9876
> URL: https://issues.jboss.org/browse/ISPN-9876
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Affects Versions: 10.0.0.Alpha2, 9.4.5.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha3, 9.4.6.Final
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-4915) Support flags for REST endpoint
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-4915?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4915:
----------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> Support flags for REST endpoint
> -------------------------------
>
> Key: ISPN-4915
> URL: https://issues.jboss.org/browse/ISPN-4915
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Reporter: Tristan Tarrant
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: hackathon
> Fix For: 10.0.0.CR3
>
>
> For protocol symmetry, we should add support for the operation flags (e.g. SKIP_CACHE_LOAD, SKIP_INDEXING, etc) on the REST operations using some form of custom header
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-4075?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4075:
----------------------------------
Sprint: Sprint 10.0.0.Alpha2, 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 (was: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> State transfer should preserve the creation timestamp of entries
> ----------------------------------------------------------------
>
> Key: ISPN-4075
> URL: https://issues.jboss.org/browse/ISPN-4075
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 6.0.1.Final
> Reporter: dan.berindei
> Assignee: dan.berindei
> Priority: Major
> Fix For: 9.4.7.Final, 10.0.0.Beta1, 10.0.0.Final
>
>
> State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended.
> The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-6161) [Remote query] Indexes should be created only for annotated message types
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-6161?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-6161:
----------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> [Remote query] Indexes should be created only for annotated message types
> -------------------------------------------------------------------------
>
> Key: ISPN-6161
> URL: https://issues.jboss.org/browse/ISPN-6161
> Project: Infinispan
> Issue Type: Task
> Components: Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> Modify behaviour of indexing for protobuf entities: Current behaviour is: if the message types is not annotated then we index all its fields; if some fields are annotated then index those fields only. New behaviour: index only the annotated fields.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month
[JBoss JIRA] (ISPN-10534) ProtoStreamMarshaller.getSerializationContext fails with unclear message
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10534?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10534:
-----------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36)
> ProtoStreamMarshaller.getSerializationContext fails with unclear message
> ------------------------------------------------------------------------
>
> Key: ISPN-10534
> URL: https://issues.jboss.org/browse/ISPN-10534
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 9.4.16.Final, 10.0.0.CR1
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.CR2, 9.4.17.Final
>
>
> The marshaller could be null for many reasons, so a clearer error message is needed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 1 month