[
https://issues.apache.org/jira/browse/METRON-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253804#comment-16253804
]
ASF GitHub Bot commented on METRON-1302:
----------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/831#discussion_r151189543
--- Diff:
metron-deployment/packaging/ambari/metron-mpack/src/main/resources/common-services/METRON/CURRENT/configuration/metron-indexing-env.xml
---
@@ -73,18 +98,31 @@
<display-name>Indexing Update Column Family</display-name>
</property>
<property>
- <name>indexing_workers</name>
+ <name>ra_indexing_workers</name>
+ <description>Number of Indexing Topology Workers</description>
--- End diff --
That sounds good. Which one would you guys prefer:
* display names in the mpack of "Elasticsearch" and "HDFS"
* variable prefixes of `es` and `hdfs`
I think I'd prefer the first as I really have been trying to set us up to a
world where we can make things pluggable (this is the first baby step).
> Split up Indexing Topology into batch and random access sections
> ----------------------------------------------------------------
>
> Key: METRON-1302
> URL: https://issues.apache.org/jira/browse/METRON-1302
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
>
> Currently we have the indexing topology handle writing to both random access
> indices (e.g. elasticsearch) as well as batch write indices (e.g. hdfs). We
> should split these up and configure them separately.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
