[JBoss JIRA] (RTGOV-532) Path for Elasticsearch node data is relative
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-532?page=com.atlassian.jira.plugin.... ]
Gary Brown updated RTGOV-532:
-----------------------------
Fix Version/s: 2.0.0.Final
> Path for Elasticsearch node data is relative
> --------------------------------------------
>
> Key: RTGOV-532
> URL: https://issues.jboss.org/browse/RTGOV-532
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Final
> Reporter: Jiri Pechanec
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> When RTGov is installed into EAP it sets path.data config property to "../elasticsearch". This is incorrect as the value
> - should not be relative as it depends on the directory from which the server is started
> - should use ${jboss.server.data.dir}/elasticsearch as it a place where all data files for EAP are stored
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[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:
-----------------------------
Affects Version/s: (was: 2.0.0.Final)
> 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.0.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.1#6329)
10 years, 3 months
[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:
-----------------------------
Fix Version/s: 2.0.0.Final
> 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.0.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.1#6329)
10 years, 3 months
[JBoss JIRA] (RTGOV-575) endex custom loading of index mappings per .epn deployment
by ivan mckinley (JIRA)
ivan mckinley created RTGOV-575:
-----------------------------------
Summary: 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
Affects Versions: 2.0.0.Final
Reporter: ivan mckinley
Assignee: Gary Brown
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.1#6329)
10 years, 3 months