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

Logical Tests Failing #916

Closed
neosujoy opened this issue Jan 21, 2022 · 5 comments
Closed

Logical Tests Failing #916

neosujoy opened this issue Jan 21, 2022 · 5 comments

Comments

@neosujoy
Copy link

Name: Sujoy Neogi
Company: Innominds

I am working on a Tableau connector, i see all logical and lod tests are failing, some of them were previously passing but now i see all are failing with "TableauException: Tableau cannot evaluate the query that results from this calculation."

For LOD tests i see "DataSourceException: No such function $IN_SET$ that takes arguments of type (int, datetime, datetime, datetime)."

Based on the forum posts it seems to be dialect issue, based on the postgres dialect if i have all the functions but not able to figure out, any other way to find the missing functions in dialect which i suppose is the reason behind this error

@neosujoy
Copy link
Author

I upgraded to the latest tdvt, and defined the unsupported columns types in tds files. Now i see some test cases are fixed but i still see lot of errors like

DataSourceException: Abstract query SELECT [date0] is not defined.
DataSourceException: Abstract query SELECT [Order Date] is not defined.

Is there a way to fix these issues

@rosswbrown
Copy link
Contributor

Hi. The two most common reasons errors like this may occur are an incomplete dialect or an incorrectly loaded TestV1 data set (step 3).

Based on the error messages above I would suspect the dialect is the best starting point. All of those errors look related to Date or DateTime type definition. In addition to the Postgres sample we also have an additional folder of supplemental dialect examples here. It includes the default, a full <function-map> list and a complete example of a Hive-based data source dialect.

For a more detailed investigation we generally require these artifacts. Since this is a TDVT test the product logs and screenshots can be omitted. Thanks.

@neosujoy
Copy link
Author

neosujoy commented Mar 4, 2022

Thanks for the explanation, what i understand is the errors are coming because i have defined virtual/derived columns in the tds files, so the Staples Data, Calcs Data tests are passing as they are using the formulae to get the column values, but several tests like LOD are still sending select queries with the virtual column name (for bool and datetime types, which are not supported by us), as these are not really present and only defined in tds file, the Abstract Query COLUMN is not defined error is coming, if TDVT is able to generate query for the Staples Data test case correctly i know nothing wrong with my column definition, this looks more of some tests cannot be run as data for these virtual column cannot be directly extracted.

@rosswbrown
Copy link
Contributor

I'd recommend following the steps above for attaching artifacts. Even a single failing case's artifacts would be useful here. It is possible from the .tds files alone and the name of the test case we can identify the issue, but less likely. Please remember to remove the PII from the .tds files before inclusion. Thanks.

@rosswbrown
Copy link
Contributor

This can be reactivated when more details are provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants