windowFunctions/misc/bug5366_01.sql
- select * from region where (r_regionkey+1) in (select min(n_regionkey) over() from nation where r_regionkey=n_regionkey);
gives back 25 rows (a lot of duplicates). Since the query is in form "select * from <table> where <condition>" it should not return more rows than there are in the table, which is 5 for the table region
-------------------------------------------------------------------------------------------------------------------------------------------+
| r_regionkey | r_name | r_comment |
-------------------------------------------------------------------------------------------------------------------------------------------
| 0 | AFRICA | lar deposits. blithely final packages cajole. regular waters are final requests. regular accounts are according to |
| 0 | AFRICA | lar deposits. blithely final packages cajole. regular waters are final requests. regular accounts are according to |
| 0 | AFRICA | lar deposits. blithely final packages cajole. regular waters are final requests. regular accounts are according to |
| 0 | AFRICA | lar deposits. blithely final packages cajole. regular waters are final requests. regular accounts are according to |
| 0 | AFRICA | lar deposits. blithely final packages cajole. regular waters are final requests. regular accounts are according to |
| 1 | AMERICA | hs use ironic, even requests. s |
| 1 | AMERICA | hs use ironic, even requests. s |
| 1 | AMERICA | hs use ironic, even requests. s |
| 1 | AMERICA | hs use ironic, even requests. s |
| 1 | AMERICA | hs use ironic, even requests. s |
| 2 | ASIA | ges. thinly even pinto beans ca |
| 2 | ASIA | ges. thinly even pinto beans ca |
| 2 | ASIA | ges. thinly even pinto beans ca |
| 2 | ASIA | ges. thinly even pinto beans ca |
| 2 | ASIA | ges. thinly even pinto beans ca |
| 3 | EUROPE | ly final courts cajole furiously final excuse |
| 3 | EUROPE | ly final courts cajole furiously final excuse |
| 3 | EUROPE | ly final courts cajole furiously final excuse |
| 3 | EUROPE | ly final courts cajole furiously final excuse |
| 3 | EUROPE | ly final courts cajole furiously final excuse |
| 4 | MIDDLE EAST | uickly special accounts cajole carefully blithely close requests. carefully final asymptotes haggle furiousl |
| 4 | MIDDLE EAST | uickly special accounts cajole carefully blithely close requests. carefully final asymptotes haggle furiousl |
| 4 | MIDDLE EAST | uickly special accounts cajole carefully blithely close requests. carefully final asymptotes haggle furiousl |
| 4 | MIDDLE EAST | uickly special accounts cajole carefully blithely close requests. carefully final asymptotes haggle furiousl |
| 4 | MIDDLE EAST | uickly special accounts cajole carefully blithely close requests. carefully final asymptotes haggle furiousl |
-------------------------------------------------------------------------------------------------------------------------------------------
25 rows in set (0.14 sec)
David.Hall Is there anything that needs attention. If so, could you share the steps to run the test automatically?
From the discussions I get that it sorta runs (though , my last comment is I think still valid), and 5 queries do not run that are not supposed to run ,because they failed on Calpont
wlad Other than windowFunctions/misc/bug5366_01.sql, which other windowFunctions test queries are failing or returning incorrect results ?
For that (incorrect result sets), I really need to know how to run the test automated 
the one i picked looked obvious, Davi Hall says it is fixed now,
I remember some other test was failing complaining about missing SQL function . Will provide more info tomorrow on that
David.HallIs this same as MCOL-93 ?
MCOL-40 is not related to MCOL-93. MCOL-93 is about erroneous syntax errors and MCOL-40 is about a wrong result. This test should be re-run as it may have been a manifestation of a bug that was fixed prior to tracking in JIRA and may no longer be an issue.
Actually, while the above is true to a point, it should be pointed out that MCOL-40 was first written as a catch-all for all failing Windows functions and devolved to a be about a specific problem. So in a way, MCOL-40 and MCOL-93 are related, but fixing one does not fix the other.
The query mentioned in the notes should be verified as working and if it is, MCOL-40 should be closed and any further Windows Function problems found should each have individual JIRA issues. At the time this issue was written, we were just trying to broadly catalog the problems in columnstore. I believe we have evolved to having individula JIRA for separate bugs.
If MCOL-40 is regarding wrong result, then it is duplicate of MCOL-37 that Daniel Lee has already reported - hence closing this.
duplicate of MCOL-37