load_csv_to_postgres_via_copy considers _id and _full_text
Open
Nobody has claimed this yet.
bug
frozen
- Dominant language
- Python
- Stars
- 34
- Forks
- 8
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 1
Description
The task load_csv_to_postgres_via_copy considers these two fields when trying to fit the CSV into the table. Find a solution that allows a clean CSV load
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 locating the load_csv_to_postgres_via_copy task and trace how it determines which CSV fields fit the PostgreSQL table. Verify why _id and _full_text are considered, then confirm that a CSV containing these fields can be loaded cleanly without inappropriate field handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100