Better way to send resource fields information
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- Python
- Stars
- 34
- Forks
- 8
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 1
Description
At this time they are sent via array in the DAG params (e.g. "schema_fields_array": "['field1', 'field2']") and everything is treated as text type.
What are good alternatives?
Questions:
- Modify this array to become a dictionary of names and types. What is a good way to pass it? I believe doing it in plain text can be tedious. What about adding another node on the DAG to fetch the header of the CSV and automatically create a dictionary of fields, hard-coding everything to text?
- Should we start considering different types?
- If yes, define how to treat errors
Contributor guide
No contributing guide indexed for this repository
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 reviewing how DAG params currently carry schema_fields_array and how the CSV header is available to the pipeline. The issue does not name files or tests; completion would require an agreed field-schema format, type-handling behavior, and error policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100