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
The assignment of internal column names is not consistent across different queries. The problem might be in the auto-increment when creating a new internal column name.
To Reproduce
Steps to reproduce the behavior, include:
The version of KSQL.
Master
Sample source data.
No need for source data
Any SQL statements you ran
First create a table with a value column without any alias. Then, try to create a new table that uses this column again without an alias.
describe metrics_cube;
Name : METRICS_CUBE
Field | Type
---------------------------------------------------
ROWTIME | BIGINT (system)
METRICS_STREAM.ROWKEY | VARCHAR(STRING)
METRICS_NAME | VARCHAR(STRING)
METRICS_VALUE | DOUBLE
KSQL_COL_2 | ARRAY<VARCHAR(STRING)>
---------------------------------------------------
For runtime statistics and query details run: DESCRIBE EXTENDED <Stream,Table>;
CREATE TABLE metrics_table AS
SELECT metrics_name, KSQL_COL_2, avg(metrics_value) from metrics_cube WINDOW TUMBLING (size 60 seconds)
GROUP BY metrics_name, KSQL_COL_2;
Gives the error Duplicate values found in schema: KSQL_COL_2 DOUBLE
Expected behavior
Assign a new internal column name KSQL_COL_3 to the non-aliased column
Actual behaviour
A clear and concise description of what actually happens, including:
CLI output
Error messages Duplicate values found in schema: KSQL_COL_2 DOUBLE
KSQL logs
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The assignment of internal column names is not consistent across different queries. The problem might be in the auto-increment when creating a new internal column name.
To Reproduce
Steps to reproduce the behavior, include:
Master
No need for source data
First create a table with a value column without any alias. Then, try to create a new table that uses this column again without an alias.
Gives the error
Duplicate values found in schema:
KSQL_COL_2DOUBLE
Expected behavior
Assign a new internal column name
KSQL_COL_3
to the non-aliased columnActual behaviour
A clear and concise description of what actually happens, including:
Duplicate values found in schema:
KSQL_COL_2DOUBLE
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: