Skip to content

Direct specification of NUMERIC columns in bigquery.SchemaField #2053

Open
@shering243

Description

@shering243

Thanks for stopping by to let us know something could be better!

PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.

Is your feature request related to a problem? Please describe.

Direct specification of NUMERIC columns in bigquery.SchemaField. This is available for INT, FLOAT, STRING etc but only NUMERIC is missing. This leads to the need of client side conversion of datatype in case the column data type in bigquery is NUMERIC. An optimum solution for the customer would be that the bigquery client library supports NUMERIC too just like the other datatypes

Describe the solution you'd like

Interested in the default option where we can specific NUMERIC datatype in the schemaField in the client library itself just like it can be done with other data types.

Describe alternatives you've considered

Manual conversion of datatype before upload is performed to avoid datatype mismatch error.

Additional context

NA

Metadata

Metadata

Assignees

Labels

api: bigqueryIssues related to the googleapis/python-bigquery API.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy