-
Notifications
You must be signed in to change notification settings - Fork 1k
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
KSQL 5.4 error says a stream is a table #3523
Labels
Comments
Against another stream I get this instead:
Both objects are
Same point as above for this different error message ( |
big-andy-coates
added a commit
to big-andy-coates/ksql
that referenced
this issue
Nov 18, 2019
Fixes: confluentinc#3523 Remove the 'table' in the error message 'Table `foo` is not materialized' as it won't always be a table: it could be a stream.
2 tasks
big-andy-coates
added a commit
that referenced
this issue
Nov 20, 2019
Fixes: #3523 Remove the 'table' in the error message 'Table `foo` is not materialized' as it won't always be a table: it could be a stream.
@big-andy-coates is this in ksqlDB 0.6? I still see the problem, e.g. against a STREAM:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CLI v5.4.0-beta190925193823, Server v5.4.0-beta190925193823
The error message says that it's a
TABLE
, but I've created aSTREAM
. Also if I need to includeEMIT CHANGES
then this message should include the explanation as shown in #3521 because this is a statement that worked fine <5.4The text was updated successfully, but these errors were encountered: