GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/655
Profiler Should be Less Dramatic When Missing Configuration
When the Profiler topology is running, but no Profiler definition is found
in Zookeeper, the Profiler will now just calmly log a warning. Previously the
Profiler would throw a rather nasty looking exception.
I also refactored the logic for Profile `expires` handling. Previously,
this code was not all in one place (`ProfileHBaseMapper` + `ProfileConfig`),
which made it less than clear what units the code base supported for `expires`.
I refactored the code so that it is all in one place (`ProfileHBaseMapper`)
and very clear what is happening to avoid confusion.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/metron METRON-1043
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/655.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #655
----
commit 8d77e4167aeefc1a769c1c266ff8e883e9a06ce8
Author: Nick Allen <n...@nickallen.org>
Date: 2017-07-13T19:45:16Z
Profiler Should be Less Dramatic When Missing Configuration
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
