January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3890) Store data in binary format for C/S mode

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3890?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3890: ------------------------------------- Assignee: (was: Mircea Markus) > Store data in binary format for C/S mode > ---------------------------------------- > > Key: ISPN-3890 > URL: https://issues.jboss.org/browse/ISPN-3890 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Mircea Markus > Priority: Minor > > ATM the data is stored as POJO. Storing the data in binary mode would reduce the number of serialization and increase performance. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4280) Enhance Distributed Iterator when a shared loader is used.

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4280?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4280: ------------------------------------- Assignee: (was: Mircea Markus) > Enhance Distributed Iterator when a shared loader is used. > ---------------------------------------------------------- > > Key: ISPN-4280 > URL: https://issues.jboss.org/browse/ISPN-4280 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > > It may be possible when a shared loader is present to not have to request those values from the remote nodes and instead do it on the originator. This has some issues with activation/passivation that would need some additional thought though. Doing so would allow for much more efficient access from the store since it is from 1 node only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3546) Migrate mongodb cache store to the 6.0 cachestore API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3546?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3546: ------------------------------------- Assignee: (was: Mircea Markus) > Migrate mongodb cache store to the 6.0 cachestore API > ----------------------------------------------------- > > Key: ISPN-3546 > URL: https://issues.jboss.org/browse/ISPN-3546 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Mircea Markus > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3660) Allow CacheStores to access fields of data for which the schema is known

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3660?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3660: ------------------------------------- Assignee: (was: Mircea Markus) > Allow CacheStores to access fields of data for which the schema is known > ------------------------------------------------------------------------ > > Key: ISPN-3660 > URL: https://issues.jboss.org/browse/ISPN-3660 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Tristan Tarrant > > Currently cache stores read/write data from persistent storage as an opaque blob. Where we have access to the schema of data, we could expose this schema to the store so that it can write the single fields in a more appropriate fashion for the underlying persistence layer, e.g. write individual fields as columns in a relational database table or use the rich mapping of document stores (e.g. CouchDB, MongoDB). > Additionally, stores should also be able to do the same for the entry's metadata (e.g. version, etc), as is already done for expiration. > This technique can enable analysis / modification of data using the specific store tools (e.q. sqlplus, etc), or load pre-existing data to be served by the cache -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3372) Make AdvanceCache.getXaResource throw an exception if the cache is not XA + recovery enabled

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3372?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3372: ------------------------------------- Assignee: (was: Mircea Markus) > Make AdvanceCache.getXaResource throw an exception if the cache is not XA + recovery enabled > -------------------------------------------------------------------------------------------- > > Key: ISPN-3372 > URL: https://issues.jboss.org/browse/ISPN-3372 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Priority: Minor > > also on the returned XAResource instance make sure that all methods besides the recovery releated ones would throw an exception. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3538) Align recovery() enabling in Configuration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3538?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3538: ------------------------------------- Assignee: (was: Mircea Markus) > Align recovery() enabling in Configuration > ------------------------------------------- > > Key: ISPN-3538 > URL: https://issues.jboss.org/browse/ISPN-3538 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 6.0.0.Beta1 > Reporter: Jiří Holuša > Priority: Minor > > When configuring recovery via ConfigurationBuilder, calling .transaction().recovery() will by default enable recovery, so no need to call enable(). > But when calling e.g. globalJmxStatistics() in GlobalConfigurationBuilder, you have to explicitly call enable(). Another example is when configuring L1 cache, e.g. l1().lifespan(60000L), you also have to explicitly call enable(). > I think it would be nice to have it consistent. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2491) Order of locks in optimistic locking is not strict

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2491?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2491: ------------------------------------- Assignee: (was: Mircea Markus) > Order of locks in optimistic locking is not strict > -------------------------------------------------- > > Key: ISPN-2491 > URL: https://issues.jboss.org/browse/ISPN-2491 > Project: Infinispan > Issue Type: Quality Risk > Components: Transactions > Affects Versions: 5.1.8.Final, 5.2.0.Beta3 > Reporter: Radim Vansa > Priority: Minor > > In OptimisticLockingInterceptor, the keys are ordered according to their hash. However, the hashes can still collide, which may result in a deadlock if two keys with identical hash (only 32-bit) are sorted to different order. We should try to check if the keys are Comparable or let user provide some comparator class in config, and use the compare of hash only as the last resort. > In all cases, a warning should be emitted if the compare operation had non-strict result. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3079) xsite replication custom failurePolicy does not work with ASYNC strategy

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3079?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3079: ------------------------------------- Assignee: (was: Mircea Markus) > xsite replication custom failurePolicy does not work with ASYNC strategy > ------------------------------------------------------------------------ > > Key: ISPN-3079 > URL: https://issues.jboss.org/browse/ISPN-3079 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 5.2.5.Final > Environment: ISPN 5.2.5.final > Reporter: dex chen > > I configure xsite backupFailurePolicy="CUSTOM" and specified failurePolicyClass (see below xml configuration). > When the strategy is set to "ASYNC", the failurePolicyClass code is never got invoked!! > But, same code will will be invoked if the strategy is set to "SYNC". > ..... > <sites> > <backups> > <backup site="NYC" strategy="ASYNC" backupFailurePolicy="CUSTOM" failurePolicyClass="com.test.cluster.infinispan.CrossSiteReplicationFailurePolicy" timeout="12003"/> > </backups> > </sites> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3551) Migrate bdbje cache store to the 6.0 cachestore API

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3551?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3551: ------------------------------------- Assignee: (was: Mircea Markus) > Migrate bdbje cache store to the 6.0 cachestore API > ---------------------------------------------------- > > Key: ISPN-3551 > URL: https://issues.jboss.org/browse/ISPN-3551 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Mircea Markus > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3898) Missing dependencies in infinispan-server-jgroups

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3898?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3898: ------------------------------------- Assignee: (was: Mircea Markus) > Missing dependencies in infinispan-server-jgroups > ------------------------------------------------- > > Key: ISPN-3898 > URL: https://issues.jboss.org/browse/ISPN-3898 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Valerio Schiavoni > Attachments: versions_pom.diff > > > Maven complains about unresolvable dependencies: > [ERROR] Failed to execute goal on project infinispan-server-jgroups: Could not resolve dependencies for project org.infinispan.server:infinispan-server-jgroups:jar:7.0.0-SNAPSHOT: The following artifacts could not be resolved: org.jboss.byteman:byteman:jar:2.0.1, org.jboss.byteman:byteman-submit:jar:2.0.1, org.jboss.byteman:byteman-install:jar:2.0.1: Could not find artifact org.jboss.byteman:byteman:jar:2.0.1 in central > (same happens with the other byteman dependencies). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 2015