[JBoss JIRA] (ISPN-6845) A JDBC-based CacheLoader/CacheWriter that breaks down keys and values into multiple table columns
by Krzysztof Sobolewski (JIRA)
[ https://issues.jboss.org/browse/ISPN-6845?page=com.atlassian.jira.plugin.... ]
Krzysztof Sobolewski edited comment on ISPN-6845 at 7/11/16 6:33 AM:
---------------------------------------------------------------------
[This comment was made obsolete by closing of ISPN-6743]
was (Author: ksobolewski):
(But see also https://github.com/ksobolew/infinispan/tree/ISPN-6743, for ISPN-6743)
> A JDBC-based CacheLoader/CacheWriter that breaks down keys and values into multiple table columns
> -------------------------------------------------------------------------------------------------
>
> Key: ISPN-6845
> URL: https://issues.jboss.org/browse/ISPN-6845
> Project: Infinispan
> Issue Type: Feature Request
> Components: Loaders and Stores
> Affects Versions: 9.0.0.Alpha2
> Reporter: Krzysztof Sobolewski
>
> Even in the JBoss Cache days we (at my $DAYJOB) were not really happy with how the JDBC cache loader stores the data. Yes, marshalling the value into a BLOB is universal and portable, but nevertheless we created our own variant that increases visibility into the data by storing each attribute of the value in its own database table, in a human-readable format. It also very slightly improves performance, but that's not the primary goal. I think something like this would be useful in Infinispan.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-3835:
--------------------------------------
Fix Version/s: 9.0.0.Alpha4
(was: 9.0.0.Alpha3)
> Index Update command is processed before the registry listener is triggered
> ---------------------------------------------------------------------------
>
> Key: ISPN-3835
> URL: https://issues.jboss.org/browse/ISPN-3835
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 6.0.0.Final
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Priority: Critical
> Labels: 64QueryBlockers
> Fix For: 9.0.0.Alpha4
>
>
> When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet.
> Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event.
> This leads to index update commands to be lost (with a stacktrace logged)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months