[JBoss JIRA] (ISPN-3478) Polish CS API revamp
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3478?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3478:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/2062, https://github.com/infinispan/infinispan-cachestore-leveldb/pull/6, https://github.com/infinispan/infinispan-server/pull/149, https://github.com/infinispan/infinispan-cachestore-rest/pull/5
> Polish CS API revamp
> --------------------
>
> Key: ISPN-3478
> URL: https://issues.jboss.org/browse/ISPN-3478
> Project: Infinispan
> Issue Type: Feature Request
> Affects Versions: 6.0.0.Alpha4
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 6.0.0.Beta1
>
>
> Still some TODOs:
> * 3.4 name consistently
> * Make ClusterStore configuration match the name (ClusterLoader)
> * 3.5 - move the params from init to an instance named InitializationContext that contains context info (is singleton etc, and also marshaller etc)
> * 4 - push pull request
> * 5 - remove all the "store" references from the code
> * 6 - don't use "bulk" in the name of them methods ...
> * 7 - make CacheLoaderException runtime
> * 8 - rename EntryFactory in ContextEntryFactory and MVCCEntry in ContextEntry
> * 9 - make StoreConfiguration aware of purging etc
> * 10 - add removed test to the compatibility module: ConfigurationCompatibilityTest.testModeShapeStoreConfiguration
> * - FileCacheStoreTest
> * 11 - remove EHCache2InfinispanTransformerTest and other product migration tests in general + user manual entries
> * 12 - Config: loaders/shared should be configured on a per cache basis.
> * - action - lockAcquisitionTimeout (moved to bucket), concurrencyLevel (mode to bucket),
> * purgerThreads & purgeSynchronously(removed as purging is async anyway)
> * - purge on startup should be renamed to clean on startup as purging, as a term, is already used for cleaning
> * up expired entries
> * 13 - add test to show that notification happens for purged entries
> * 14 - add interruption support in the code that invokes the CacheLoaderTask
> * 15 - allow the number of map/reduce threads that iterate over the store to be configured
> * 16 - Make ByteBuffer an interface and add a factory for it. Also consider adding a factory for MarshalledEntry
> * 17 - rename org.infinispan.loader -> o.i.persistence
> * 18 - remote gets should not serialize the entries but operate on bytebuffers directly
> * 19 - make sure cachestore string is not present int he source base
> * 20 - https://community.jboss.org/thread/232195
> * 21 - remove DataManipulationHelper
> * 22 - move Sleepycat Berkeley DB Java Edition license to the right place
> * 23 removed 5.2 and 5.3 config files from the test resource dir
> * 24 make the name consistent in the other modules 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, 7 months
[JBoss JIRA] (ISPN-2177) Refactor AbstractCacheTransaction
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2177?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2177:
--------------------------------
Assignee: William Burns (was: Mircea Markus)
> Refactor AbstractCacheTransaction
> -----------------------------------
>
> Key: ISPN-2177
> URL: https://issues.jboss.org/browse/ISPN-2177
> Project: Infinispan
> Issue Type: Feature Request
> Components: Transactions
> Affects Versions: 5.1.2.FINAL
> Reporter: Mircea Markus
> Assignee: William Burns
> Labels: refactoring, transaction
> Fix For: 6.0.0.CR1
>
>
> There are several collections holding transaction related information in the AbstractCacheTransaction:
> - lockedKeys: this holds all the keys that were actually locked on the local node
> - affectedKeys: this holds all the keys that were acquired by the transaction allover the cluster
> - backupKeyLocks: this holds all the locks for which the local node is a secondary data owner.
> To do:
> - affectedKeys belongs to LocalCacheTransaction(subclass) and no point in having it in the AbstractCacheTransaction
> - a better name for affectedKeys might be "clusterLockedKey" and for lockedKeys --> localLokedKeys
> - also add a Javadoc explaining the correlation between these key groups
--
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, 7 months
[JBoss JIRA] (ISPN-3509) Infinispan does not support postgresplus database
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3509?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-3509:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1007991
> Infinispan does not support postgresplus database
> -------------------------------------------------
>
> Key: ISPN-3509
> URL: https://issues.jboss.org/browse/ISPN-3509
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 6.0.0.Alpha3, 6.0.0.Alpha4
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Attachments: server.log
>
>
> When I run our functional tests inside EAP server against postgresplus database following error occured
> 17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
> at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
> Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
>
--
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, 7 months
[JBoss JIRA] (ISPN-3509) Infinispan does not support postgresplus database
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3509?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3509:
-----------------------------------------------
Vitalii Chepeliuk <vchepeli(a)redhat.com> made a comment on [bug 1007991|https://bugzilla.redhat.com/show_bug.cgi?id=1007991]
See description of problem here
https://issues.jboss.org/browse/ISPN-3509
> Infinispan does not support postgresplus database
> -------------------------------------------------
>
> Key: ISPN-3509
> URL: https://issues.jboss.org/browse/ISPN-3509
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 6.0.0.Alpha3, 6.0.0.Alpha4
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Attachments: server.log
>
>
> When I run our functional tests inside EAP server against postgresplus database following error occured
> 17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
> at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
> Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
>
--
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, 7 months
[JBoss JIRA] (ISPN-3509) Infinispan does not support postgresplus database
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-3509?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-3509:
------------------------------------
Description:
When I run our functional tests inside EAP server against postgresplus database following error occured
17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
was:
When I run our functional tests against postgresplus database following error occured
17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> Infinispan does not support postgresplus database
> -------------------------------------------------
>
> Key: ISPN-3509
> URL: https://issues.jboss.org/browse/ISPN-3509
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 6.0.0.Alpha3, 6.0.0.Alpha4
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Attachments: server.log
>
>
> When I run our functional tests inside EAP server against postgresplus database following error occured
> 17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
> at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
> Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
>
--
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, 7 months
[JBoss JIRA] (ISPN-3509) Infinispan does not support postgresplus database
by Vitalii Chepeliuk (JIRA)
Vitalii Chepeliuk created ISPN-3509:
---------------------------------------
Summary: Infinispan does not support postgresplus database
Key: ISPN-3509
URL: https://issues.jboss.org/browse/ISPN-3509
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 6.0.0.Alpha4, 6.0.0.Alpha3
Reporter: Vitalii Chepeliuk
Assignee: Mircea Markus
Attachments: server.log
When I run our functional tests against postgresplus database following error occured
17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
--
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, 7 months
[JBoss JIRA] (ISPN-3509) Infinispan does not support postgresplus database
by Vitalii Chepeliuk (JIRA)
[ https://issues.jboss.org/browse/ISPN-3509?page=com.atlassian.jira.plugin.... ]
Vitalii Chepeliuk updated ISPN-3509:
------------------------------------
Attachment: server.log
Attach server.log of EAP server
> Infinispan does not support postgresplus database
> -------------------------------------------------
>
> Key: ISPN-3509
> URL: https://issues.jboss.org/browse/ISPN-3509
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 6.0.0.Alpha3, 6.0.0.Alpha4
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Attachments: server.log
>
>
> When I run our functional tests against postgresplus database following error occured
> 17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
> at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
> Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
>
--
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, 7 months