owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
ClickHouse | ClickHouse | 683,951,583 | 14,276 | filimonov | Please confirm you use one of:
```
case Encoding::DELTA_BINARY_PACKED:
case Encoding::DELTA_LENGTH_BYTE_ARRAY:
case Encoding::DELTA_BYTE_ARRAY:
``` | 2020-08-31T18:29:05 | 2020-08-31T18:29:05 | {
"hooray": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,734,101 | 14,249 | alexey-milovidov | The relevant code does not exist in this release. | 2020-08-31T11:57:10 | 2020-08-31T11:57:10 | {} | MEMBER |
ClickHouse | ClickHouse | 683,740,818 | 12,552 | alexey-milovidov | @KochetovNicolai It imposes the following complications:
- it won't work for RowBinary, TSV, etc... - the user will not be able to deserialize the format with old version;
- it will require to add compatibility logic (add column names near data type names) for Native format;
- it will require to change `columns.txt`... | 2020-08-31T12:12:58 | 2020-08-31T12:12:58 | {} | MEMBER |
ClickHouse | ClickHouse | 683,774,724 | 14,254 | filimonov | Did you pick clickhouse build from Yandex CI ? Or build your own? In second case - did you use Poco from system of from contrib? | 2020-08-31T13:23:03 | 2020-08-31T13:23:03 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,784,788 | 12,552 | alexey-milovidov | > But I don't understand why. The name won't change. I suppose that for old typed it will work the same way.
The user should be able to specify serialization format of the data. The only possible way to do it for these formats is - in type name.
> Also don't understand. Why column names are affected at all?
Co... | 2020-08-31T13:39:24 | 2020-08-31T13:39:24 | {} | MEMBER |
ClickHouse | ClickHouse | 683,833,540 | 14,232 | alexey-milovidov | Performance test Ok. | 2020-08-31T14:59:12 | 2020-08-31T14:59:12 | {} | MEMBER |
ClickHouse | ClickHouse | 683,899,141 | 14,097 | filimonov | Yes, but that is not for s3 table function. @Jokser @excitoon is there a way to use it with table function? | 2020-08-31T16:49:39 | 2020-08-31T16:49:39 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,940,670 | 11,672 | filimonov | Regression.... | 2020-08-31T18:08:43 | 2020-08-31T18:08:43 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,955,676 | 14,260 | azat | >kubectl -n test exec -n test chi-test-cluster-for-alerts-default-0-1-0 -c clickhouse -- clickhouse-client --echo -q "SYSTEM SHUTDOWN"
But why do you halting clickhouse-server? It should be alive.
Otherwise it will indeed throw another error. | 2020-08-31T18:36:45 | 2020-08-31T18:36:45 | {} | MEMBER |
ClickHouse | ClickHouse | 683,977,726 | 8,333 | den-crane | Fixed in https://github.com/ClickHouse/ClickHouse/pull/8367 20.8+ only | 2020-08-31T19:16:04 | 2020-08-31T19:16:04 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,074,766 | 9,339 | s-mx | @alexey-milovidov Hi! What is \l, \d, \c in your understanding? What other commands are desired? | 2020-08-31T22:25:21 | 2020-08-31T22:25:21 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,773,299 | 12,552 | KochetovNicolai | > it won't work for RowBinary, TSV, etc... - the user will not be able to deserialize the format with old version
But I don't understand why. The name won't change. I suppose that for old typed it will work the same way.
> it will require to add compatibility logic (add column names near data type names) for Nati... | 2020-08-31T13:20:36 | 2020-08-31T13:20:36 | {} | MEMBER |
ClickHouse | ClickHouse | 683,796,210 | 14,219 | akuzm | > Cannot reproduce fuzzer error locally.
This query gets the "connection refused" from the start, so what failed is probably the previous query. Not sure how to make this more convenient, maybe fail fast on EOF (error code 32).
https://github.com/ClickHouse/ClickHouse/issues/14275
| 2020-08-31T13:58:32 | 2020-08-31T13:58:32 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,777,161 | 14,264 | den-crane | > --max_compress_block_size=500000000 --max_insert_block_size=10000000000000
> DB::Exception: Allocator: Cannot realloc from 1.00 MiB to 2.00 MiB., errno: 12
It's kinda expected behavior, that huge blocks need a lot of memory. Did you try max_insert_block_size=1000000 (100000) ?
Did you change max_memory_usage (d... | 2020-08-31T13:26:59 | 2020-08-31T14:07:05 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,826,440 | 14,269 | floxard | ClickHouse server version 20.3.12 revision 54433
```
CREATE TABLE test
(
`d` Date
)
ENGINE = ReplicatedMergeTree('/test/test', 'test', d, d, d, 8192)
Ok.
0 rows in set. Elapsed: 0.065 sec.
:) insert into test values ('0000-00-00');
INSERT INTO test VALUES
Ok.
:) insert into test values (today... | 2020-08-31T14:47:46 | 2020-08-31T15:19:14 | {} | NONE |
ClickHouse | ClickHouse | 684,022,002 | 14,298 | OmarBazaraa | I installed the latest version of the official pre-compiled rpm packages for CentOS.
```
$ systemctl status clickhouse-server
● clickhouse-server.service - ClickHouse Server (analytic DBMS for big data)
Loaded: loaded (/etc/systemd/system/clickhouse-server.service; enabled; vendor preset: disabled)
Active:... | 2020-08-31T20:32:11 | 2020-08-31T20:32:11 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,766,742 | 14,269 | den-crane | CH version?
I could not reproduce with 20.8.1.4508 | 2020-08-31T13:09:03 | 2020-08-31T13:09:03 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,857,287 | 14,269 | floxard | ```
2020.08.31 15:20:29.585740 [ 18329 ] {} <Debug> dw.test: There is no part 19700101_19700101_0_0_0 in ZooKeeper, it was only in filesystem
```
How to get this state, @den-crane ? Did you removed part 19700101_19700101_0_0_0 from zookeeper manually? | 2020-08-31T15:38:45 | 2020-08-31T15:38:45 | {} | NONE |
ClickHouse | ClickHouse | 683,892,211 | 14,062 | alexey-milovidov | The format of test output has been changed. | 2020-08-31T16:37:52 | 2020-08-31T16:37:52 | {} | MEMBER |
ClickHouse | ClickHouse | 683,927,213 | 13,861 | siradjev | @vitlibar
this one may be failing too. I'm not sure when they are called:
SQL_IDENTIFIER_QUOTE_CHAR getinfo shall also be failing, but I'm not sure when it is called and how to reproduce.
https://github.com/ClickHouse/ClickHouse/blob/cc4ddfd89e17efc70640228086ef3de39fc8c957/programs/odbc-bridge/getIdentifierQu... | 2020-08-31T17:43:01 | 2020-08-31T17:43:01 | {} | NONE |
ClickHouse | ClickHouse | 683,732,292 | 13,939 | fastio | @azat Thanks for your review.
> Improve the Kafka engine performance by multithreading implementation.
> Can you provide some numbers?
Sure.
In my test environment, the Kafka instance has a topic named `next which has 9TB data which has 4 partitions.
The consumer network bandwidth is limited to 600MB/s. The V... | 2020-08-31T11:52:38 | 2020-08-31T23:48:29 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,138,201 | 14,114 | bohutang | > if there is no 'bad' tables,drop ckdb and recreate it, all tables can be selected.
>
> ```
> mysql> create database ckdb3;
> Query OK, 1 row affected (0.02 sec)
>
> mysql> use ckdb3;
> Database changed
> ```
>
> create db in clickhouse now
>
> ```
> CREATE DATABASE ckdb3
> ENGINE = MaterializeMySQL(... | 2020-09-01T01:33:02 | 2020-09-01T01:33:20 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,794,486 | 14,264 | alexey-milovidov | Raising `max_compress_block_size` is especially harmful. It will slow down all SELECT queries. | 2020-08-31T13:55:48 | 2020-08-31T13:55:48 | {} | MEMBER |
ClickHouse | ClickHouse | 683,844,993 | 14,232 | zhang2014 | What should I do for this PR? | 2020-08-31T15:18:38 | 2020-08-31T15:18:38 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,849,156 | 14,269 | den-crane | Connected to ClickHouse server version 20.8.1 revision 54438.
tail -20000 /var/log/clickhouse-server/clickhouse-server.log|grep test
```
2020.08.31 15:20:06.970246 [ 18342 ] {b679799f-b7d6-45e2-86d2-16b19d0dd7c9} <Debug> executeQuery: (from [::1]:40918) CREATE TABLE test ( `d` Date ) ENGINE = ReplicatedMergeTr... | 2020-08-31T15:25:13 | 2020-08-31T15:25:13 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,928,085 | 14,097 | Jokser | @filimonov Unfortunately no. But the same approach as in storage policy can be reused for table function as well. | 2020-08-31T17:44:42 | 2020-08-31T17:44:42 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,930,708 | 14,269 | den-crane | > ```
> 2020.08.31 15:20:29.585740 [ 18329 ] {} <Debug> dw.test: There is no part 19700101_19700101_0_0_0 in ZooKeeper, it was only in filesystem
> ```
>
> How to get this state, @den-crane ? Did you removed part 19700101_19700101_0_0_0 from zookeeper manually?
I did nothing except your SQL commands. Can you sh... | 2020-08-31T17:49:44 | 2020-08-31T17:49:44 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,946,022 | 14,276 | filimonov | Current master - is the same:
https://github.com/apache/arrow/blob/8f3b029122a8f7149e2061c17a74f4add2677a6e/cpp/src/parquet/column_reader.cc#L713-L716 | 2020-08-31T18:18:30 | 2020-08-31T18:18:30 | {
"laugh": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,090,624 | 14,313 | alexey-milovidov | CC @nikvas0 | 2020-08-31T23:13:42 | 2020-08-31T23:13:42 | {} | MEMBER |
ClickHouse | ClickHouse | 684,092,020 | 14,276 | filimonov | No workarounds. It's just a library used by clickhouse to read parquet doesn't support that encoding - you can open an issue in upstream project https://issues.apache.org/jira/projects/ARROW/issues/
| 2020-08-31T23:18:16 | 2020-08-31T23:18:16 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,736,377 | 14,211 | abyss7 | You have a compilation error:
/ClickHouse/src/Interpreters/DDLWorker.cpp:1461:56: error: use of undeclared identifier 'current_database' | 2020-08-31T12:02:39 | 2020-08-31T12:02:39 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,792,794 | 14,269 | filimonov | Checked on 20.1.8: can't reproduce. | 2020-08-31T13:53:09 | 2020-08-31T13:53:09 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,799,668 | 14,097 | macEar | Ok, thanks
As I understood I can define s3 proxy in `config.xml` or in `config.d` directory as follows:
```xml
<s3_with_resolver>
<type>s3</type>
<endpoint>http://minio1:9001/root/data/</endpoint>
<access_key_id>minio</access_key_id>
<secret_access_key>minio123</secret_access_key>
<proxy... | 2020-08-31T14:04:18 | 2020-08-31T14:04:18 | {} | NONE |
ClickHouse | ClickHouse | 683,734,169 | 14,246 | alexey-milovidov | The relevant code does not exist in this release. | 2020-08-31T11:57:20 | 2020-08-31T11:57:20 | {} | MEMBER |
ClickHouse | ClickHouse | 683,748,120 | 14,268 | alexey-milovidov | Currently there is no support for UDF in ClickHouse, #11. | 2020-08-31T12:28:27 | 2020-08-31T12:28:27 | {} | MEMBER |
ClickHouse | ClickHouse | 683,786,491 | 12,552 | KochetovNicolai | I expect that we use serialization format **instead of** type name. And it will almost always be equal to type name.
And we will use mapping `format -> type name` to determine type name | 2020-08-31T13:42:13 | 2020-08-31T13:42:13 | {} | MEMBER |
ClickHouse | ClickHouse | 683,804,456 | 12,552 | KochetovNicolai | It is not different if we talk about data serialization. But logically it is different, because new server will know about the separation between data type and format. Single in-memory representation of type may be serialized to different formats. | 2020-08-31T14:12:58 | 2020-08-31T14:12:58 | {} | MEMBER |
ClickHouse | ClickHouse | 683,834,462 | 14,232 | alexey-milovidov | Unfortunately, AST Fuzzer check does not give server logs... Currently the only way to figure out what's happening is to copy-paste one of the last queries and execute them with the server built in debug mode (when assertions and extra runtime checks are enabled). @akuzm | 2020-08-31T15:00:44 | 2020-08-31T15:00:44 | {} | MEMBER |
ClickHouse | ClickHouse | 683,930,542 | 12,339 | akuzm | The deadlock is fixed.
The std::move changes I'm not sure are needed at all.
What's left is the print function. @nikitamikhaylov do you want to continue? Maybe we should close this PR and concentrate on something more vital. | 2020-08-31T17:49:23 | 2020-08-31T17:49:23 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,963,329 | 14,045 | radiatorius | > /var/log/clickhouse-server/stderr
**cat /var/log/clickhouse-server/stderr.log**
```
Logging trace to /var/log/clickhouse-server/clickhouse-server.log
Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
Include not found: networks
Include not found: clickhouse_remote_servers
Include not ... | 2020-08-31T18:50:31 | 2020-08-31T18:50:31 | {} | NONE |
ClickHouse | ClickHouse | 684,020,474 | 14,296 | den-crane | Check this https://github.com/ClickHouse/ClickHouse/issues/10368
Also you can execute `alter table detach partition ... / alter table attach partition ` but during detach data will be unavailable for selects and other replicas will download this partition from the node which executed attach. | 2020-08-31T20:29:16 | 2020-08-31T20:31:47 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,093,117 | 9,339 | alexey-milovidov | First step:
`\l` will invoke `SHOW DATABASES`
`\d` will invoke `SHOW TABLES`
`\c db_name` will invoke `USE db_name`; no need to implement full reconnect feature - just allow to change databases this way.
We can even format the query being executed as usual.
| 2020-08-31T23:20:43 | 2020-08-31T23:25:56 | {} | MEMBER |
ClickHouse | ClickHouse | 684,116,377 | 14,261 | CurtizJ | One possible issue is that there are a lot of merges with TTL and it takes a lot of time to execute them due to timeout. Since you have `ttl_only_drop_parts = 1`, you can lower `merge_with_ttl_timeout` without any performance drawbacks.
Also you can run manually query `ALTER TABLE <table_name> MATERIALIZE TTL`.
An... | 2020-09-01T00:20:22 | 2020-09-01T00:20:37 | {} | MEMBER |
ClickHouse | ClickHouse | 684,131,965 | 14,235 | bohutang | This issue has been fixed in https://github.com/ClickHouse/ClickHouse/commit/0586f0d555f7481b394afc55bbb29738cd573a1c | 2020-09-01T01:12:40 | 2020-09-01T01:12:40 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,135,981 | 14,114 | bohutang | 1. Bad 'table' will break the MaterializeMySQL replciation thread, you should drop and re-create it.
2. CREATE TABLE ... SELECT statements are not allowed when using GTID-based replication(and the new version MaterializeMySQL ONLY support GTID mode), it's not safe or you will get:
```
ERROR 1786 (HY000): Statement ... | 2020-09-01T01:25:27 | 2020-09-01T01:25:27 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,747,401 | 14,251 | bohutang | The error message tells us where went wrong, and the sql tell us how the error caused.
We need the sql what's the mysql executed, please provide:
1. what's your table schema
2. what's sqls executed
3. what did you do to clickhouse
So I'll try to reproduce the problem and locate the root cause.
| 2020-08-31T12:26:51 | 2020-08-31T12:29:02 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,795,748 | 14,261 | alexey-milovidov | Let's ask @CurtizJ | 2020-08-31T13:57:46 | 2020-08-31T13:57:46 | {} | MEMBER |
ClickHouse | ClickHouse | 683,822,638 | 13,958 | mcgrawia | thanks for the quick fix! is there a way to know what release with have this fix? | 2020-08-31T14:41:56 | 2020-08-31T14:41:56 | {} | NONE |
ClickHouse | ClickHouse | 683,893,303 | 11,740 | filimonov | @geronsv @jerome-leclercq-contentsquare @kanadaj
Guys, can some of you help to build a reproducible case (`CREATE TABLE ...; INSERT INTO ... ; ALTER ... ;`)?
'Me too' messages don't help too much... | 2020-08-31T16:39:48 | 2020-08-31T16:39:48 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,945,411 | 14,276 | filimonov | https://github.com/apache/arrow/blob/2898577b22a1047516af9ad2bc53490c458cf3b8/cpp/src/parquet/column_reader.cc#L703-L706 | 2020-08-31T18:17:21 | 2020-08-31T18:17:21 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,946,571 | 12,339 | akuzm | > Of course, maybe I will create PR only with function in the near future.
OK, I'll close this one then. | 2020-08-31T18:19:30 | 2020-08-31T18:19:30 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,024,829 | 14,298 | den-crane | try `/etc/init.d/clickhouse-server status `, `/etc/init.d/clickhouse-server stop` | 2020-08-31T20:37:19 | 2020-08-31T20:37:19 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,038,595 | 13,939 | filimonov | > Case 1: Kafka engine with one thread for all consumers
What exactly do you mean? `kafka_num_consumers=1`? Or `kafka_num_consumers=4,kafka_thread_per_consumer=0`? | 2020-08-31T21:03:03 | 2020-08-31T21:03:03 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,145,719 | 11,948 | CurtizJ | I've added a draft of simple test for durability. It starts up clickhouse server in `qemu` VM and runs inserts via `clickhouse benchmark` tool. Then it kills VM in random moment and checks whether table contains broken parts. With `fsync` no broken parts should be appeared in committed state, because they will be commi... | 2020-09-01T01:59:08 | 2020-09-01T02:01:59 | {
"+1": 2
} | MEMBER |
ClickHouse | ClickHouse | 683,946,318 | 14,097 | alexey-milovidov | We should add support for default proxy (resolver). | 2020-08-31T18:19:03 | 2020-08-31T18:19:16 | {
"+1": 1
} | MEMBER |
ClickHouse | ClickHouse | 684,085,651 | 14,232 | alexey-milovidov | https://github.com/ClickHouse/ClickHouse/issues/13981 | 2020-08-31T22:58:17 | 2020-08-31T22:58:17 | {} | MEMBER |
ClickHouse | ClickHouse | 683,734,303 | 14,242 | alexey-milovidov | The relevant code does not exist in this release. | 2020-08-31T11:57:40 | 2020-08-31T11:57:40 | {} | MEMBER |
ClickHouse | ClickHouse | 683,802,084 | 14,110 | akuzm | Let's merge it now because it has a fix. But the difference between queries no. 7 and no. 8 doesn't look good... | 2020-08-31T14:08:44 | 2020-08-31T14:09:03 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,807,161 | 14,254 | DOBRO | I'm using precompiled binary. So it was just downloaded:
`curl -O 'https://builds.clickhouse.tech/master/macos/clickhouse' && chmod a+x ./clickhouse`
following the instructions from https://clickhouse.tech/docs/en/getting-started/install/#from-binaries-non-linux
| 2020-08-31T14:17:13 | 2020-08-31T14:17:13 | {} | NONE |
ClickHouse | ClickHouse | 683,838,664 | 14,269 | floxard | same on 20.1.8 revision 54431 | 2020-08-31T15:07:47 | 2020-08-31T15:07:47 | {} | NONE |
ClickHouse | ClickHouse | 683,904,438 | 14,061 | alexey-milovidov | > Stress test (address) — Killed by signal (in clickhouse-server.log)
It's about Lazy database, @nikvas0 | 2020-08-31T16:59:05 | 2020-08-31T16:59:05 | {} | MEMBER |
ClickHouse | ClickHouse | 684,018,962 | 14,298 | den-crane | Please show an output of
`systemctl status clickhouse-server`
`cat /etc/cron.d/clickhouse-server`
Have you upgrade CH ? Or install it? | 2020-08-31T20:26:17 | 2020-08-31T20:26:59 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,099,984 | 9,339 | alexey-milovidov | And that's it.
All other commands are rarely used and some of them are even harmful. | 2020-08-31T23:26:54 | 2020-08-31T23:26:54 | {} | MEMBER |
ClickHouse | ClickHouse | 683,790,888 | 12,552 | alexey-milovidov | Then it is not too different than what I have proposed... | 2020-08-31T13:49:52 | 2020-08-31T13:49:52 | {} | MEMBER |
ClickHouse | ClickHouse | 683,935,697 | 13,492 | filimonov | It seems only 20.5 is affected.
20.3.17.173 - works
20.4.9.110 - works
20.5.2.7 - FAILS
20.5.5.74 - FAILS
20.6.4.44 - works
20.7.2.30 - works | 2020-08-31T17:59:11 | 2020-08-31T17:59:11 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,090,487 | 14,298 | filimonov | Also it looks like clickhouse was started by init.d (sysv script in the /etc/init.d/clickhouse-server) and you are checking the status of systemd service.
May be it is inaccurate update - did you saw that message during updating the package?
https://github.com/ClickHouse/ClickHouse/blob/9791be4effc3cb74d0e7460a13... | 2020-08-31T23:13:14 | 2020-08-31T23:13:14 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,168,431 | 14,282 | l1t1 | where is the release notes? | 2020-09-01T03:10:05 | 2020-09-01T03:10:05 | {} | NONE |
ClickHouse | ClickHouse | 684,182,004 | 14,251 | liangli1213 | @BohuTANG I think I have found the root cause, exactly speaking, I found a workaround to avoid such issue happen and keep replication proceeding continuously.
My script has a piece of code which use a transaction to refresh a table every 5 minutes.
```
BEGIN;
DELETE * FROM TABLE WHERE ****;
INSERT INTO TABLE *... | 2020-09-01T03:54:10 | 2020-09-01T03:54:10 | {} | NONE |
ClickHouse | ClickHouse | 683,753,590 | 14,268 | pavitrakumar78 | @alexey-milovidov Ah.. Ok. Thanks for clarifying! Any idea about arrayshift or emulating `lag` function? The edit in my original post shows an example: calculation of price - price 10 days ago. | 2020-08-31T12:41:08 | 2020-08-31T12:41:08 | {} | NONE |
ClickHouse | ClickHouse | 683,768,701 | 14,268 | filimonov | > @alexey-milovidov Ah.. Ok. Thanks for clarifying! Any idea about arrayshift or emulating `lag` function? The edit in my original post shows an example: calculation of price - price 10 days ago.
https://github.com/ClickHouse/ClickHouse/issues/5485
https://github.com/ClickHouse/ClickHouse/issues/1469 | 2020-08-31T13:13:01 | 2020-08-31T13:13:01 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,958,630 | 13,939 | azat | >Yes, the name of setting is inappropriate. So can we name the setting as kafka_thread_per_consumer ?
LGTM (and don't forget to update [docs](https://github.com/ClickHouse/ClickHouse/blob/master/docs/en/engines/table-engines/integrations/kafka.md)) | 2020-08-31T18:42:03 | 2020-08-31T18:42:03 | {} | MEMBER |
ClickHouse | ClickHouse | 683,988,475 | 10,004 | azat | @alexey-milovidov #12982 indeed looks related, but it is hard to say (since there is no reproducer)
@johnatannvmd can you verify (preferably on some staging) that #12982 helps you? (it has been backported to 20.3, in particular v20.3.17.173-lts and v20.3.16.165-lts) | 2020-08-31T19:35:31 | 2020-08-31T19:35:31 | {} | MEMBER |
ClickHouse | ClickHouse | 684,006,701 | 14,267 | alesapin | Tests ok | 2020-08-31T20:01:20 | 2020-08-31T20:01:20 | {} | MEMBER |
ClickHouse | ClickHouse | 684,009,327 | 14,294 | Akazz | The failed check "Push to dockerhub" should not be related. | 2020-08-31T20:06:41 | 2020-08-31T20:06:41 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,078,183 | 12,513 | adrian17 | Still reproducible on 20.7.2. | 2020-08-31T22:34:59 | 2020-08-31T22:34:59 | {} | NONE |
ClickHouse | ClickHouse | 684,088,320 | 14,298 | filimonov | Please
1) check the pid of the running clickhouse - server process = pid reporter by service status
2) show the content of /run/clickhouse-server/clickhouse-server.pid
3) show the content of /mnt/clickhouse/status
| 2020-08-31T23:06:13 | 2020-08-31T23:06:13 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,772,409 | 14,230 | filimonov | Duplicate
#5125
#5409
#4159
#1178
#3312
and others... | 2020-08-31T13:19:07 | 2020-08-31T13:19:07 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,789,989 | 14,264 | filimonov | > `--max_compress_block_size=500000000 --max_insert_block_size=10000000000000`
Those settings have no sense at all. Do you have a server with > 10 Terabytes of RAM? | 2020-08-31T13:48:15 | 2020-08-31T13:48:15 | {
"+1": 3,
"laugh": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,835,424 | 14,232 | akuzm | > Unfortunately, AST Fuzzer check does not give server logs... Currently the only way to figure out what's happening is to copy-paste one of the last queries and execute them with the server built in debug mode (when assertions and extra runtime checks are enabled). @akuzm
For now, replace `fuzzer.log` with `server.... | 2020-08-31T15:02:14 | 2020-08-31T15:02:14 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,843,398 | 14,269 | floxard | same on 20.8.1 revision 54438 | 2020-08-31T15:15:55 | 2020-08-31T15:15:55 | {} | NONE |
ClickHouse | ClickHouse | 683,872,416 | 14,232 | alexey-milovidov | Nothing is remaining. We need to classify this fuzzer failure. It usually finds some already existing issues in corner cases.
The PR is Ok. | 2020-08-31T16:02:58 | 2020-08-31T16:03:16 | {} | MEMBER |
ClickHouse | ClickHouse | 683,889,272 | 14,277 | alexey-milovidov | @kssenii | 2020-08-31T16:32:56 | 2020-08-31T16:32:56 | {} | MEMBER |
ClickHouse | ClickHouse | 683,905,547 | 14,277 | kssenii | @siamskoi will be fixed when https://github.com/ClickHouse/ClickHouse/pull/12761 is merged. | 2020-08-31T17:01:04 | 2020-08-31T17:01:04 | {
"+1": 1
} | MEMBER |
ClickHouse | ClickHouse | 684,138,402 | 12,171 | taiyang-li | @filimonov greping by message keyword will not be very convenient when the message keyword is very common. Print source file and line number would help you find the source code more directly, and the new added part to the log is short. | 2020-09-01T01:33:41 | 2020-09-01T01:33:41 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,788,807 | 14,266 | den-crane | It's impossible to implement with MV. MV is an insert trigger.
` sum(bytes) as bytes, ... GROUP BY timestamp` works against inserted buffer and does not read data from `log_data_local` table.
Probably you could partially emulate this behavior with TTL/rollup https://github.com/ClickHouse/ClickHouse/pull/10537 | 2020-08-31T13:46:12 | 2020-08-31T13:46:12 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,848,476 | 14,269 | floxard | It is important to use old syntax like "ReplicatedMergeTree(zkpath,replica,other,params)" and **Replicated**MergeTree engine to reproduce | 2020-08-31T15:24:09 | 2020-08-31T15:24:09 | {} | NONE |
ClickHouse | ClickHouse | 683,869,742 | 14,095 | akuzm | Unbundled build broken in master. | 2020-08-31T15:58:48 | 2020-08-31T15:58:48 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,952,277 | 10,373 | azat | @alexey-milovidov any thoughts on this? | 2020-08-31T18:30:17 | 2020-08-31T18:30:17 | {} | MEMBER |
ClickHouse | ClickHouse | 684,045,809 | 14,276 | blackrez | Hello,
This is it DELTA_BYTE_ARRAY the responsible of the error.
have you an idea on how to avoid this error ?
Thanks. | 2020-08-31T21:18:17 | 2020-08-31T21:18:17 | {} | NONE |
ClickHouse | ClickHouse | 684,171,451 | 14,256 | dmthuc | Thank you, I will try it | 2020-09-01T03:19:28 | 2020-09-01T03:19:28 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,744,602 | 11,740 | geronsv | We have the same problem with ReplicatedSummingMergeTree in 20.3.17 revision 54433. | 2020-08-31T12:20:45 | 2020-08-31T13:27:00 | {} | NONE |
ClickHouse | ClickHouse | 683,929,820 | 8,333 | filimonov | Fixed? Can be closed? | 2020-08-31T17:48:03 | 2020-08-31T17:48:03 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,026,359 | 14,298 | OmarBazaraa | Still giving me `stopped` status.
```
$ /etc/init.d/clickhouse-server status
clickhouse-server service is stopped
``` | 2020-08-31T20:40:01 | 2020-08-31T20:40:01 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,758,592 | 14,219 | 4ertus2 | Fuzzer error:
```
Error on processing query: SELECT ignore(256, 2), * FROM lc_null_int8_defnull AS values
Code: 210, e.displayText() = DB::NetException: Connection refused (localhost:9000)
```
Cannot reproduce fuzzer error locally. | 2020-08-31T12:52:40 | 2020-08-31T12:52:40 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,790,320 | 14,261 | macEar | Could you please explain to me why `delete_ttl_info_max` is in past but those parts (expired ones) include more than 0 rows? If there were only parts with 0 rows then I wouldn't question you. | 2020-08-31T13:48:48 | 2020-08-31T13:50:29 | {} | NONE |
ClickHouse | ClickHouse | 683,872,716 | 14,045 | filimonov | Good! And one more thing: /var/log/clickhouse-server/stderr content, please. | 2020-08-31T16:03:29 | 2020-08-31T16:03:29 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 683,998,910 | 14,276 | filimonov | > The file are provided by an external providers. I don't know the library used to generate files.
You can use parquet-tools ( https://github.com/apache/parquet-mr/tree/master/parquet-tools ) to inspect your parquet file. | 2020-08-31T19:45:18 | 2020-08-31T19:45:18 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 684,157,935 | 14,260 | Slach | @azat thanks you. ok I understood what exactly happens ;)
we just need to insert sync 1kk rows one block to the distributed table to achieve timeout | 2020-09-01T02:38:04 | 2020-09-01T02:38:04 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 665,681,294 | 10,193 | alexey-milovidov | @blinkov This task is still relevant.
We should either merge this pull request or you must propose an alternative solution. | 2020-07-29T13:59:02 | 2020-07-29T13:59:02 | {} | MEMBER |
ClickHouse | ClickHouse | 666,240,560 | 9,259 | veqryn | I was about to make a new issue for this exact problem.
I spent hours trying to debug something that was just a typo in a query, and I had I had seen the original error message just telling me it was a simple typo. | 2020-07-30T08:56:35 | 2020-07-30T08:56:35 | {
"+1": 2
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.