Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/236#discussion_r76795784
--- Diff:
metron-analytics/metron-profiler/src/main/flux/profiler/remote.yaml ---
@@ -25,11 +25,28 @@ components:
- id: "defaultExecutor"
className:
"org.apache.metron.profiler.stellar.DefaultStellarExecutor"
- - id: "hbaseMapper"
- className: "org.apache.metron.profiler.bolt.ProfileHBaseMapper"
+ - id: "rowKeyBuilder"
+ className: "org.apache.metron.profiler.hbase.SaltyRowKeyBuilder"
properties:
- name: "saltDivisor"
value: ${profiler.hbase.salt.divisor}
+ - name: "periodsPerHour"
+ value: ${profiler.periods.per.hour}
+
+ - id: "columnBuilder"
+ className:
"org.apache.metron.profiler.hbase.ValueOnlyColumnBuilder"
+ constructorArgs:
+ - "${profiler.hbase.column.family}"
+
+ - id: "hbaseMapper"
+ className: "org.apache.metron.profiler.bolt.ProfileHBaseMapper"
+ properties:
+ - name: "rowKeyBuilder"
+ ref: "rowKeyBuilder"
+ - name: "columnBuilder"
+ ref: "columnBuilder"
+ - name: "executor"
+ ref: "defaultExecutor"
--- End diff --
I have multiple components that each need their own `StellarExecutor`. Does
Flux treat the `defaultExecutor` reference as a singleton and so every
reference to `defaultExecutor` is pointing to the same object? Or is treated
more like a Spring Bean's 'Prototype' scope? I would think it would have to be
treated as a prototype, but I'd like to make sure.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
