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 | 858,282,285 | 25,139 | lopn | @abyss7 can you help me? | 2021-06-10T04:06:18 | 2021-06-10T04:06:18 | {} | NONE |
ClickHouse | ClickHouse | 858,363,496 | 24,897 | excitoon | @alexey-milovidov main process was killed with SIGSEGV, probably because of sanitizer checks. However I can not see anything in `stderr.log`. I may guess that it was restarted externally and rewrote `stderr.log`. | 2021-06-10T06:54:04 | 2021-06-10T06:54:04 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,388,226 | 16,503 | excitoon | @azat about your comments parallel writes and thread pool would only be used in mulltipart mode, so it is already controlled by `s3_max_single_part_upload_size`. Do we really need an additional setting?
Interface is needed because we can not use thread pools from IO otherwise. | 2021-06-10T07:35:45 | 2021-06-10T07:35:45 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,482,353 | 24,406 | CurtizJ | Test failures are unrelated. | 2021-06-09T08:06:33 | 2021-06-09T08:06:33 | {} | MEMBER |
ClickHouse | ClickHouse | 857,599,768 | 25,109 | filimonov | Clickhouse can not access the node in zookeeper which he just created.
Check zookeeper configuration and zookeeper issues / disconnects, may be jute.maxbuffer | 2021-06-09T11:01:13 | 2021-06-09T11:01:13 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,828,283 | 24,778 | shacuros | As `select final` will almost everytime need to scan multiple parts, i'd suggest that when the final keyword is used, the optimizer should always ignore aggregated projections, and just consider main table or projections with different sortings only. At least for any partition with multiple parts.
As for the origina... | 2021-06-09T15:58:13 | 2021-06-10T09:19:34 | {
"+1": 1
} | NONE |
ClickHouse | ClickHouse | 857,437,174 | 24,885 | vdimir | @mergifyio update | 2021-06-09T06:55:56 | 2021-06-09T06:55:56 | {
"+1": 1
} | MEMBER |
ClickHouse | ClickHouse | 857,479,450 | 23,656 | kssenii | @Mergifyio update | 2021-06-09T08:02:09 | 2021-06-09T08:02:09 | {
"+1": 1
} | MEMBER |
ClickHouse | ClickHouse | 857,580,874 | 24,941 | filimonov | @Mergifyio update | 2021-06-09T10:30:12 | 2021-06-09T10:30:12 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,591,522 | 25,112 | filimonov | Every part is a folder on a filesystem with files inside. I see about 400k folders which need to be iterated during the server startup. I guess inside every folder you have from 10 to few thousands of files (depends on the number of columns).
So your question can sound "how can I iterate over tens of millions of fil... | 2021-06-09T10:47:31 | 2021-06-09T10:48:15 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,159,698 | 25,022 | mergify[bot] | **Command `update`: success**
> **Branch has been successfully updated**
>
| 2021-06-09T23:11:20 | 2021-06-09T23:11:20 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,229,906 | 10,892 | yingshikong186 | i replicate the problem in version 21.6.1 | 2021-06-10T02:24:54 | 2021-06-10T02:24:54 | {} | NONE |
ClickHouse | ClickHouse | 858,256,984 | 25,120 | deepprakash345 | @shacuros , This worked, thank you so much | 2021-06-10T03:45:30 | 2021-06-10T03:45:30 | {} | NONE |
ClickHouse | ClickHouse | 858,408,670 | 25,070 | larspars | Thanks for all of your work on this.
I'm still unsure how/if I can recover some old parts. I do have something stored in various /detached/ folders.
My current plan:
1) Backup the data I have now into a table partitioned on a non-UUID key.
2) Downgrade clickhouse-server.
3) Hopefully the previous clickho... | 2021-06-10T08:07:44 | 2021-06-10T08:07:44 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,437,472 | 24,885 | mergify[bot] | **Command `update`: success**
> **Branch has been successfully updated**
>
| 2021-06-09T06:56:20 | 2021-06-09T06:56:20 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,665,581 | 24,778 | shacuros | Similar problem occurs when using FINAL Keyword on query time:
```
CREATE TABLE ProjTest2
(
a_int UInt8,
b_int UInt16,
PROJECTION prj1 (SELECT a_int, max(b_int) AS max_b, count(*) AS count_total GROUP BY a_int)
) ENGINE=ReplacingMergeTree ORDER BY (a_int, b_int);
INSERT INTO ProjTest2
SELECT *
FROM gener... | 2021-06-09T12:49:05 | 2021-06-09T12:49:05 | {} | NONE |
ClickHouse | ClickHouse | 857,713,125 | 25,062 | anneji-dev | ```sql
SELECT
sum(segment_res) AS segment_total,
sum(send_res) AS send_total
FROM
(
SELECT
segmentLengthSum(Start, End) AS segment_res,
sum(SendSize) AS send_res
FROM quefang.ck_tvideo_hot_rate_calculate_all
WHERE (Host = 'v11.douyinvod.com') AND ((Gnow >= '2021-05-25 00:00... | 2021-06-09T13:52:30 | 2021-06-09T13:52:30 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,720,709 | 25,128 | qoega | Incorporates changes from #25113 | 2021-06-09T14:01:51 | 2021-06-09T14:01:51 | {} | MEMBER |
ClickHouse | ClickHouse | 857,837,263 | 23,047 | tavplubix | > @tavplubix Can you include it into 21.3? I've caught this problem for 21.3.11 version. Many thanks
The problem appeared in 21.4 after 3c0f5a57ec6506b18636a1e8137325c800960ea5 was merged. Probably you caught another problem. Could you please create issue with detailed bug report? | 2021-06-09T16:10:19 | 2021-06-09T16:10:19 | {} | MEMBER |
ClickHouse | ClickHouse | 858,125,336 | 25,148 | nikitamikhaylov | Please provide any paper where you took there formulas for reference. | 2021-06-09T21:49:48 | 2021-06-09T21:49:48 | {} | MEMBER |
ClickHouse | ClickHouse | 858,142,920 | 24,318 | alexey-milovidov | https://github.com/ClickHouse/ClickHouse/pull/25149 | 2021-06-09T22:28:07 | 2021-06-09T22:28:07 | {} | MEMBER |
ClickHouse | ClickHouse | 858,226,213 | 25,058 | zcw5116 | > @sherrychenzhang Are there any other memory heavy operations?:
> ORDER BY, DISTINCT, IN subquery, JOIN, etc...
Received exception from server (version 19.5.3):
DB::Exception: Memory limit (for query) exceeded: would use 99.03 GiB (attempt to allocate
chunk of 8589934592 bytes), maximum: 93.13 GiB.
His error ... | 2021-06-10T02:13:41 | 2021-06-10T02:13:41 | {} | NONE |
ClickHouse | ClickHouse | 858,229,903 | 25,015 | alexey-milovidov | TODO:
- make IAggregateFunction intrusive_ptr instead of enable_shared_from_this;
- move almost every aggregate function to .cpp and remove header files;
| 2021-06-10T02:24:53 | 2021-06-10T02:24:53 | {} | MEMBER |
ClickHouse | ClickHouse | 858,256,396 | 25,109 | l19891223j | > Clickhouse无法访问他刚刚创建的zookeeper中的节点。
>
> 检查zookeeper配置和zookeeper问题/断开连接，可能是jute.maxbuffer
thanks！
I think it's caused by dirty data in zookeeper, because I've re-built a high version of zookeeper 3.6.3, and then creating a distributed table is OK | 2021-06-10T03:43:31 | 2021-06-10T03:43:31 | {} | NONE |
ClickHouse | ClickHouse | 858,421,759 | 25,070 | KochetovNicolai | You can just downgrade, and then run `ALTER TABLE mydb.counts ATTACh PART '...'` for every part or `ALTER TABLE mydb.counts ATTACH PARTITION ID '...'` for every partition in `/detached`.
Or even move parts from `/detached` back to data dir, if their name does not start with `ignored_` or `broken_` or `unexpected_` (... | 2021-06-10T08:25:41 | 2021-06-10T08:25:41 | {} | MEMBER |
ClickHouse | ClickHouse | 857,465,061 | 19,970 | etah000 | I will check the fork. think you for the message. | 2021-06-09T07:40:03 | 2021-06-09T07:40:03 | {
"+1": 2
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,872,482 | 24,458 | sevirov | @traceon Hi. I found this translation in several sources (bind DN -> DN подключения). I fixed it. Please, review again. | 2021-06-09T17:02:07 | 2021-06-09T17:02:07 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,127,754 | 25,148 | alexey-milovidov | Link to Wikipedia is also Ok. | 2021-06-09T21:54:37 | 2021-06-09T21:54:37 | {} | MEMBER |
ClickHouse | ClickHouse | 858,322,926 | 25,052 | stasDomb | Also I tried to change the settings **receive_timeout** and **send_timeout**. I increased them to 1000 sec. And I was surprised when I saw that it didn't help | 2021-06-10T05:45:24 | 2021-06-10T05:45:24 | {} | NONE |
ClickHouse | ClickHouse | 858,334,329 | 21,267 | filimonov | No failures related to the change. | 2021-06-10T06:06:20 | 2021-06-10T06:06:40 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,436,912 | 25,131 | KochetovNicolai | Error `Too many optimizations applied to query plan.` is just a check that prevent doing to many optimization steps for query plan (potentially, infinite). When there are 55668, mutations, we try to merge it together and build one common query plan. It will have at least as many steps, so limit 1000 can be not enough. ... | 2021-06-10T08:47:00 | 2021-06-10T08:47:00 | {} | MEMBER |
ClickHouse | ClickHouse | 857,732,597 | 23,047 | r3b-fish | @tavplubix Can you include it into 21.3? I've caught this problem for 21.3.11 version. Many thanks | 2021-06-09T14:16:12 | 2021-06-09T14:16:12 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,804,119 | 24,778 | amosbird | > As seen count() is way to small when using final on query time
Hmm, the result of `select final` is indeed strange. I'll take a look. But in general we should not use projections in ReplacingMergeTree for now | 2021-06-09T15:30:24 | 2021-06-09T15:30:24 | {} | COLLABORATOR |
ClickHouse | ClickHouse | 858,135,885 | 25,061 | alexey-milovidov | Why not? | 2021-06-09T22:11:52 | 2021-06-09T22:11:52 | {} | MEMBER |
ClickHouse | ClickHouse | 858,143,304 | 24,318 | alexey-milovidov | Maybe need to check the most affected case when hash table size after all resizes is 64 MB
... and aggregation is parallel - to avoid fitting the working set in L3 cache. | 2021-06-09T22:29:07 | 2021-06-09T22:39:23 | {} | MEMBER |
ClickHouse | ClickHouse | 858,332,042 | 25,122 | msaf1980 | Detect POCO headers is ugly in this PR, but not found in existing CMake scenarious. | 2021-06-10T06:02:08 | 2021-06-10T06:02:08 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,382,357 | 23,183 | ElapsedSoul | > @roygbip Could you help me debugging this issue? It happens on specific cloud instance and on specific OS where I cannot obtain access. Maybe you can create a small temporary VM, temporary ssh keypair and send the address along with keypair to [clickhouse-feedback@yandex-team.ru](mailto:clickhouse-feedback@yandex-tea... | 2021-06-10T07:25:48 | 2021-06-10T07:33:57 | {} | NONE |
ClickHouse | ClickHouse | 857,664,433 | 25,103 | alexey-milovidov | Performance test is Ok. | 2021-06-09T12:47:11 | 2021-06-09T12:47:11 | {} | MEMBER |
ClickHouse | ClickHouse | 857,773,093 | 25,131 | volfco | I enabled debugging, and the following message showed up:
```
Not enough idle threads to apply mutations at the moment. See settings 'number_of_free_entries_in_pool_to_execute_mutation' and 'background_pool_size'
``` | 2021-06-09T15:02:21 | 2021-06-09T15:02:21 | {} | NONE |
ClickHouse | ClickHouse | 857,788,271 | 25,131 | filimonov | Just do
```
Kill mutations where 1
```
After that start it once again on a proper way | 2021-06-09T15:11:33 | 2021-06-09T15:11:33 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,390,783 | 16,503 | excitoon | About table-wide thread pools, it may be not a good idea because it would spoil parallelism in uploading different parts, one part may wait another, and typically these settings are for situations when we upload something in not very reliable network conditions, and not so frequently. | 2021-06-10T07:39:57 | 2021-06-10T07:39:57 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,639,715 | 25,062 | anneji-dev | When the amount of data is large, it is estimated that it will reach 20 billion，this issue reproduce consistenly，but when the amount of data is small is normal. | 2021-06-09T12:09:13 | 2021-06-09T12:09:13 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,805,754 | 24,404 | nvartolomei | @alexey-milovidov help me understand why this is related to this PR. It doesn't seem to me. Let me know how can I help getting this merged faster :) | 2021-06-09T15:32:35 | 2021-06-09T15:32:35 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,245,823 | 23,515 | rdbuf | No, the problem was non-existent when we were querying the partial table.
Sorry, I can't share the data because currently the minimal reproducible example is of several terabytes. | 2021-06-10T03:10:56 | 2021-06-10T03:10:56 | {} | NONE |
ClickHouse | ClickHouse | 857,757,517 | 25,120 | filimonov | > You can try like this:
>
```
select *
from table
where name in ('AAA','BBB','CCC')
ORDER BY name
```
| 2021-06-09T14:44:43 | 2021-06-09T14:44:43 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,790,039 | 25,131 | volfco | I have done that, I'm just bringing this error to your attention as it looks like a bug. | 2021-06-09T15:13:42 | 2021-06-09T15:13:42 | {} | NONE |
ClickHouse | ClickHouse | 858,165,603 | 25,069 | alexey-milovidov | Maybe introduce this field just in case?
BTW does s3 metadata have versioning or extensibility? | 2021-06-09T23:27:59 | 2021-06-09T23:28:10 | {} | MEMBER |
ClickHouse | ClickHouse | 858,180,701 | 24,537 | alexey-milovidov | Superseded by https://github.com/ClickHouse/ClickHouse/pull/25148 | 2021-06-10T00:05:35 | 2021-06-10T00:05:35 | {} | MEMBER |
ClickHouse | ClickHouse | 858,224,828 | 25,058 | alexey-milovidov | @sherrychenzhang Are there any other memory heavy operations?:
ORDER BY, DISTINCT, IN subquery, JOIN, etc... | 2021-06-10T02:09:19 | 2021-06-10T02:09:26 | {} | MEMBER |
ClickHouse | ClickHouse | 857,474,425 | 24,081 | kasnet | I also faced this problem.I found that the reason is view in mysql. | 2021-06-09T07:54:40 | 2021-06-09T07:55:01 | {} | NONE |
ClickHouse | ClickHouse | 857,479,753 | 25,058 | sherrychenzhang | set max_bytes_before_external_group_by 10000000000 1
still error? not big enough?
Received exception from server (version 19.5.3):
DB::Exception: Memory limit (for query) exceeded: would use 99.03 GiB (attempt to allocate
chunk of 8589934592 bytes), maximum: 93.13 GiB.
| 2021-06-09T08:02:37 | 2021-06-09T08:03:20 | {} | NONE |
ClickHouse | ClickHouse | 856,972,027 | 25,070 | KochetovNicolai | Repro:
21.5.6.6
```
create table tab (id UUID, value UInt32) engine = MergeTree PARTITION BY id order by tuple();
insert into tab values ('00000000-0000-0000-0000-000000000000', 1), ('00000000-0000-0000-0000-000000000000', 2), ('61f0c404-5cb3-11e7-907b-a6006ad3dba0', 1), ('61f0c404-5cb3-11e7-907b-a6006ad3dba0', 2... | 2021-06-08T17:51:56 | 2021-06-09T13:03:21 | {
"+1": 1
} | MEMBER |
ClickHouse | ClickHouse | 858,226,115 | 25,129 | alexey-milovidov | @nikitamikhaylov It looks unexpected, could you please take a look? | 2021-06-10T02:13:24 | 2021-06-10T02:13:24 | {} | MEMBER |
ClickHouse | ClickHouse | 858,372,205 | 23,976 | excitoon | @alexey-milovidov Rebased it. | 2021-06-10T07:08:34 | 2021-06-10T07:08:34 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,386,379 | 23,183 | ElapsedSoul | @roygbip @alexey-milovidov
My servers cpu arch is Phytium,
I build from x86 cross is ok for UOS but not for Kylin v10 sp1,
[my issuse](crashed on kylin os with arm #19028) | 2021-06-10T07:32:25 | 2021-06-10T07:32:25 | {} | NONE |
ClickHouse | ClickHouse | 858,423,094 | 25,070 | larspars | Thanks, Nicolai, will try that! | 2021-06-10T08:27:29 | 2021-06-10T08:27:29 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,475,299 | 25,079 | alesapin | @Mergifyio update | 2021-06-09T07:55:54 | 2021-06-09T07:55:54 | {
"+1": 1
} | MEMBER |
ClickHouse | ClickHouse | 857,548,804 | 25,071 | tavplubix | > Thanks Denny for the reply. By the way, is there any process on the light delete and update implimentation?
See #19627 | 2021-06-09T09:41:29 | 2021-06-09T09:41:29 | {} | MEMBER |
ClickHouse | ClickHouse | 857,811,642 | 25,131 | volfco | Funny enough, running kill mutations results in this:
```
Received exception from server (version 21.6.3):
Code: 241. DB::Exception: Received from localhost:9000. DB::Exception: Memory limit (total) exceeded: would use 42.26 GiB (attempt to allocate chunk of 4198176 bytes), maximum: 42.26 GiB.
``` | 2021-06-09T15:40:25 | 2021-06-09T15:40:25 | {} | NONE |
ClickHouse | ClickHouse | 857,850,833 | 25,103 | tavplubix | > @tavplubix Need to check 00993_system_parts_race_condition_drop_zookeeper
Seems like `StorageReplicatedMergeTree::shutdown()` hung somewhere between `part_moves_between_shards_orchestrator.shutdown()` and `clearOldPartsFromFilesystem(true);`:
```
$ zgrep -Fa "2d08b532-f80b-47c4-995e-164075c57caa" clickhouse-serv... | 2021-06-09T16:29:42 | 2021-06-09T16:29:42 | {} | MEMBER |
ClickHouse | ClickHouse | 857,402,490 | 25,108 | AKMCC-hub | > > 在块中找不到列 createTime
>
> 如果该列在那里 - 请共享表架构并运行查询。
>
> 否则我们无法帮助您，票将被关闭。
db :) desc student_login_log
DESCRIBE TABLE student_login_log
Query id: 1aa306f4-234b-4164-adeb-117ded8dd02f
┌─name────────┬─type─────────────┬─default_type─┬─default_expression─┬─comment─┬─codec_expression─┬─ttl_expression─┐
│ id... | 2021-06-09T05:58:15 | 2021-06-09T05:58:15 | {} | NONE |
ClickHouse | ClickHouse | 857,581,122 | 24,941 | mergify[bot] | **Command `update`: success**
> **Branch has been successfully updated**
>
| 2021-06-09T10:30:33 | 2021-06-09T10:30:33 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,735,081 | 24,585 | nvartolomei | At this point I'm quite happy with the tests and that it works.
cc @xjewer @alesapin please review.
There are 2 open questions that need attention. If we agree on these I think this will be ready to be merged. This is the best I could come with taking into account time constraints.
The questions are related to... | 2021-06-09T14:19:15 | 2021-06-09T14:19:15 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,882,415 | 24,458 | traceon | @sevirov thanks, looks great. | 2021-06-09T17:17:29 | 2021-06-09T17:17:29 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,180,540 | 25,148 | alexey-milovidov | Please address review comments from here: https://github.com/ClickHouse/ClickHouse/pull/24537 | 2021-06-10T00:05:18 | 2021-06-10T00:05:18 | {} | MEMBER |
ClickHouse | ClickHouse | 858,195,566 | 25,086 | hbk-ronak | Thanks this works. I'm now able to run clickhouse client and clickhouse server. | 2021-06-10T00:45:02 | 2021-06-10T00:45:02 | {
"rocket": 1
} | NONE |
ClickHouse | ClickHouse | 858,224,364 | 25,058 | alexey-milovidov | I can check if the memory usage is normal if you provide some datasets to test. | 2021-06-10T02:08:14 | 2021-06-10T02:08:14 | {} | MEMBER |
ClickHouse | ClickHouse | 857,686,959 | 25,111 | alesapin | `test_storage_kafka/test.py::test_kafka_virtual_columns`
`test_storage_kafka/test.py::test_kafka_virtual_columns_with_materialized_view`
nasty tests.... | 2021-06-09T13:18:34 | 2021-06-09T13:18:34 | {} | MEMBER |
ClickHouse | ClickHouse | 858,141,563 | 24,318 | alexey-milovidov | @kitaisreal has checked this proposal and found that it is not beneficial at all. | 2021-06-09T22:24:51 | 2021-06-09T22:26:48 | {} | MEMBER |
ClickHouse | ClickHouse | 858,157,474 | 25,067 | alexey-milovidov | @tavplubix said that he has the required function somewhere... | 2021-06-09T23:05:37 | 2021-06-09T23:05:37 | {} | MEMBER |
ClickHouse | ClickHouse | 858,166,186 | 25,070 | alexey-milovidov | It is for parts with level more than zero.
Parts with level zero (just inserted parts) were deleted.
| 2021-06-09T23:29:27 | 2021-06-09T23:29:27 | {} | MEMBER |
ClickHouse | ClickHouse | 858,373,254 | 23,051 | excitoon | Failed tests are unrelated. | 2021-06-10T07:10:19 | 2021-06-10T07:10:19 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,597,498 | 25,110 | filimonov | /cc @andyyzh @sundy-li
https://github.com/ClickHouse/ClickHouse/pull/17858 | 2021-06-09T10:57:27 | 2021-06-09T10:57:27 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,697,294 | 25,120 | shacuros | You can try like this:
```
select *
from table
where name in ('AAA','BBB','CCC')
ORDER BY indexOf(['AAA','BBB','CCC'], name)
``` | 2021-06-09T13:32:02 | 2021-06-09T13:32:02 | {
"+1": 1
} | NONE |
ClickHouse | ClickHouse | 857,789,090 | 17,268 | traceon | > The protocol forbids autodetection:
In case when the proxy IPs/networks are pre-configured, the `autodetection` is safe, since the proxy is "trusted". | 2021-06-09T15:12:34 | 2021-06-09T15:12:34 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,873,495 | 25,070 | nvartolomei | @alexey-milovidov
1. shouldn't deletion be prevented here by incrementing `suspicious_broken_parts`?
2. should there be a check on broken parts per partition ratio? It is not unheard of to have 1 part per partition intentionally after running optimize final. A bit of a problem here as we don't even know the partit... | 2021-06-09T17:03:49 | 2021-06-09T17:05:57 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,041,551 | 25,086 | hbk-ronak | Hi,
FYI the CPU changed from Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz to AMD Phenom(tm) II X2 B53 Processor
As suggested I built with clang-12 and the build was successful. But when I tried to run
```ls -l programs/clickhouse```
I get the following message (when run from $HOME or from $HOME/packages/ClickHo... | 2021-06-09T19:41:18 | 2021-06-09T22:30:58 | {} | NONE |
ClickHouse | ClickHouse | 858,225,688 | 25,131 | alexey-milovidov | @KochetovNicolai @alesapin You may found it interesting.
Maybe lower some threshold on how many mutations are merged together? | 2021-06-10T02:11:59 | 2021-06-10T02:12:08 | {} | MEMBER |
ClickHouse | ClickHouse | 858,257,359 | 25,120 | deepprakash345 | @shacuros , can you please give me some input on https://github.com/ClickHouse/ClickHouse/issues/25121. | 2021-06-10T03:46:48 | 2021-06-10T03:46:48 | {} | NONE |
ClickHouse | ClickHouse | 857,377,761 | 25,108 | filimonov | > Not found column createTime in block
If the column is there - please share table schema and query you run.
Otherwise we can't help you and ticket will be closed. | 2021-06-09T05:09:09 | 2021-06-09T05:09:09 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,481,225 | 23,656 | mergify[bot] | **Command `update`: success**
> **Branch has been successfully updated**
>
| 2021-06-09T08:04:49 | 2021-06-09T08:04:49 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,663,988 | 25,062 | anneji-dev | When sql runs to 99%,this issue reproduce consistenly. | 2021-06-09T12:46:29 | 2021-06-09T12:46:29 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,826,802 | 21,267 | filimonov | test_kafka_virtual_columns - will fix in another PR (https://github.com/ClickHouse/ClickHouse/pull/25111) | 2021-06-09T15:56:10 | 2021-06-09T15:56:10 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,149,146 | 25,086 | alexey-milovidov | It is in your build directory, usually `build/programs/clickhouse`.
Nevertheless, you can find it:
`find . -name clickhouse -type f -executable` | 2021-06-09T22:44:05 | 2021-06-09T22:44:05 | {} | MEMBER |
ClickHouse | ClickHouse | 858,158,078 | 25,022 | alexey-milovidov | @Mergifyio update | 2021-06-09T23:07:04 | 2021-06-09T23:07:04 | {
"+1": 1
} | MEMBER |
ClickHouse | ClickHouse | 858,257,087 | 25,131 | volfco | Playing around in a testing database, it seems like once
```
2021.06.10 03:13:49.425199 [ 1993100 ] {} <Debug> default.media: Not enough idle threads to apply mutations at the moment. See settings 'number_of_free_entries_in_pool_to_execute_mutation' and 'background_pool_size'
```
shows up in the logs, the mutation... | 2021-06-10T03:45:51 | 2021-06-10T03:45:51 | {} | NONE |
ClickHouse | ClickHouse | 857,411,684 | 25,058 | zcw5116 | > If you set `max_bytes_before_external_group_by` to a very low value, large number of temporary files will be generated, and (paradoxically) the amount of memory needed to merge these temporary files and finish the query will be even higher.
Good reply, thank you very much. | 2021-06-09T06:14:20 | 2021-06-09T06:14:20 | {} | NONE |
ClickHouse | ClickHouse | 857,475,411 | 25,079 | mergify[bot] | **Command `update`: success**
> **Branch has been successfully updated**
>
| 2021-06-09T07:56:03 | 2021-06-09T07:56:03 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,580,467 | 24,941 | filimonov | Missed some small api changes introduced in https://github.com/ClickHouse/ClickHouse/commit/872e36c207f5ed96f97883cb974038474160c84d#diff-8129a3b04ff2293c2d89b35395be9ef49918cdafd4420a745d05733b00979646L86-R100 and merged just before that pr | 2021-06-09T10:29:30 | 2021-06-09T10:29:30 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,591,878 | 25,118 | siradjev | Additional info.
problem won't happen if GLobal WITH is not used (enable_global_with_statement=0). Backward incompatible change not mentioned in documentation/changelog #18705.
Problem won't happen if explicit prewhere or implicit move to prewhere is not used. | 2021-06-09T10:48:08 | 2021-06-09T10:48:08 | {} | NONE |
ClickHouse | ClickHouse | 857,595,062 | 25,110 | filimonov | It is expected to be slower, but not sure why the difference is so big (10-12 times). | 2021-06-09T10:53:21 | 2021-06-09T10:53:32 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,675,084 | 25,125 | vzakaznikov | @alexey-milovidov, let's disable extended precision data types tests for now until they are fixed. | 2021-06-09T13:02:38 | 2021-06-09T13:02:38 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 857,886,437 | 25,069 | Jokser | @yuzhichang Agree, it can be. But it affects only Log* engines. At the moment there is no backup mechanism for them.
This issue can be solved with introducing an order field in S3 object metadata which determines order of S3 object in corresponding metadata file. | 2021-06-09T17:22:44 | 2021-06-09T17:22:44 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,111,977 | 24,941 | filimonov | No related failures. | 2021-06-09T21:23:12 | 2021-06-09T21:23:12 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 858,212,031 | 15,352 | zhoupengbo | this is my fault, thank you all ! Sorry for not replying！@filimonov @alexey-milovidov | 2021-06-10T01:32:22 | 2021-06-10T01:32:22 | {
"hooray": 1
} | NONE |
ClickHouse | ClickHouse | 858,374,767 | 23,183 | ElapsedSoul | > but our old clickhouse version 20.3.18.186 runing correct:
@roygbip This version run on kylin v10 too?
I'am afraid, It's the OS's case. | 2021-06-10T07:13:00 | 2021-06-10T07:26:22 | {} | NONE |
ClickHouse | ClickHouse | 865,677,006 | 25,582 | alexey-milovidov | What is the scenario? Why this feature is a candidate for backporting? | 2021-06-22T07:39:47 | 2021-06-22T07:39:47 | {} | MEMBER |
ClickHouse | ClickHouse | 865,685,101 | 25,525 | alesapin | 
ヽ(‘ー`)ノ | 2021-06-22T07:51:59 | 2021-06-22T07:51:59 | {
"hooray": 1
} | MEMBER |
ClickHouse | ClickHouse | 846,357,846 | 24,319 | azat | >Functional stateless tests (memory) — fail: 1, passed: 3052, skipped: 13
>Functional stateless tests (release) — fail: 1, passed: 3065
`00753_system_columns_and_system_tables` - #24411
>Functional stateless tests (thread) — fail: 2, passed: 3038, skipped: 26
>Functional stateless tests (ubsan) — fail: 1, passe... | 2021-05-22T06:13:02 | 2021-06-22T12:37:24 | {} | MEMBER |
ClickHouse | ClickHouse | 865,886,512 | 16,726 | dl-lim | Here's my logs from Clickhouse when trying to use MaterializeMySql with MariaDB:
```
Code: 537. DB::Exception: Received from localhost:9000.
DB::Exception: Illegal MySQL variables,
the MaterializeMySQL engine requires
log_bin_use_v1_row_events='OFF',
default_authentication_plugin='mysql_native_password'.
```
... | 2021-06-22T11:03:23 | 2021-06-22T16:37:23 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.