[JBoss JIRA] (RTGOV-575) endex custom loading of index mappings per .epn deployment
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-575?page=com.atlassian.jira.plugin.... ]
Gary Brown resolved RTGOV-575.
------------------------------
Resolution: Done
[~imckinle] I've currently disabled the thread context class loader as we are dropping support for OSGi for now. However it would be useful to have a quickstart showing use of a custom Elasticsearch index, which I can then build an integration test around, to make sure this capability is supported in future. Would you be able to provide such a quickstart? (no urgent)
> endex custom loading of index mappings per .epn deployment
> -----------------------------------------------------------
>
> Key: RTGOV-575
> URL: https://issues.jboss.org/browse/RTGOV-575
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Components: Event Processor
> Reporter: ivan mckinley
> Assignee: Gary Brown
> Labels: elasticsearch
> Fix For: 2.1.0.Final
>
>
> Prior to the karaf integration it was possible to deploy a epn with a elasticsearch store configured for a separate index as rtogv.
> 1: developer would deploy a custom epn with a ElasticsearchKeyValueStore configured for a custom index and type.
> 2: the elastisearchclient class would look for a file name $index-mapping.json on the path
> The concept is developers can store business data they extracted from the activity events and store in ES for later analysis via kibana or what ever
> unfortunately the following line
> Thread.currentThread().setContextClassLoader(TransportClient.class.getClassLoader());
> in ElasticsearchClient that was added for the karaf intergration means that the classloader can not longer see any bundled $index-mappings.json file that accompany the deployed epns (.war)
> one solution would be to switch to the same mechanism used to to load ip.json or epn.json files
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (RTGOV-575) endex custom loading of index mappings per .epn deployment
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-575?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-575:
-----------------------------
Git Pull Request: https://github.com/Governance/rtgov/pull/255
> endex custom loading of index mappings per .epn deployment
> -----------------------------------------------------------
>
> Key: RTGOV-575
> URL: https://issues.jboss.org/browse/RTGOV-575
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Components: Event Processor
> Reporter: ivan mckinley
> Assignee: Gary Brown
> Labels: elasticsearch
> Fix For: 2.1.0.Final
>
>
> Prior to the karaf integration it was possible to deploy a epn with a elasticsearch store configured for a separate index as rtogv.
> 1: developer would deploy a custom epn with a ElasticsearchKeyValueStore configured for a custom index and type.
> 2: the elastisearchclient class would look for a file name $index-mapping.json on the path
> The concept is developers can store business data they extracted from the activity events and store in ES for later analysis via kibana or what ever
> unfortunately the following line
> Thread.currentThread().setContextClassLoader(TransportClient.class.getClassLoader());
> in ElasticsearchClient that was added for the karaf intergration means that the classloader can not longer see any bundled $index-mappings.json file that accompany the deployed epns (.war)
> one solution would be to switch to the same mechanism used to to load ip.json or epn.json files
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (RTGOV-634) Remove Fuse/Fabric support
by Gary Brown (JIRA)
Gary Brown created RTGOV-634:
--------------------------------
Summary: Remove Fuse/Fabric support
Key: RTGOV-634
URL: https://issues.jboss.org/browse/RTGOV-634
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Following a review of the current supported platforms, it has been decided to focus on Wildfly and EAP in the short/medium term and re-assess how best to support other platforms (such as Karaf/Fuse/Fabric) - possibly just providing a 'client side integration' only.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years