Investigate: does BigQueryIO honor write disposition in all cases?
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
I am not certain that we have proper testing of the spread of write dispositions, and I do not see enough (any?) testing of the non-default values. We should verify that these are properly used, even for large multi-table copies, etc.
Imported from Jira [BEAM-1181](https://issues.apache.org/jira/browse/BEAM-1181). Original Jira may contain additional context.
Reported by: dhalperi.
Contributor guide
Research direction
Start by locating BigQueryIO and its existing write-disposition tests. Check whether non-default dispositions are covered, including large multi-table copies, and verify that each relevant case behaves as expected. The work is done when the disposition behavior is tested across the identified cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, java
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100