locationtech / locationtech/geomesa
Merged Store - Support filters on a per-layer basis
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Merged Store - Support filters on a per-layer basis
currently you can specify filters with geomesa.merged.store.filter but if you have different layers, the filter might need to be different. could add something like geomesa.merged.store..filter so that you can specify them per layer
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-3585
Key: GEOMESA-3585
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Emilio Lahr-Vivaz
Created: Thu, 21 May 2026 16:00:35 -0400
Updated: Thu, 21 May 2026 16:00:36 -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
Start by locating the Merged Store implementation and the existing handling for geomesa.merged.store.filter. Trace how filters are applied when multiple layers are configured, then determine how a per-layer filter setting should be recognized. Done means different layers can use different filters while the existing shared filter behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100