March 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1833) Add EmbeddedCacheManager.getGlobalComponentRegistry

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1833?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1833. --------------------------------- Resolution: Done > Add EmbeddedCacheManager.getGlobalComponentRegistry > --------------------------------------------------- > > Key: ISPN-1833 > URL: https://issues.jboss.org/browse/ISPN-1833 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > > You should be able to retrieve the global component registry out of the EmbeddedCacheManager. > Rather that having to do: > cache.getAdvancedCache().getComponentRegistry().getGlobalComponentRegistry() -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-984) Add ability to retrieve cache names remotely in Hot Rod

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-984?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant closed ISPN-984. -------------------------------- Resolution: Duplicate Issue > Add ability to retrieve cache names remotely in Hot Rod > ------------------------------------------------------- > > Key: ISPN-984 > URL: https://issues.jboss.org/browse/ISPN-984 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: hotrod > > A new operation would be needed to retrieve all cache names that are configured and running. > A new version of the protocol would need to be set up to deal with the new operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-7979) Include all component licenses in distributions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7979?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7979: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Include all component licenses in distributions > ----------------------------------------------- > > Key: ISPN-7979 > URL: https://issues.jboss.org/browse/ISPN-7979 > Project: Infinispan > Issue Type: Task > Components: Build > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 9.3.0.Final > > > The distributions should include licenses for all components -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8951) LevelDB store parser should not exist past version 8.0

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8951?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8951: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1 > LevelDB store parser should not exist past version 8.0 > ------------------------------------------------------ > > Key: ISPN-8951 > URL: https://issues.jboss.org/browse/ISPN-8951 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Fix For: 9.3.0.Alpha1 > > > The LevelDB config parser should refuse to parse schemas newer than 8.0. Namespace-less XMLs should fail to parse with 9.x+ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8952) Parser namespaces should support version wildcards

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8952?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8952: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Parser namespaces should support version wildcards > -------------------------------------------------- > > Key: ISPN-8952 > URL: https://issues.jboss.org/browse/ISPN-8952 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.3.0.Alpha1, 9.3.0.Final > > > The namespace annotations require a maintenance burden when bumping schema versions. By adding support for version wildcards with support boundaries (since, until) we can simplify maintenance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-375) Enable Hot Rod clients to start transactions

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-375?page=com.atlassian.jira.plugin.s... ] Tristan Tarrant updated ISPN-375: --------------------------------- Sprint: Sprint 9.3.0.Beta1 > Enable Hot Rod clients to start transactions > -------------------------------------------- > > Key: ISPN-375 > URL: https://issues.jboss.org/browse/ISPN-375 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Priority: Blocker > Fix For: 9.3.0.Final > > > It might be useful to allow Hot Rod clients to start transactions within Hot Rod servers. The possibility of clients participating in the actual transaction, i.e. being an XAResource, should not be imposed since this might be less than trivial to achieve in non-Java environments. The alternative would be to allow clients to start Hot Rod server local transactions only. > This would require enhancing Hot Rod spec to have some begin/commit/rollback commands that return a tx id, and for clients to be able to send this id as part of each command that should participate in the transaction. > Pitfalls to avoid include avoiding a transaction to be propagated over several Hot Rod servers. IOW, to simplify things, if a tx is started in server A, all ops within that tx should be directed to tx. Load balancing could still happen but would need to be tx sticky. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1213) TreeCache expires parents that have children

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1213?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-1213. --------------------------------- Resolution: Out of Date > TreeCache expires parents that have children > -------------------------------------------- > > Key: ISPN-1213 > URL: https://issues.jboss.org/browse/ISPN-1213 > Project: Infinispan > Issue Type: Bug > Components: Eviction > Affects Versions: 4.2.1.FINAL > Reporter: Todd Ciezadlo > Assignee: Pedro Ruivo > Attachments: ExpirationTest.java, TreeCacheUtil.java > > > TreeCache parents expire according to the max-idle value even if they contain children. This puts the tree cache in an inconsistent state since the "dangling" children can be retrieved through TreeCache.get(FQN, String) calls, but cannot be traversed to through TreeCache.getRoot() and Node.getChildren() calls. > Attached unit test to to reproduce. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8981) Generate Hot Rod parser automatically

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8981?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8981: ---------------------------------- Sprint: Sprint 9.3.0.Beta1 > Generate Hot Rod parser automatically > ------------------------------------- > > Key: ISPN-8981 > URL: https://issues.jboss.org/browse/ISPN-8981 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.3.0.Final > > > This JIRA has two objectives: > 1. reduce number of allocated objects > 2. improve the parsing on server side to avoid chains of lambda mappings > Manual parsing of Hot Rod protocol, invoking recursive methods that return {{Optional}}s or {{Optional<Optional<...>}}s seems to generate a lot of garbage. A better approach would be a finite state automaton that would read the byte stream and invoke callbacks. > Such automaton can be generated from a high-level grammar as part of the build process. > Along with these changes we can remove the {{Response}} abstraction and write responses directly as {{ByteBuf}}s. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8618) Async Hot Rod client

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8618?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8618: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Async Hot Rod client > -------------------- > > Key: ISPN-8618 > URL: https://issues.jboss.org/browse/ISPN-8618 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Radim Vansa > Assignee: Radim Vansa > > While we expose asynchronous operations in RemoteCache and more recently in counters and multimap, all communication is currently synchronous. > This is an umbrella task for handling communication asynchronously. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-9003) Clustered maxIdle expiration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9003?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9003: ---------------------------------- Sprint: Sprint 9.3.0.Alpha1 > Clustered maxIdle expiration > ---------------------------- > > Key: ISPN-9003 > URL: https://issues.jboss.org/browse/ISPN-9003 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: William Burns > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2018