[
https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin....
]
ivan mckinley commented on RTGOV-415:
-------------------------------------
Great, :) I wanted to actually align with you regarding this as I found it kinda
redundant to hide the ES query dsl behind the a query method.
- Error prone.
- Would require excessive validation on the query been passed to store. (ensuring only
Actvity type is been queried)
- serialization and deserialization overhead ESdocument ->ActivityType->Json
-Only the Rest interface uses it
Why is it been deprecated?
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