August 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-686) JdbcStringBasedCacheStore loads previous data from store before an insert

by Sanne Grinovero (JIRA)

JdbcStringBasedCacheStore loads previous data from store before an insert ------------------------------------------------------------------------- Key: ISPN-686 URL: https://jira.jboss.org/browse/ISPN-686 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.2.0.ALPHA2, 4.1.0.Final, 4.0.0.Final Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.2.0.Final, 5.0.0.Final The JdbcStringBasedCacheStore implementation loads the previous data on an insert to find out if it should generate an UPDATE or INSERT statement, while it would perform much better to just verify if the primary key exists. On top of this, some databases provide ways to avoid the need to check at all, like MySQL's " INSERT ... ON DUPLICATE KEY UPDATE" [http://dev.mysql.com/doc/refman/5.0/en/insert-on-duplicate.html] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

7
29
0 / 0

[JBoss JIRA] (ISPN-2236) Test JDBC CacheStore with MSSQL, Informix, DB2 and PGSQL

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2236: ---------------------------------- Summary: Test JDBC CacheStore with MSSQL, Informix, DB2 and PGSQL Key: ISPN-2236 URL: https://issues.jboss.org/browse/ISPN-2236 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Affects Versions: 5.1.6.FINAL Reporter: Thomas Fromm Assignee: Mircea Markus Needs to be tested. I expect problems like I got when I started using ISPN with Oracle. Consider Maven profile for creating automated tests of them with internal JBoss Test infrastructure. -- 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

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2206) Query returns nulls if cache entries were removed and transaction is still not commited

by Marko Lukša (JIRA)

Marko Lukša created ISPN-2206: --------------------------------- Summary: Query returns nulls if cache entries were removed and transaction is still not commited Key: ISPN-2206 URL: https://issues.jboss.org/browse/ISPN-2206 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 5.2.0.ALPHA1 Reporter: Marko Lukša Assignee: Sanne Grinovero When using indexLocalOnly=true, the Lucene index is updated when the transaction is commited. After removing an entry from the cache (and before commiting the transaction), queries will still match the entry, but since the entry is no longer in the cache, the list returned by the query will contain a null value. This forces clients to always check whether elements of the collection returned by queries are null. IMO, Ispan-query should handle this and simply skip the entries that were matched in the index, but are no longer in the cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] (ISPN-2066) Simplify configuration of an Infinispan backend in the Hibernate Search engine of Infinispan Query

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2066: ------------------------------------- Summary: Simplify configuration of an Infinispan backend in the Hibernate Search engine of Infinispan Query Key: ISPN-2066 URL: https://issues.jboss.org/browse/ISPN-2066 Project: Infinispan Issue Type: Enhancement Components: Querying Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1 Make sure we can inject the needed caches in the Hibernate Search engine being started by Query, and also that the custom commands being sent from the engine are "routed to" the same engine again for processing on the listener side related to https://community.jboss.org/docs/DOC-18370 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
9
0 / 0

[JBoss JIRA] (ISPN-2221) Configuration builders and parsers for JDBC Cache Store

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2221: ------------------------------------- Summary: Configuration builders and parsers for JDBC Cache Store Key: ISPN-2221 URL: https://issues.jboss.org/browse/ISPN-2221 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.Final Add configuration builders and parser support to the JDBC Cache Store -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2199) Create a IGNORE_RETURN_VALUES flag

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2199: -------------------------------------- Summary: Create a IGNORE_RETURN_VALUES flag Key: ISPN-2199 URL: https://issues.jboss.org/browse/ISPN-2199 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.2.0.FINAL We should create such flag to encompass situations that involve, amongst others, both forcing SKIP_REMOTE_LOOKUP, SKIP_CACHE_LOAD...etc. See attached discussion for more info. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
4
0 / 0

[JBoss JIRA] (ISPN-2164) Return value of Cache.remove(key) not consistent in transactional context

by Carsten Lohmann (JIRA)

Carsten Lohmann created ISPN-2164: ------------------------------------- Summary: Return value of Cache.remove(key) not consistent in transactional context Key: ISPN-2164 URL: https://issues.jboss.org/browse/ISPN-2164 Project: Infinispan Issue Type: Bug Components: Core API, Transactions Affects Versions: 5.1.5.FINAL Reporter: Carsten Lohmann Assignee: Mircea Markus I have a scenario where multiple threads attempt to remove the same key concurrently via "cache.remove(key)" (each thread having explicitly started a transaction). I expect only one thread to succeed, ie. only one invocation of "cache.remove(key)" to return a non-null value. But that is not the case, the return value of "cache.remove(key)" is non-null for more than one thread. In that sense, "cache.remove(key)" seems to behave differently from "cache.remove(key, value)". The bug can be reproduced by using a test analogous to the one in "DummyTxTest" (ISPN-2077), but using "cache.remove(key)" instead of "cache.remove(key, value)". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
14
0 / 0

[JBoss JIRA] (ISPN-2212) AtomicMap contents not replicated with replication queue

by Takayoshi Kimura (JIRA)

Takayoshi Kimura created ISPN-2212: -------------------------------------- Summary: AtomicMap contents not replicated with replication queue Key: ISPN-2212 URL: https://issues.jboss.org/browse/ISPN-2212 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 5.2.0.ALPHA2, 5.1.6.FINAL Reporter: Takayoshi Kimura Assignee: Manik Surtani When we use AtomicMap with replication queue, the contents are not replicated. Normally we get delta, replicate it in prepare phase then commit the tx. However when replication queue enabled, commit tx comes first and then replication. In ReadCommittedNode.commit() we clear delta out, so nothing is replicated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
9
0 / 0

[JBoss JIRA] (ISPN-2200) Make ClusterCacheLoader configurable via new configuration API

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2200: ------------------------------------- Summary: Make ClusterCacheLoader configurable via new configuration API Key: ISPN-2200 URL: https://issues.jboss.org/browse/ISPN-2200 Project: Infinispan Issue Type: Feature Request Components: Configuration, Loaders and Stores Affects Versions: 5.2.0.ALPHA2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Minor Fix For: 5.2.0.FINAL ClusterCacheLoader should have a proper XML configuration element and a org.infinispan.configuration compatible API -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ISPN-2228) Upgrade configuration converters to 5.2 schema

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2228: ------------------------------------- Summary: Upgrade configuration converters to 5.2 schema Key: ISPN-2228 URL: https://issues.jboss.org/browse/ISPN-2228 Project: Infinispan Issue Type: Task Components: Configuration Affects Versions: 5.2.0.ALPHA2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.Alpha3 The configuration converters should produce 5.2.x-compatible configuration files. Also the tests should be upgraded to use the new configuration API -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2012