spring-projects / spring-projects/spring-ai
Can ETL Pipeline support more ways to read the file content
Open
Nobody has claimed this yet.
ETL
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.9k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 6
Description
JSON
Text
Markdown
PDF Page
PDF Paragraph
Tika (DOCX, PPTX, HTML…)
Can ETL Pipeline support more ways to read the file content, such as byte [], http url, or the file upload MultipartFile can directly read the file text content?
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 with the ETL Pipeline documentation linked in the issue and trace the existing JSON, Text, Markdown, PDF, and Tika input paths. Determine how byte arrays, HTTP URLs, and MultipartFile uploads should be represented and handled, then verify that each supported input can produce readable file content consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100