locationtech / locationtech/geomesa
Default transforms in Converters
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.5k
- Forks
- 446
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Default transforms in Converters
When writing something like a fixed width converter you end up doing a trim on every string field. We should be able to define a few defaults or something like that? Perhaps something like:
default-transforms{ {name = "trim", transform = "trim($0)" data-type = "string"} { name = "trydouble" transform = "try($0::double, null), "type = "double" } }
Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-2403
Key: GEOMESA-2403
Type: Story
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: Andrew Hulbert
Created: Tue, 18 Sep 2018 10:22:07 -0400
Updated: Wed, 13 Mar 2019 10:03:05 -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 Converters implementation and the fixed-width converter entry point. Clarify the configuration syntax, supported data types, and transform ordering, then verify that configured defaults are applied to matching fields without requiring repeated per-field transforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100