[overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation
ivan mckinley (JIRA)
issues at jboss.org
Fri May 2 07:03:57 EDT 2014
[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965071#comment-12965071 ]
ivan mckinley commented on RTGOV-415:
-------------------------------------
If (3) is possible - then the ESActivityStore could have a mapping file for index rtgov and type activity. The datastore EPN could then have then mapping file for index rtgov and types 'responsetime' and 'situation'.
> it does this already. for instance. If i define a store with index= rtgov , type = actvity and there a multiple type mappings in the rtgov-mapping.json file. it will only initialize the mapping for activity. this functionality is available in the current src.
Note: I'm re-evaluting and testing another approach. for instance, what happens when your activity is derived of more complex mappings, like children etc. needs to be able to initializes the child mappings.
> ElasticSearch Activity Store implementation
> -------------------------------------------
>
> Key: RTGOV-415
> URL: https://issues.jboss.org/browse/RTGOV-415
> Project: RTGov (Run Time Governance)
> Issue Type: Sub-task
> Reporter: Gary Brown
> Assignee: ivan mckinley
> Fix For: 2.0.0.Final
>
>
> Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative.
> If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times).
> ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional.
> The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
More information about the overlord-issues
mailing list