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.

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

Error message on expect_column_values_to_be_unique Expectation on Teradata #3842

Closed
dsehnbru opened this issue Dec 13, 2021 · 2 comments
Closed
Labels
community feature:new_backend help wanted Issues we'd love to see community contributions for. Join #contributors-contributing in our Slack!

Comments

@dsehnbru
Copy link

Describe the bug
Running validation on Teradata column against a expect_column_values_to_be_unique - Expectation resulting in error

To Reproduce

  1. Create expect_column_values_to_be_unique - Expectation on any column of Teradata database
  2. Run Expecation against Teradata datasource
    Expected behavior
    As this is obviously on of the most pivotal expectations, it should work against Teradata databases as well.

Environment (please complete the following information):

  • Operating System: Windows 10
  • Great Expectations Version: 0.13.44

Additional context
The expectation created in 1) works when run against a Sqlite database, so there has got to be a Teradata specific problem.

expect_column_values_to_be_unique error

@cdkini cdkini added community devrel This item is being addressed by the Developer Relations Team labels Dec 13, 2021
@cdkini
Copy link
Contributor

cdkini commented Dec 13, 2021

Hey @dsehnbru thanks so much for opening this up! Our support for Teradata is in the experimental phase so there may be some issues that we're not actively able to prioritize.

@imamolp recently did some work so tagging for visibility.

@cdkini cdkini added help wanted Issues we'd love to see community contributions for. Join #contributors-contributing in our Slack! and removed devrel This item is being addressed by the Developer Relations Team labels Dec 13, 2021
@github-actions github-actions bot added the stale Stale issues and PRs label Aug 5, 2022
@talagluck talagluck added feature:new_backend and removed stale Stale issues and PRs labels Aug 5, 2022
@great-expectations great-expectations deleted a comment from github-actions bot Aug 5, 2022
@kyleaton
Copy link
Member

Hi @dsehnbru, Following up here... We are closing this issue in favor of a GitHub Discussion to provide more visibility to those that would be interested in contributing to adding more support to Teradata. The conversation can be continued here: #5889

Let us know if you are interested in contributing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community feature:new_backend help wanted Issues we'd love to see community contributions for. Join #contributors-contributing in our Slack!
Projects
None yet
Development

No branches or pull requests

4 participants