[overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation
[
https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin....
]
ivan mckinley commented on RTGOV-415:
-------------------------------------
Gary,
I'm testing a different type ES mappings.
Was - ActivityUnit = flat document with ActivityType as nested objects
Now - ActivityUnit = has many ActivityType child type documents.
The nested object approach was difficult to achieve the functionality outlined by the
ActivityStore interface. This results in kibana would have work with two documents . the
activityUnit and the activityType. Would be interested in your opinion on this as this
would impact how kibana displays the AU nd AT data
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 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