locationtech / locationtech/geomesa
Docs - Add note about adding *-conf.xml files to Spark conf directory to help with Kerberos configuration
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Docs - Add note about adding *-conf.xml files to Spark conf directory to help with Kerberos configuration
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2901
Key: GEOMESA-2901
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: James Hughes
Created: Thu, 27 Aug 2020 09:01:08 -0400
Updated: Wed, 28 Dec 2022 16:30:47 -0500
Affects Version(s): 3.0.0
Comments:
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Thu, 27 Aug 2020 09:08:06 -0400):
related, we should add a check for missing geomesa principal keys in the conf so that the error message isn't an NPE:
java.lang.NullPointerException
at org.locationtech.geomesa.hbase.data.HBaseConnectionPool$.sameName(HBaseConnectionPool.scala:189)
at org.locationtech.geomesa.hbase.data.HBaseConnectionPool$.configureSecurity(HBaseConnectionPool.scala:159)
557058:48912df4-0004-4f90-9915-db26684ec006 (Mon, 8 Mar 2021 16:23:10 -0500):
Emilio Lahr-Vivaz did your recent Kerberos work address this by chance?
557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Mon, 8 Mar 2021 16:24:40 -0500):
not the docs work, it resolved the comment on the NPE.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no documentation file or test. Start by locating the Spark configuration documentation and its guidance for the conf directory, then add the note about *-conf.xml files and Kerberos configuration. Done means the relevant documentation clearly explains where these files belong and how they support Kerberos setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spark
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100