[MCOL-3580] Many window function queries returned syntax errors Created: 2019-10-31  Updated: 2020-03-27  Resolved: 2020-03-27

Status: Closed
Project: MariaDB ColumnStore
Component/s: MariaDB Server
Affects Version/s: 1.4.1
Fix Version/s: 1.4.4

Type: Bug Priority: Major
Reporter: Daniel Lee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Sprint: 2020-3, 2020-4, 2020-5

 Description   

Build tested: 1.4.1-1

[dlee@cs-tst-01 centos7]$ cat gitversionInfo.txt
engine commit:
3e7a964

Test suite: autopilot.windowFunctions

There are a total of 6576 queries in the test suite. 2976 of them failed with a syntax error. All these queries got executed successfully in 1.2.5-1 and 1.4.0-1.

select o_custkey, regr_syy(o_custkey,o_orderkey) OVER (PARTITION BY 55 ORDER BY o_custkey ,o_orderkey ROWS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING) from orders order by 1, 2;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'OVER (PARTITION BY 55 ORDER BY o_custkey ,o_orderkey ROWS BETWEEN CURRENT ROW AN' at line 1

All returned errors complain about "near the OVER keyword"



 Comments   
Comment by David Hall (Inactive) [ 2020-02-11 ]

This appears fixed by other things.

Comment by Daniel Lee (Inactive) [ 2020-03-27 ]

Build verified: 1.4.4-1 source

/root/ColumnStore/buildColumnstoreFromGithubSource/server
commit ec0071afa50b78930860a14802b8cfc9791f7d13
Author: Sergei Petrunia <psergey@askmonty.org>
Date: Thu Mar 26 01:26:39 2020 +0300

MDEV-21887: federatedx crashes on SELECT ... INTO query in select_handler code

/root/ColumnStore/buildColumnstoreFromGithubSource/server/engine
commit 6e953d01d268161ac50dabb6aa9a122ed1d43e0f
Merge: 4468c93 ba06727
Author: Gagan Goel <gagan.nith@gmail.com>
Date: Thu Mar 26 11:41:35 2020 -0400

Merge pull request #1117 from drrtuy/MCOL-3828_1_4

MCOL-3828 This commit replaces the method that calls JOIN::optimise()

Executed window function tests suite. Verified that reported issue has been fixed.

Generated at Thu Feb 08 02:43:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.