January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9322) Remove all usages of @IndexedField protostream annotation

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9322?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9322: ----------------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Remove all usages of @IndexedField protostream annotation > --------------------------------------------------------- > > Key: ISPN-9322 > URL: https://issues.redhat.com/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)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9083?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9083: ----------------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.redhat.com/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 10.0.0.Final > > > All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. > Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10 - usages will be ignored after this point. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11106) Export 'base' and 'vendor' microprofile metric registries

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11106?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11106: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Export 'base' and 'vendor' microprofile metric registries > --------------------------------------------------------- > > Key: ISPN-11106 > URL: https://issues.redhat.com/browse/ISPN-11106 > Project: Infinispan > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Final > > > These registries were not populated and smallrye metrics has a little utility that could populate them cheaply (few lines of code) with information extracted from various java.lang.management.PlatformManagedObject implementations. This is achieved by scraping the platform mbeans. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11170) Infinispan directory does not work with pre-declared indexed entities

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11170?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11170: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Infinispan directory does not work with pre-declared indexed entities > --------------------------------------------------------------------- > > Key: ISPN-11170 > URL: https://issues.redhat.com/browse/ISPN-11170 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 9.4.18.Final, 10.1.2.Final > > > This config combination leads to a circular initialisation dependency of the infinispan directory which has the potential to lead to deadlock, depending on the order the user cache and the infinispan directory's internal caches are started. > This problem of cache dependencies was always known and the LifecycleManager of query module has code to mitigate it. Unfortunately the code is wrong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11173) Add --excludeGeneratedBy cmdline option to javadoc tool to allow excluding classes generated by certain code generators

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11173?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11173: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Add --excludeGeneratedBy cmdline option to javadoc tool to allow excluding classes generated by certain code generators > ----------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-11173 > URL: https://issues.redhat.com/browse/ISPN-11173 > Project: Infinispan > Issue Type: Bug > Components: Documentation > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.2.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10723) JMX registration cleanup

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-10723?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-10723: ------------------------------------------ Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > JMX registration cleanup > ------------------------ > > Key: ISPN-10723 > URL: https://issues.redhat.com/browse/ISPN-10723 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Final > > > - all jmx registration should happen via CacheManagerJmxRegistration/CacheJmxRegistration - we should not have other classes using JmxUtil.buildJmxDomain > - there are very few legitimate direct usages of JmxUtil.lookupMBeanServer; all else must go > - some registrations are not currently ResourceDMBeans; these need to be converted > - use of registerExternalMBean should be converted to registerMBean > - avoid performing the unregistration manually. Components registered with registerMBean will be unregistered automatically -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10544) Remove dependencies on java.beans module

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-10544?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-10544: ------------------------------------------ Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Remove dependencies on java.beans module > ----------------------------------------- > > Key: ISPN-10544 > URL: https://issues.redhat.com/browse/ISPN-10544 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR2 > > > Some Infinispan morning fitness to shed off java beans module -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10534) ProtoStreamMarshaller.getSerializationContext fails with unclear message

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-10534?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-10534: ------------------------------------------ Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > ProtoStreamMarshaller.getSerializationContext fails with unclear message > ------------------------------------------------------------------------ > > Key: ISPN-10534 > URL: https://issues.redhat.com/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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6161) [Remote query] Indexes should be created only for annotated message types

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-6161?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-6161: ----------------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > [Remote query] Indexes should be created only for annotated message types > ------------------------------------------------------------------------- > > Key: ISPN-6161 > URL: https://issues.redhat.com/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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-4075?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez 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, DataGrid Sprint #38, DataGrid Sprint #39 (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, DataGrid Sprint #37, DataGrid Sprint #38) > State transfer should preserve the creation timestamp of entries > ---------------------------------------------------------------- > > Key: ISPN-4075 > URL: https://issues.redhat.com/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, 2 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 January 2020