[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/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 (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)
> 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, 5 months
[JBoss JIRA] (ISPN-6161) [Remote query] Indexes should be created only for annotated message types
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/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 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> [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, 5 months
[JBoss JIRA] (ISPN-10723) JMX registration cleanup
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10723?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10723:
------------------------------------------
Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: DataGrid Sprint #34, DataGrid Sprint #35)
> JMX registration cleanup
> ------------------------
>
> Key: ISPN-10723
> URL: https://issues.jboss.org/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, 5 months
[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/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 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> Remove support for 'indexed_by_default' option in protobuf schemas
> ------------------------------------------------------------------
>
> Key: ISPN-9083
> URL: https://issues.jboss.org/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, 5 months
[JBoss JIRA] (ISPN-9186) Upgrade Protostream to 4.3.0.Alpha8
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-9186?page=com.atlassian.jira.plugin.... ]
Pedro Zapata Fernandez updated ISPN-9186:
-----------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35)
> Upgrade Protostream to 4.3.0.Alpha8
> -----------------------------------
>
> Key: ISPN-9186
> URL: https://issues.jboss.org/browse/ISPN-9186
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Remote Querying
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 5 months