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.

In clickhouse 19.3.3 error code is parsed incorrectly

See original GitHub issue

After upgrading to clickhouse 19.3.3 from 19.1.1 ServerError is always returned with code=0. I get 'Code: 60, e.displayText() = DB::Exception: Table test.django_clickhouse_migrations doesn\‘t exist.’ message from clickhouse, which is not parsed by regexp(it doesn’t have e.what)

Issue Analytics

State:
Created 5 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

M1ha-Shvncommented, Feb 19, 2019

@Foton, may be it’s not infi bug in your case? See https://github.com/yandex/ClickHouse/issues/4431

0reactions

ishiravcommented, Jun 13, 2019

Fixed on v1.1.0

Top Results From Across the Web

2019 Changelog | ClickHouse Docs

Fix incorrect float parsing in Values #7817 #7870 (tavplubix) ... #6599 (Anton Popov); HTTP status code for INCORRECT_DATA and TYPE_MISMATCH error codes was ......

Troubleshooting | ClickHouse Docs

If you are seeing an error message like one of these, your IP Access List may be denying ... Code: 210. ... Unexpected...

Syntax | ClickHouse Docs

The INSERT INTO t VALUES fragment is parsed by the full parser, and the data (1, 'Hello, world'), (2, 'abc'), (3, 'def') is...

2022 Changelog | ClickHouse Docs

Fix possible logical error Array sizes mismatched while parsing JSON object ... It is now possible to set a custom error code for...

2020 Changelog | ClickHouse Docs

Now such functions return NULL on parsing errors instead of throwing exception. ... Fix a very wrong code in TwoLevelStringHashTable implementation, ...