[Feature][Core] Support define all nested types
- Dominant language
- Java
- Stars
- 9.7k
- Forks
- 2.4k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 203
Description
### Search before asking
- [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement.
### Description
Currently, our API design has limited support for nested data structures, and we need to support the definition and processing of any nested data types.
Please refer https://github.com/apache/seatunnel/blob/45609ef1dfd88d4844a90eec0d0984b1797e44d4/seatunnel-api/src/main/java/org/apache/seatunnel/api/table/type/ArrayType.java#L22
and
https://github.com/apache/seatunnel/blob/45609ef1dfd88d4844a90eec0d0984b1797e44d4/seatunnel-api/src/main/java/org/apache/seatunnel/api/table/type/MapType.java#L30
### Usage Scenario
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading seatunnel-api/src/main/java/org/apache/seatunnel/api/table/type/ArrayType.java and MapType.java at the referenced lines. Trace how these types currently define and process nested structures, then determine the API changes needed for arbitrary nested data types. Done means nested data types can be defined and processed beyond the current limitations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100