metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mattf-horton <...@git.apache.org>
Subject [GitHub] incubator-metron pull request #470: METRON-752 Fix documentation typos and M...
Date Sat, 04 Mar 2017 02:07:34 GMT
Github user mattf-horton commented on a diff in the pull request:

    https://github.com/apache/incubator-metron/pull/470#discussion_r104275196
  
    --- Diff: metron-analytics/metron-profiler/README.md ---
    @@ -204,21 +204,21 @@ The Profiler runs as an independent Storm topology.  The configuration
for the P
     The values can be changed on disk and then the Profiler topology must be restarted.
     
     
    -| Setting   | Description   |
    -|---        |---            |
    -| profiler.workers | The number of worker processes to create for the topology.   |
    -| profiler.executors | The number of executors to spawn per component.  |
    -| profiler.input.topic | The name of the Kafka topic from which to consume data.  |
    -| profiler.output.topic | The name of the Kafka topic to which profile data is written.
 Only used with profiles that use the [`triage` result field](#result).  |
    -| profiler.period.duration | The duration of each profile period.  This value should
be defined along with `profiler.period.duration.units`.  |
    -| profiler.period.duration.units | The units used to specify the `profiler.period.duration`.
|
    -| profiler.ttl | If a message has not been applied to a Profile in this period of time,
the Profile will be forgotten and its resources will be cleaned up. This value should be defined
along with `profiler.ttl.units`. |
    -| profiler.ttl.units | The units used to specify the `profiler.ttl`. |
    -| profiler.hbase.salt.divisor  |  A salt is prepended to the row key to help prevent
hotspotting.  This constant is used to generate the salt.  Ideally, this constant should be
roughly equal to the number of nodes in the Hbase cluster.  |
    -| profiler.hbase.table | The name of the HBase table that profiles are written to.  |
    -| profiler.hbase.column.family | The column family used to store profiles. |
    -| profiler.hbase.batch | The number of puts that are written in a single batch.  |
    -| profiler.hbase.flush.interval.seconds | The maximum number of seconds between batch
writes to HBase. |
    +| Setting                               | Description
    +|---                                    |---
    +| profiler.workers                      | The number of worker processes to create for
the topology.
    +| profiler.executors                    | The number of executors to spawn per component.
    +| profiler.input.topic                  | The name of the Kafka topic from which to consume
data.
    +| profiler.output.topic                 | The name of the Kafka topic to which profile
data is written.  Only used with profiles that use the [`triage` result field](#result).
    +| profiler.period.duration              | The duration of each profile period.  This
value should be defined along with `profiler.period.duration.units`.
    +| profiler.period.duration.units        | The units used to specify the `profiler.period.duration`.
    +| profiler.ttl                          | If a message has not been applied to a Profile
in this period of time, the Profile will be forgotten and its resources will be cleaned up.
This value should be defined along with `profiler.ttl.units`.
    +| profiler.ttl.units                    | The units used to specify the `profiler.ttl`.
    +| profiler.hbase.salt.divisor           | A salt is prepended to the row key to help
prevent hotspotting.  This constant is used to generate the salt.  Ideally, this constant
should be roughly equal to the number of nodes in the Hbase cluster.
    +| profiler.hbase.table                  | The name of the HBase table that profiles are
written to.
    +| profiler.hbase.column.family          | The column family used to store profiles.
    +| profiler.hbase.batch                  | The number of puts that are written in a single
batch.
    +| profiler.hbase.flush.interval.seconds | The maximum number of seconds between batch
writes to HBase.
    --- End diff --
    
    Okay


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message