locationtech / locationtech/geomesa
FSDS - improve metadata stats
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
FSDS - improve metadata stats
Keep more than just spatial bounds and count in the metadata for each file. Allow for configurable flags on attributes to include?
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2961
Key: GEOMESA-2961
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Thu, 10 Dec 2020 07:18:43 -0500
Updated: Thu, 10 Dec 2020 08:59:01 -0500
Comments:
557058:48912df4-0004-4f90-9915-db26684ec006 (Thu, 10 Dec 2020 08:59:01 -0500):
Keeping the dictionaries for certain columns could allow for skipping files when doing an entity lookup.
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 files, tests, or entry points. Start by locating where per-file metadata currently records spatial bounds and counts, then determine how configurable attribute flags and column dictionaries should be defined; done should mean the requested metadata is retained and can support file skipping without breaking existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100