November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-9835) Jenkinsfile snapshot deployment fails

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9835?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9835: ---------------------------------- 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) > Jenkinsfile snapshot deployment fails > ------------------------------------- > > Key: ISPN-9835 > URL: https://issues.jboss.org/browse/ISPN-9835 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.0.0.Alpha2 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.0.0.Beta1 > > > {noformat} > 11:16:21.413 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project infinispan-checkstyle: The packaging for this project did not assign a file to the build artifact -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-cli) on project infinispan-checkstyle: The packaging for this project did not assign a file to the build artifact > {noformat} > https://ci.infinispan.org/job/Infinispan/job/master/1005 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10532) org.antlr.runtime.RecognitionException class leaks from logger interface of object-filter

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10532?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10532: ----------------------------------- 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) > org.antlr.runtime.RecognitionException class leaks from logger interface of object-filter > ----------------------------------------------------------------------------------------- > > Key: ISPN-10532 > URL: https://issues.jboss.org/browse/ISPN-10532 > Project: Infinispan > Issue Type: Bug > 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 > > > This prevents ANTLR to be actually shaded. The effect of the shade plugin is quasi-no-op. The dependency is still carried around and hacks have been done to cope with it https://github.com/infinispan/infinispan/blob/10.0.0.CR1/feature-pack/emb... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9843) RocksDBStore should not write entire MarshalledEntry as store value

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9843?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9843: ---------------------------------- 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) > 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)

6 years, 4 months

1
0
0 / 0

[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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9877) Nashorn and sun.scription modules optional for embedded feature-packs

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9877?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9877: ---------------------------------- 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) > Nashorn and sun.scription modules optional for embedded feature-packs > --------------------------------------------------------------------- > > Key: ISPN-9877 > URL: https://issues.jboss.org/browse/ISPN-9877 > 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)

6 years, 4 months

1
0
0 / 0

[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)

6 years, 4 months

1
0
0 / 0

[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)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10519) Upgrade to protostream-4.3.0.Alpha11

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10519?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10519: ----------------------------------- 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) > Upgrade to protostream-4.3.0.Alpha11 > ------------------------------------- > > Key: ISPN-10519 > URL: https://issues.jboss.org/browse/ISPN-10519 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[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)

6 years, 4 months

1
0
0 / 0

[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)

6 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019