What would you like to happen?
BigQueryIO supports a CreateDisposition (NEVER, CREATE_IF_NEEDED) and any file-based IO requires no additional create step. Our (Spotify's) internal users are comfortable with and indeed expect this behavior.
We have added iceberg support to in scio spotify/scio#5494 but for example in the integration test we must issue createTable requests before the test is run:
https://github.com/spotify/scio/pull/5494/files#diff-5116ce37fed90178a3919b87a160d5795f51beb644117d63340ba55ffbf45b46R66-R71
I think it is reasonable to expect the catalog/namespace to exist but table creation could be automatically supported in the IO
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components
What would you like to happen?
BigQueryIO supports a
CreateDisposition(NEVER, CREATE_IF_NEEDED) and any file-based IO requires no additional create step. Our (Spotify's) internal users are comfortable with and indeed expect this behavior.We have added iceberg support to in scio spotify/scio#5494 but for example in the integration test we must issue createTable requests before the test is run:
https://github.com/spotify/scio/pull/5494/files#diff-5116ce37fed90178a3919b87a160d5795f51beb644117d63340ba55ffbf45b46R66-R71
I think it is reasonable to expect the catalog/namespace to exist but table creation could be automatically supported in the IO
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components