[overlord-issues] [JBoss JIRA] (RTGOV-575) endex custom loading of index mappings per .epn deployment

Gary Brown (JIRA) issues at jboss.org
Fri Dec 12 06:11:29 EST 2014


     [ https://issues.jboss.org/browse/RTGOV-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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)


More information about the overlord-issues mailing list