Unknown datatypes INT and Varchar when creating expectation suites or checkpoints accessing Teradata tables

[dsehnbru]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Create a datasource accessing a Teradata DB
2. Create an expectation suite accessing a table of the Teradata DB created in step 1 bases on the profiler via the CLI. (the same happens when you create expectations for int and varchar columns manually and run a checkpoint against those and a teradata table)
3. For columns with types int and varchar the output gives the message "No recognized sqlalchemy types in type_list for current dialect".

Expected behavior Given that the access to a teradata db via sqlalchemy works without any problemes based on the teradatasqlalchemy module, it should be possible to create expecations for all columns regardless of the data type.

Environment (please complete the following information):

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

[dsehnbru]

Describe the bug:

when creating expectation suites or checkpoints accessing Teradata tables GE will not recognize Int and Varchar data types

[austiezr]

Hey @dsehnbru! Thank you for raising this; we will review internally.

[austiezr]

Hey @dsehnbru! Thank you again for surfacing this issue. While we do have eyes on this, we are unfortunately unable to prioritize work here as GE for Teradata is still experimental and not fully supported. We would welcome a contribution in this area (@imamolp you may be interested in seeing this!), and we would be happy to offer guidance and review in support of any community efforts here.

[github-actions[bot]]

Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity.

It will be closed if no further activity occurs. Thank you for your contributions 🙇