locationtech / locationtech/geomesa
Auths for adding indexes
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Auths for adding indexes
A few things...
- Ensure Auths are set on input formats for jobs that create new types of indexes or add attributes to indexes. They need them to read the data
- Ensure that auths are copied properly from the original records to new indexes/attribute indexes
- Create some sort of test for these. Look into a mrunit test with embedded accumulo? but make it an IT.
Note that 1.2 had a previous commit for part of this:
https://github.com/locationtech/geomesa/commit/146df3e8d12069511ddd3ef7522acf1e8b97fa60
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1788
Key: GEOMESA-1788
Type: Story
Priority: Major
Status: To Do
Resolution: Unresolved
Assignee: Andrew Hulbert
Reporter: Andrew Hulbert
Created: Mon, 24 Apr 2017 13:30:43 -0400
Updated: Mon, 24 Apr 2017 13:30:43 -0400
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
Review commit 146df3e8d12069511ddd3ef7522acf1e8b97fa60, then trace the input formats and jobs that create indexes or add index attributes. Add integration coverage using the proposed embedded Accumulo/MRUnit approach; done means auths are available for reads and are copied from original records to new indexes and attribute indexes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- authorization, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100