We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Assume a table with schema: ROWTIME|ROWKEY|METRICS_NAME |CLUSTER|TOPIC_NAME|ENV|AVG_VALUE
ROWTIME|ROWKEY|METRICS_NAME |CLUSTER|TOPIC_NAME|ENV|AVG_VALUE
Assume the table contains the following two rows: |1571347727133 |fetch_latency_ms|+|null|+|null|+|staging : Window{start=1571347680000 end=-}|fetch_latency_ms|null|null|staging|9.44924| |1571347727133 fetch_latency_ms|+|cluster_lmn|+|topic_2|+|staging : Window{start=1571347680000 end=-} |fetch_latency_ms |cluster_lmn |topic_2 |staging| 7.988785
|1571347727133 |fetch_latency_ms|+|null|+|null|+|staging : Window{start=1571347680000 end=-}|fetch_latency_ms|null|null|staging|9.44924| |1571347727133 fetch_latency_ms|+|cluster_lmn|+|topic_2|+|staging : Window{start=1571347680000 end=-} |fetch_latency_ms |cluster_lmn |topic_2 |staging| 7.988785
Note how the key contains the string null in the first row.
Issue query: select * from metrics_table where rowkey='fetch_latency_ms|+|null|+|null|+|null'; Error reported: Server Error
select * from metrics_table where rowkey='fetch_latency_ms|+|null|+|null|+|null';
Server Error
To Reproduce Steps to reproduce the behavior, include:
Expected behavior Support rowkeys that contain the null string
Actual behaviour A clear and concise description of what actually happens, including:
[2019-10-17 15:47:15,556] ERROR Server Error (io.confluent.ksql.cli.console.Console:323)
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Fix bug confluentinc#3617
ea3b53a
Hi @vpapavas I am trying to understand what the '+' symbols represent in the example row:
|1571347727133 |fetch_latency_ms|+|null|+|null|+|staging : Window{start=1571347680000 end=-}|fetch_latency_ms|null|null|staging|9.44924|
Are you missing a '|' ?
Sorry, something went wrong.
6697d96
fix: Don't throw NPE on null columns (#3647)
6969768
* Fix bug #3617
Hey @purplefox !
Sorry I just saw your message.
This is how Ksql currently represents keys that consist of multiple columns.
Successfully merging a pull request may close this issue.
Describe the bug
Assume a table with schema:
ROWTIME|ROWKEY|METRICS_NAME |CLUSTER|TOPIC_NAME|ENV|AVG_VALUE
Assume the table contains the following two rows:
|1571347727133 |fetch_latency_ms|+|null|+|null|+|staging : Window{start=1571347680000 end=-}|fetch_latency_ms|null|null|staging|9.44924| |1571347727133 fetch_latency_ms|+|cluster_lmn|+|topic_2|+|staging : Window{start=1571347680000 end=-} |fetch_latency_ms |cluster_lmn |topic_2 |staging| 7.988785
Note how the key contains the string null in the first row.
Issue query:
select * from metrics_table where rowkey='fetch_latency_ms|+|null|+|null|+|null';
Error reported:
Server Error
To Reproduce
Steps to reproduce the behavior, include:
Master
Provided above
Provided above
Expected behavior
Support rowkeys that contain the null string
Actual behaviour
A clear and concise description of what actually happens, including:
Server Error
Server Error
ksql-cli logs contain:
[2019-10-17 15:47:15,556] ERROR Server Error (io.confluent.ksql.cli.console.Console:323)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: