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

WINDOWSTART not recognized for GROUP BY #5595

Closed
harlev opened this issue Jun 10, 2020 · 4 comments
Closed

WINDOWSTART not recognized for GROUP BY #5595

harlev opened this issue Jun 10, 2020 · 4 comments
Labels

Comments

@harlev
Copy link
Contributor

harlev commented Jun 10, 2020

When creating a windowed table, trying to use the WINDOWSTART in GROUP BY generates an error

To Reproduce

  1. ksqlDB 0.9.0
  2. ksqldb-cli:0.9.0
  3. Steps to reproduce
  • CREATE STREAM s1 (a VARCHAR, b INT) WITH (kafka_topic='s1', partitions=1, value_format = 'avro');
  • CREATE TABLE t1 AS SELECT count(*) FROM s1 WINDOW TUMBLING (SIZE 10 MINUTES) GROUP BY a EMIT CHANGES;
  • SELECT count(*), WINDOWSTART FROM t1 GROUP BY WINDOWSTART EMIT CHANGES;
  • Get the error Unknown column WINDOWSTART.

Note that running SELECT WINDOWSTART FROM t1 EMIT CHANGES; works successfully in this scenario.

Expected behavior
Grouping on WINDOWSTART should work like for any other table column.

Actual behaviour

  • CLI output: Unknown column WINDOWSTART.
  • No error in the log while running the failed query.
@harlev
Copy link
Contributor Author

harlev commented Jun 10, 2020

More insights:
SELECT * FROM t1 WHERE WINDOWSTART > 0 GROUP BY 1 EMIT CHANGES;
generates:

Unknown column WINDOWSTART.

While
SELECT * FROM t1 WHERE WINDOWSTART > 0 EMIT CHANGES;
works just fine.

@big-andy-coates
Copy link
Contributor

Thanks for reporting @harlev. This is indeed an issue and a fix is on our roadmap, but will take a bit of reworking to make it work. Closing this issue as a duplicate of #4397

@devopg
Copy link

devopg commented Apr 10, 2022

its fixed ? i got Unknown column WINDOWSTART in latest ksqldb

@mjsax
Copy link
Member

mjsax commented Apr 12, 2022

Closing this issue as a duplicate of #4397

Not fixed. #4397 is still open. (This ticket was only closed as duplicate.)

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

No branches or pull requests

5 participants