Skip to content

Code: 40, e.displayText() = DB::Exception: Checksum doesn't match: corrupted data. Reference: 8a58086e26544cb09217aa1bba09a1d9. Actual: 7c7a5cd56cac83a714e286dbbd46acb5. #11398

@shizihao123

Description

@shizihao123

(you don't have to strictly follow this form)

Describe the unexpected behaviour
when I complie a new client with the same code,it just returns Code 40, DB::Exception: Checksum doesn't match: corrupted data. But The Server side && Client side doesn't change
anything. The error stack from the server side is as following:
image

How to reproduce
just use client to visit server

  • Which ClickHouse server version to use
    ClickHouse server version 19.14.7 revision 54425
  • Which interface to use, if matters
    ClickHouse client version 19.14.7.15
  • Non-default settings, if any
  • CREATE TABLE statements for all tables involved
  • Sample data for all these tables, use clickhouse-obfuscator if necessary
  • Queries to run that lead to unexpected result

Expected behavior
Should have no error.

Error message and/or stacktrace
image

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    obsolete-versionst-need-infoWe need extra data to continue (waiting for response). Either some details or a repro of the issue.unexpected behaviourResult is unexpected, but not entirely wrong at the same time.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions