-
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 LEFT JOIN IS NOT WORKING. #968
Comments
Which version are you running? This should be fixed in the latest master. |
@rodesai Hi I am using the latest version of KSQL 0.5 and confluent 4.0.0 |
I got the same error but the latest master works fine for me. |
@VladMl Hi Dude, I hope you are running the same version or do you mean building the latest code from the repository. I tried that but its failing due restriction to use the public repositories in our organization. |
@zamirarif |
This was fixed by #927 . The patch will be part of the 4.1 release at the end of march / early April. |
@apurvam Thanks for the response & closing the ticket. |
Hello Folks,
I have 2 kafka avro topics deal & expense but data had alot of whitespaces to clear that I have created following topic and table with trimmed data.
DEAL_STREAM
EXPENSE_TABLE
ksql> describe EXPENSE_TABLE;
Field | Type
ROWTIME | BIGINT (system)
ROWKEY | VARCHAR(STRING) (system)
KSQL_COL_0 | VARCHAR(STRING)
KSQL_COL_1 | VARCHAR(STRING)
KSQL_COL_2 | VARCHAR(STRING)
ksql> describe deal_stream;
Field | Type
ROWTIME | BIGINT (system)
ROWKEY | VARCHAR(STRING) (system)
KSQL_COL_0 | VARCHAR(STRING)
KSQL_COL_1 | VARCHAR(STRING)
KSQL_COL_2 | VARCHAR(STRING)
When I execute the following Query its giving me null pointer exception.
I tried following queries.
1:
ksql> CREATE STREAM deal_expense_new AS SELECT td.KSQL_COL_0 , te.KSQL_COL_1 FROM deal_stream td LEFT JOIN expense_table te ON td.KSQL_COL_0 = te.KSQL_COL_0;
2:
ksql> CREATE STREAM deal_expense_new AS SELECT td.KSQL_COL_0 AS KSQL_COL_0 , te.KSQL_COL_1 FROM deal_stream td LEFT JOIN expense_table te ON td.KSQL_COL_0 = te.KSQL_COL_0;
3:
The text was updated successfully, but these errors were encountered: