question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Question]Receive inconsistent query results when connected to Clickhouse(?)

See original GitHub issue

Using the same Clickhouse database and the same SQL statement, the results obtained by superset and idea are inconsistent; Specifically, superset should only query some data, but I don’t know why

Expected results

When I used the pie chart to visualize the data in a Clickhouse database, I found this problem. The queried data was incorrect. To be exact, I only got some data, but I didn’t make any settings. I felt that there was a problem somewhere

Screenshots

PIE BAR REAL RESULT WRONG

Environment

(please complete the following information):

  • superset version: docker pull apache/superset:master
  • python version: python --version 3.8

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven’t found one similar.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:14 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
junlincccommented, Aug 16, 2021

Is it only happening in clickhouse data? What’s the expected results from your query? the ones showing in the spreadsheet screenshot? both results from Explore and SQL lab are incorrect? can you double check if any filters, same as in superset was added to your query in excel?

@zhaoyongjie please follow up in the issue, if it’s validated by the users with more info come back, let me know.

0reactions
stale[bot]commented, Apr 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Inconsistent query results · Issue #135 · ClickHouse ...
Connected to ClickHouse server version 1.1.54022. TOTAL number of records loaded. This is consistent with the raw CSV data. :) select count() ......
Read more >
[GitHub] [superset] IKkSssDendi commented on issue #16276 ...
[GitHub] [superset] IKkSssDendi commented on issue #16276: [Question]Receive inconsistent query results when connected to Clickhouse(?).
Read more >
Troubleshooting | ClickHouse Docs
Installation; Connecting to the server; Query processing; Efficiency of query ... displayText() = Connection refused, e.what() = Connection refused.
Read more >
Clickhouse external dictionary returns inconsistent results
This query was using the cached dict in the FROM clause and so the filtering was applied to the cached dict:
Read more >
Clickhouse: Inconsistent backup/restore for latest partition ...
Execute the same select statement as in step 2 to check if there are any differences. The problem is that for one of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found