[Feature Request]: JSON Input - when processing a field, it can only be a String
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### What would you like to happen?
You can configure a JSON Input transform to extract data from a field from the previous transform, especially if you need to decode a complex-structured payload or a REST response.
However, this field can only be a String: it you try to pass on a JSON object (as you're probably tempted to do, when linking more JSON Input transforms together), the transform fails for a ClassCastException.
### Issue Priority
Priority: 3
### Issue Component
Component: Transforms
Contributor guide
Research direction
Start by locating the JSON Input transform and the field-processing code that currently raises the ClassCastException for non-String values. Reproduce the issue with a JSON object passed from a previous transform, then verify that chained JSON Input transforms can process the object successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100