[overlord-issues] [JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation
[
https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin....
]
Gary Brown commented on RTGOV-415:
----------------------------------
[~imckinle] Was wondering how you planned to handle the ES mapping for activities, when
the activity store is used? Will we just ship a preconfigured mapping file in the
ESActivityStore jar?
If so, then the problem will be using the same index for activities and other things (e.g.
response time, situations) - as from the code it looks like the index can only be
initialised once.
Solutions I can see:
1) Use separate indexes for each deployable unit - i.e. the activity store, and any EPNs
have their own index - so index per EPN, so one mapping file per EPN?
2) Some central location for all rtgov related mappings, and then act store and our EPNs
just rely on it already being initialised. Then the local EPN mapping file mechanism would
just be used by users who want to store their own info.
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)