Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CT-3306] [Bug] Spark Integration Failure Due in get_filtered_catalog() #8974

Closed
2 tasks done
peterallenwebb opened this issue Nov 1, 2023 · 0 comments · Fixed by #8975
Closed
2 tasks done

[CT-3306] [Bug] Spark Integration Failure Due in get_filtered_catalog() #8974

peterallenwebb opened this issue Nov 1, 2023 · 0 comments · Fixed by #8975
Labels
backport 1.7.latest bug Something isn't working

Comments

@peterallenwebb
Copy link
Contributor

peterallenwebb commented Nov 1, 2023 •
edited
Loading

Is this a new bug in dbt-core?

  • I believe this is a new bug in dbt-core
  • I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

The integration tests for dbt-spark (in CircleCI) are failing.

https://app.circleci.com/pipelines/github/dbt-labs/dbt-spark/3169/workflows/07148ef8-c908-43f9-9f61-e624918f2b97/jobs/15742

This is due to the fact that Spark does not use a database identifier.

Impact to Other Teams

Adapters

Backport?

Yes. Backport to 1.7.latest
@peterallenwebb peterallenwebb added bug Something isn't working triage labels Nov 1, 2023
@github-actions github-actions bot changed the title [Bug] Spark Integration Failure Due in get_filtered_catalog() [CT-3306] [Bug] Spark Integration Failure Due in get_filtered_catalog() Nov 1, 2023
@peterallenwebb peterallenwebb mentioned this issue Nov 1, 2023
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backport 1.7.latest bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make relation Filtering None-tolerant for maximal flexibility dbt-labs/dbt-core
1 participant
@peterallenwebb