Hey Is there a reason the solids in `dagster gcp` that load

Question

Hey Is there a reason the solids in `dagster gcp` that load to BQ don t support specifying schema fields in the load job config Is it as simple as just adding the parameter here I see a TODO If so I can make a PR <https github com dagster io dagster blob a07fc28ae6878235aeada88e3584c6dea01f845b python modules libraries dagster gcp dagster gcp bigquery configs py L369|https github com dagster io dagster blob a07fc28ae6878235aeada88e3584c6dea01f845 n modules libraries dagster gcp dagster gcp bigquery configs py>

sashank · Answer

Looks like it just got stuck as TODO A PR would be great here cc < nate> who originally wrote this

Prratek Ramchandani · Answer

Cool I ll do that today Should I create an issue as well or is just a PR fine here

nate · Answer

just a PR is fine thanks for taking a look at this

Prratek Ramchandani · Answer

< nate> quick question would you recommend creating a custom type to check that the schema provided is valid or should I just accept a `List dict ` for the schema field and let the API call to BigQuery return an error if it s an invalid schema

Prratek Ramchandani · Answer

Going down the custom type route since we seem to do that for the other config options

Prratek Ramchandani · Answer

Could one of you take a look It s my first contribution to an open source project so I m not sure how to test that it works as expected <https github com dagster io dagster pull 3479>