Github user nickwallen commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/421#discussion_r97800043
--- Diff: metron-platform/metron-data-management/README.md ---
@@ -250,3 +250,18 @@ The parameters for the utility are as follows:
| -l | --log4j | No | The log4j properties
file to load
|
| -n | --enrichment_config | No | The JSON document
describing the enrichments to configure. Unlike other loaders, this is run
first if specified.
|
+### GeoLite2 Loader
+
+The shell script `$METRON_HOME/bin/geo_enrichment_load.sh` will retrieve
MaxMind GeoLite2 data and load data into HDFS, and update the configuration.
+
+THIS SCRIPT WILL NOT UPDATE AMBARI'S GLOBAL.JSON, JUST THE ZK CONFIGS.
CHANGES WILL GO INTO EFFECT, BUT WILL NOT PERSIST PAST AN AMBARI RESTART UNTIL
UPDATED THERE.
+
--- End diff --
This seems like something that could cause a really annoying problem for a
user. Is there no simple action we can take in this PR to stop Ambari from
clobbering things?
Obviously, deploying/updating the geo database in an Ambari "service
action" would be ideal. Would be nice to have one way to do it that does not
break on restart.
Or maybe we need to accept this for now and once we have Ansible
deployments using the MPack, we can implement an Ambari "service action" for
this?
---
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.
---