Distribute the hbase-site configuration to distributed jobs

Distribute the hbase-site configuration to distributed jobs

Running hbase mr ingest with the hbase-site on the classpath doesn't work without the zookeeper param because the configuration isn't sent to the mappers.

Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2250

Key: GEOMESA-2250
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Assignee: Austin Heyne
Reporter: Austin Heyne
Created: Wed, 4 Apr 2018 15:31:56 -0400
Updated: Fri, 17 Apr 2020 14:17:29 -0400

Comments:

557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Mon, 9 Jul 2018 12:38:05 -0400):

Partial work here: https://github.com/locationtech/geomesa/pull/1927

557058:48912df4-0004-4f90-9915-db26684ec006 (Thu, 16 Apr 2020 17:57:05 -0400):

Austin Heyne Emilio Lahr-Vivaz is this handled?

557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Fri, 17 Apr 2020 09:09:13 -0400):

I think the accepted solution is to add the hbase-site.xml into the geomesa datastore jar. That's the approach we give in the docs.

557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Fri, 17 Apr 2020 09:09:42 -0400):

If we didn't have to do that it would be nice, but might be kind of complicated.

557058:3f10fbb6-8894-45e8-828a-0f6aa4281f1d (Fri, 17 Apr 2020 11:24:30 -0400):

Adding it works well enough, I’m not sure how we’d get around it cleanly.

557058:48912df4-0004-4f90-9915-db26684ec006 (Fri, 17 Apr 2020 14:17:29 -0400):

How do the MR jobs get kicked off? I wonder if we have an obvious place where we could hook in and add the hbase-site.xml ‘late’…

Start with the hbase MR ingest entry point and the partial work in PR 1927; no source file or test is named in the issue. Determine where mapper configuration is assembled, then verify that a classpath hbase-site.xml reaches distributed jobs without requiring a ZooKeeper parameter.