[
https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin....
]
ivan mckinley commented on RTGOV-415:
-------------------------------------
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.
this is how i imagined it. The ootb epn for activities, situations
and responses would be initialize the core rtgov index. the EPNs and ACT store reference
these indexes. it does not make sense to have a separate index for the act store and the
activity epn. this would be duplication of data.(your 1st point)
The current
central location is the EPN at the moment, so it would be initialized the first time the
epn is activated. or should the act store be referenced first the actstore would then
initialize it. (first come first serve). Currently it doesn't matter when it gets
initialized but it would be clean if we had a central location for this.
Local epn mappings would then define their own mapping files(rtgov-mapping,
<myindex>-mapping.json). the mapping file can either define own index or append the
rtgov index (this is how it works at the moment).
I seriously need to document this stuff soon :)
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)