[
http://jira.amdatu.org/jira/browse/AMDATU-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATU-242.
-------------------------------------------
Resolution: Fixed
The way CPM and CFA services are registered have been refactored. A separate
thread keeps inspecting the cassandra db (there is no event mechanism yet in
cassandra) for any changes in keyspaces or columnfamilies. If so, cf's are
added for keyspace-global CF providers and CPM and CFA services are
registered/unregistered when necessary.
> No ColumnFamilyAvailable services are started for ColumnFamily's in new
> keyspaces when the CF provider defined keyspace null
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMDATU-242
> URL: http://jira.amdatu.org/jira/browse/AMDATU-242
> Project: Amdatu
> Issue Type: Bug
> Components: Amdatu Cassandra
> Affects Versions: 0.1.0
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.1.0
>
>
> In a ColumnFamilyProvider you can define in what keyspace(s) your
> ColumnFamily should become available. Define a keyspace that equals null
> means that the ColumnFamily will be available in all keyspaces. An example of
> such a provider is the FriendColumnFamilyProvider.
> However, when I add a keyspace using the cassandra daemon service, no
> ColumnFamilyAvailable services are started for those column families. And
> this the "Friend" CF will only be available in the keyspaces that are already
> present at the time this service was started.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
