July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2915) Deprecate JBossTransactionManagerLookup as it is redundant

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2915?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2915: -------------------------------- Fix Version/s: 6.0.0.Final > Deprecate JBossTransactionManagerLookup as it is redundant > ---------------------------------------------------------- > > Key: ISPN-2915 > URL: https://issues.jboss.org/browse/ISPN-2915 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 5.2.1.Final > Reporter: Martin Gencur > Assignee: Mircea Markus > Priority: Minor > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > JDNI lookups from JBossTransactionManagerLookup are all covered by the GenericTransactionManagerLookup. > Furthermore, the JBoss JNDI names are requested first in the GenericTML so there's is no point in having two different TransactioManager lookup classes serving the same purpose. > I suggest that we deprecate the JBossTransactionManagerLookup in the next release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1295) Deprecate transport properties and replace with configuration on transport itself

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1295?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1295: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Deprecate transport properties and replace with configuration on transport itself > --------------------------------------------------------------------------------- > > Key: ISPN-1295 > URL: https://issues.jboss.org/browse/ISPN-1295 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.0.0.CR8 > Reporter: Pete Muir > Assignee: Pete Muir > > Currently transport properties are detyped and confusing for users as it sounds like the should actually configure properties of the transport, not properties of the transport configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1295) Deprecate transport properties and replace with configuration on transport itself

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1295?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-1295: ------------------------------------- better to handle this as part of the configuration revamp/7.0. > Deprecate transport properties and replace with configuration on transport itself > --------------------------------------------------------------------------------- > > Key: ISPN-1295 > URL: https://issues.jboss.org/browse/ISPN-1295 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.0.0.CR8 > Reporter: Pete Muir > Assignee: Pete Muir > > Currently transport properties are detyped and confusing for users as it sounds like the should actually configure properties of the transport, not properties of the transport configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3105) Design query API for both embedded use and Java Hot Rod client

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3105?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3105: -------------------------------- Priority: Blocker (was: Major) > Design query API for both embedded use and Java Hot Rod client > -------------------------------------------------------------- > > Key: ISPN-3105 > URL: https://issues.jboss.org/browse/ISPN-3105 > Project: Infinispan > Issue Type: Task > Components: Querying > Reporter: Mircea Markus > Assignee: Adrian Nistor > Priority: Blocker > Labels: remote-query > Fix For: 6.0.0.Alpha2, 6.0.0.Final > > > There are several parts to this JIRA. > 1. We'd need a query API to be able to run queries on a cache. For example: > {code:java} > // Super-interface to Cache and RemoteCache > public interface BasicCache { > ... > Set<?> runQuery(Filter f); > ... > } > {code} > such that the same API can be used for remote (for the Hot Rod Java client) as well as embedded querying. > 2. Since the approach we're using is effectively to look at the global data set and apply a series of filters, we'd need a {{FilterBuilder}} as well to create such filters. E.g., > {code:java} > new FilterBuilder().matches("name", "QueenElizabeth").and().greaterThan("age", 65).build(); > {code} > The Hibernate Search query DSL could probably be used for inspiration. > 3. Further, we should still have an API that takes in Lucene Query objects - as per the existing Query API - but this would be for embedded mode only. E.g., > {code:java} > public interface Cache { > ... > Set<?> runLuceneQuery(LuceneQuery q); > ... > } > {code} > 4. Projections. We may also want to support projections. This needs thought. Again, Hibernate Search's APIs can provide inspiration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2640) Design security functionality in Infinispan

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2640?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2640: -------------------------------- Assignee: Tristan Tarrant (was: Adrian Nistor) > Design security functionality in Infinispan > ------------------------------------------- > > Key: ISPN-2640 > URL: https://issues.jboss.org/browse/ISPN-2640 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Tristan Tarrant > Priority: Blocker > Fix For: 6.0.0.Final > > > The task is about gathering the requirements, discussing them with the community and sum them up in a requirements document. OpenShift team should also be involved in defining the requirements for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2915) Deprecate JBossTransactionManagerLookup as it is redundant

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2915?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2915: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1940 > Deprecate JBossTransactionManagerLookup as it is redundant > ---------------------------------------------------------- > > Key: ISPN-2915 > URL: https://issues.jboss.org/browse/ISPN-2915 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 5.2.1.Final > Reporter: Martin Gencur > Assignee: Mircea Markus > Priority: Minor > Fix For: 6.0.0.Alpha1 > > > JDNI lookups from JBossTransactionManagerLookup are all covered by the GenericTransactionManagerLookup. > Furthermore, the JBoss JNDI names are requested first in the GenericTML so there's is no point in having two different TransactioManager lookup classes serving the same purpose. > I suggest that we deprecate the JBossTransactionManagerLookup in the next release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3280) HotRod client should depend on commons and not core

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3280?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3280: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1939 > HotRod client should depend on commons and not core > --------------------------------------------------- > > Key: ISPN-3280 > URL: https://issues.jboss.org/browse/ISPN-3280 > Project: Infinispan > Issue Type: Sub-task > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1350) Create dynamic object support instead of pojos

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1350?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-1350. --------------------------------- Resolution: Out of Date we're adding protobuf files to define the objetc schema and also additional tooling (potentially protobuff annotations) to define the indexes. > Create dynamic object support instead of pojos > ---------------------------------------------- > > Key: ISPN-1350 > URL: https://issues.jboss.org/browse/ISPN-1350 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Magnus Magnus > Assignee: Manik Surtani > Fix For: 6.0.0.Final > > > Dynamic structures should be supported. Eg List and Map based dynamic objects (or generate pojos with asm like it is in eclipse link) which structure could be described in an xml file(included substructures). XML descriptor should be able to modify in runtime with a version number. XML descriptor could contain the indexable fields as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3194) Create diagnostics dumping tool

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3194?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3194: -------------------------------- Fix Version/s: (was: 6.0.0.Final) (was: 6.0.0.Alpha1) > Create diagnostics dumping tool > ------------------------------- > > Key: ISPN-3194 > URL: https://issues.jboss.org/browse/ISPN-3194 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Affects Versions: 5.3.0.Final > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: diagnostics > > A simple script that an end-user can run on an existing cluster, that will: > 1. Connect to a given node via JMX > 2. Get a list of all caches on all nodes > 3. Run JMX calls on each cache on each node to capture diagnostic data > 4. Serialise this data (maybe JSON?), zip it up. > This will allow end-users to share such stats for debugging and perf tuning. > Diagnostic data to be captured would include all JMX info on hit/miss ratio, RPC performance, transaction commit/rollback rates, config details, time budgeting info, etc. > This tool would require that JMX statistics are enabled and running for a while before the snapshot is captured. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1355) Create an ultra high performance serialization as an internal cache format. Eg: with Kryo

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1355?page=com.atlassian.jira.plugin.... ] Mircea Markus closed ISPN-1355. ------------------------------- Resolution: Rejected JBoss Marshalling is quite fast as it is. I'll close this till there's a benchmark to back the benefit of considering an alternative > Create an ultra high performance serialization as an internal cache format. Eg: with Kryo > ----------------------------------------------------------------------------------------- > > Key: ISPN-1355 > URL: https://issues.jboss.org/browse/ISPN-1355 > Project: Infinispan > Issue Type: Feature Request > Reporter: Magnus Magnus > Assignee: Manik Surtani > Priority: Optional > > Create an ultra high performance serialization for internal cache format. Eg: with Kryo or something like that. > Serialized data should be able to compress as well with a high performance compression algorithm. Use Snappy compression from Google. > With this solution the memory requirement could be reduced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 July 2013