[
https://issues.jboss.org/browse/ISPN-6798?page=com.atlassian.jira.plugin....
]
Sanne Grinovero updated ISPN-6798:
----------------------------------
Description:
The "shared" configuration attribute is defaulting to _false_ even for
database-based CacheStore instances as the attribute is defined in the parent of all
{{CacheStore}} types.
The attribute isn't very visible either, as it's not explicitly listed among the
available attributes (because it's inherited), and I think this is quite confusing as
- while a non-shared configuration could be a choice - there's a strong assumption and
expectation that these will point to a shared relational database.
I'd suggest to:
- add a highlighted reminder about this
- set the attribute explicitly in all example configurations
See also:
-
http://stackoverflow.com/questions/37949448/duplicate-record-errors-in-hi...
was:
The "shared" configuration attribute is defaulting to _false_ even for
database-based CacheStore instances as the attribute is defined in the parent of all
{{CacheStore}} types.
The attribute isn't very visible either, as it's not explicitly listed among the
available attributes (because it's inherited), and I think this is quite confusing as
- while a non-shared configuration could be a choice - there's a strong assumption and
expectation that these will point to a shared relational database.
See also:
-
http://stackoverflow.com/questions/37949448/duplicate-record-errors-in-hi...
Examples of JDBC CacheStore configuration should remind about the
shared attribute
----------------------------------------------------------------------------------
Key: ISPN-6798
URL:
https://issues.jboss.org/browse/ISPN-6798
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Documentation-Core
Reporter: Sanne Grinovero
Priority: Minor
Fix For: 9.0.0.Alpha4
The "shared" configuration attribute is defaulting to _false_ even for
database-based CacheStore instances as the attribute is defined in the parent of all
{{CacheStore}} types.
The attribute isn't very visible either, as it's not explicitly listed among the
available attributes (because it's inherited), and I think this is quite confusing as
- while a non-shared configuration could be a choice - there's a strong assumption and
expectation that these will point to a shared relational database.
I'd suggest to:
- add a highlighted reminder about this
- set the attribute explicitly in all example configurations
See also:
-
http://stackoverflow.com/questions/37949448/duplicate-record-errors-in-hi...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)