Skip to content

ValueError: Please install the 'db-dtypes' package to use this function. #2537

Closed

Description

@chhabrakadabra

Expected Behavior

If I install feast with the [gcp] extra, I should be able to use BigQueryRetrievalJob.to_bigquery() without problems.

Current Behavior

When feast is installed with the [gcp] extra, it installs google-cloud-bigquery as per this line. It does not use the pandas extra, which means nothing triggers the installation of the db-dtypes package.

When bigquery.py uses to_dataframe() on the result of a BQ query as done here, it triggers a verification of imports available, which causes the exception here.

Steps to reproduce

Install feast[gcp] and use BigQueryRetrievalJob.to_bigquery().

Specifications

  • Version: feast[gcp]==0.16.1
  • Platform: OSX
  • Subsystem: Not sure what this is referring to

Possible Solution

Use google-cloud-bigquery[pandas] for the [gcp] extra.

Activity

  1. felixwang9817 commented on Apr 15, 2022

    @felixwang9817
    Collaborator

    Hey @chhabrakadabra, thanks for reporting this issue. What version of google-cloud-bigquery do you have? I suspect the issue is that google-cloud-bigquery recently released v3.0.0 which had the db-dtypes breaking change. See this release and this migration guide for more details. Can you try reverting to google-cloud-bigquery<3.0.0 and seeing if this error still persists? I'm on 2.34.1 and it works fine for me.

    I'll keep this issue open to track an upgrade to v3.0.0.

  2. felixwang9817 commented on Apr 15, 2022

    @felixwang9817
    Collaborator

    I believe #2554 should have resolved this issue, so I'll close it now. If for some reason the bug persists, please feel to reopen it @chhabrakadabra!

  3. michaelzolo commented on May 30, 2022

    @michaelzolo

    For me this bug still persists. I'm using google-cloud-bigquery 3.0.1

  4. removed their assignment
    on May 31, 2022
  5. jerinscaria commented on Jun 7, 2022

    @jerinscaria

    Issue persists google-cloud-bigquery version 3.1.0

  6. reopened this on Jun 7, 2022
  7. felixwang9817 commented on Jun 7, 2022

    @felixwang9817
    Collaborator

    hey @michaelzolo and @jerinscaria, we still haven't upgraded to support bigquery >=3.0.0, so I would recommend using bigquery <3 for now

  8. added a commit that references this issue on Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions