Hi,\nI've been trying to get the teradata driver working as per the documentation, had a lot of issues. I've been working with Teradata and python for a long time and I know that the driver thats used in Superset is pretty old and there is a much newer teradata driver for python called teradatasql. I was able to add this in to superset as a database engine, and eventually run a query in sql lab.\nThe problems that I'm seeing are, on the add data source, I can do a test connection and get a success or bad password back with no problem, but adding the datasource runs forever and eventually crashes out.\nI gave up and eventually created it on the Superset CLI, which worked a treat.\nThen in the SQL Lab I wanted to test this out, I ran a couple of small queries, worked fine but eventually it stopped returning anything. Even queries that should run in a second and return just 1 row weren't returning.\nAnyway, I think both issues are due to the number of schemas on our database, which is over 2700. I noticed the SQL lab is trying to return them all and I'm guessing when we create the connection it does the same thing. Anyone know if I can turn this off or limiting how many schemas are returned when defining the new engine.\nI think teradata using the newer teradatasql and teradatasqlalchemy python libraries would be easy to add, but I'm just struggling to test it.