[
https://issues.apache.org/jira/browse/METRON-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838189#comment-15838189
]
ASF GitHub Bot commented on METRON-283:
---------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/421#discussion_r97832200
--- Diff: metron-deployment/packaging/docker/rpm-docker/SPECS/metron.spec
---
@@ -317,6 +316,8 @@ This package installs the Metron Profiler %{metron_home}
#
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
%changelog
+* Thu Jan 19 2017 Justin Leet <[email protected]> - 0.3.0
--- End diff --
It is true that apache recommends strongly (or maybe outright forbids)
things like author tags in source code (see
[here](https://mail-archives.apache.org/mod_mbox/www-community/200306.mbox/%[email protected]%3E)
for a discussion, the reasoning was mostly around the author tags not being
accurately representative.
For this situation, however, this is a changelog, so it doesn't have the
problem of accurate representation that author tags do. That being said, it is
redundant information because such information is stored in git.
I'd recommend doing a dev list discussion with a subject that starts with
[MENTORS] on this to see what the ASF wants.
> Migrate Geo Enrichment outside of MySQL
> ---------------------------------------
>
> Key: METRON-283
> URL: https://issues.apache.org/jira/browse/METRON-283
> Project: Metron
> Issue Type: Improvement
> Reporter: James Sirota
> Assignee: Justin Leet
> Priority: Minor
>
> We need to migrate our enrichment SQL store from MySQL to Phoenix or some
> other SQL on Hbase library. Or alternatively come up with a way to do this
> without using SQL. This way we don't have a dependency on MySQL and there is
> one less thing that we need to install on our platform
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
