You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When upgrading from ksqlDB 5.5.x to 6.0.x+, if an existing query uses a field named PERIOD, ksqlDB fails to parse the query in the command topic in the new version. Upgrades should be able to execute existing queries without any changes. PERIOD was added as a keyword in 6.0.x to support GRACE PERIOD, but was not added a non-reserved word, which leads to this issue.
To Reproduce
ksqlDB version: 6.0.x+
Define the following query in ksqlDB 5.5.x:
create stream s asselect level as PERIOD from ksql_processing_log emit changes;
Upgade ksqlDB in place (keeping same command topic) to 6.0.x, and start the server.
Expected behavior
Server starts and executes all existing queries successfully.
Actual behaviour
Exception parsing statement in ksqlDB command topic:
Describe the bug
When upgrading from ksqlDB 5.5.x to 6.0.x+, if an existing query uses a field named
PERIOD
, ksqlDB fails to parse the query in the command topic in the new version. Upgrades should be able to execute existing queries without any changes.PERIOD
was added as a keyword in 6.0.x to supportGRACE PERIOD
, but was not added a non-reserved word, which leads to this issue.To Reproduce
ksqlDB version: 6.0.x+
Define the following query in ksqlDB 5.5.x:
Upgade ksqlDB in place (keeping same command topic) to 6.0.x, and start the server.
Expected behavior
Server starts and executes all existing queries successfully.
Actual behaviour
Exception parsing statement in ksqlDB command topic:
Additional context
The text was updated successfully, but these errors were encountered: