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 | 782,914,784 | 20,996 | azat | > If it cannot obtain stack trace - usually it cannot do it for all threads - so it will simply write ~1000 useless messages.
Actually it will not fail for all threads, look:
```
$ pigz -cd clickhouse-server\ \(5\).log.gz | fgrep -a 034edc75-91b1-4eba-a639-52389b6eaa6e
2021.02.20 12:14:53.707097 [ 74226 ] {034e... | 2021-02-21T19:49:34 | 2021-02-21T19:49:34 | {} | MEMBER |
ClickHouse | ClickHouse | 782,870,912 | 12,571 | alexey-milovidov | The reason is that full table (with both `id` and `name`) is required to be fetched in memory.
I can confirm what @4ertus2 has already written.
| 2021-02-21T14:57:16 | 2021-02-21T14:57:16 | {} | MEMBER |
ClickHouse | ClickHouse | 782,886,148 | 20,585 | alesapin | For some reason, it takes more than a minute to start from the log with 854461 entries.... A similar amount of records on my machine takes about 10-20 seconds even with address sanitizer...
Same with memory sanitizer:
```
2021.02.21 19:35:21.172708 [ 732768 ] {} <Information> RaftInstance: [PRIORITY] decay, target... | 2021-02-21T16:40:21 | 2021-02-21T16:44:32 | {} | MEMBER |
ClickHouse | ClickHouse | 782,908,419 | 20,921 | alexey-milovidov | Not correctly merged. | 2021-02-21T19:05:39 | 2021-02-21T19:05:39 | {} | MEMBER |
ClickHouse | ClickHouse | 782,908,764 | 20,902 | alexey-milovidov | Does not really matter. | 2021-02-21T19:07:50 | 2021-02-21T19:07:50 | {} | MEMBER |
ClickHouse | ClickHouse | 782,911,879 | 19,233 | alexey-milovidov | The bug introduced here: #9968 | 2021-02-21T19:29:24 | 2021-02-21T19:29:24 | {} | MEMBER |
ClickHouse | ClickHouse | 782,912,244 | 20,100 | alexey-milovidov | Duplicate #19914 | 2021-02-21T19:31:39 | 2021-02-21T19:31:39 | {} | MEMBER |
ClickHouse | ClickHouse | 782,830,375 | 20,479 | alexey-milovidov | If I remember correctly, it does not compare Float32 and Float64 correctly. | 2021-02-21T09:56:04 | 2021-02-21T09:56:04 | {} | MEMBER |
ClickHouse | ClickHouse | 782,907,527 | 21,012 | alexey-milovidov | Not relevant for this release. | 2021-02-21T19:00:11 | 2021-02-21T19:00:11 | {} | MEMBER |
ClickHouse | ClickHouse | 782,907,961 | 20,966 | alexey-milovidov | Not correctly merged. | 2021-02-21T19:02:46 | 2021-02-21T19:02:46 | {} | MEMBER |
ClickHouse | ClickHouse | 782,908,949 | 20,824 | alexey-milovidov | Not important enough. | 2021-02-21T19:09:18 | 2021-02-21T19:09:18 | {} | MEMBER |
ClickHouse | ClickHouse | 782,909,841 | 21,043 | alexey-milovidov | Better not to backport to avoid potential issues. | 2021-02-21T19:15:08 | 2021-02-21T19:15:08 | {} | MEMBER |
ClickHouse | ClickHouse | 783,058,316 | 21,054 | den-crane | Normal database Atomic behavior.
Duplicate https://github.com/ClickHouse/ClickHouse/issues/20243
https://github.com/ClickHouse/ClickHouse/issues/12135
https://github.com/ClickHouse/ClickHouse/issues/12135#issuecomment-653932557 | 2021-02-22T03:55:47 | 2021-02-22T03:57:33 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,256,338 | 12,454 | alexey-milovidov | @asafcombo How exactly does it reproduce? Could you please create a new issue? | 2021-02-22T10:06:39 | 2021-02-22T10:06:39 | {} | MEMBER |
ClickHouse | ClickHouse | 783,302,120 | 21,058 | wangzhen11aaa | Use command
`ld -v`
show the linker version. | 2021-02-22T11:19:45 | 2021-02-22T11:19:45 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,830,847 | 19,457 | alexey-milovidov | Fixed in #20206. | 2021-02-21T10:00:18 | 2021-02-21T10:00:18 | {} | MEMBER |
ClickHouse | ClickHouse | 782,853,917 | 20,964 | alexey-milovidov | Does the issue reproduce on recent releases? The current stable release is 21.2. | 2021-02-21T12:56:05 | 2021-02-21T12:56:05 | {} | MEMBER |
ClickHouse | ClickHouse | 782,897,610 | 7,787 | alexey-milovidov | This task is completely solved: both parsing and formatting of named Tuples work for now. | 2021-02-21T17:57:06 | 2021-02-21T17:57:06 | {
"hooray": 1
} | MEMBER |
ClickHouse | ClickHouse | 782,899,635 | 21,041 | alexey-milovidov | Does MongoDB server actually receive the query?
Maybe full scan query is just too hard and takes too long to process? | 2021-02-21T18:09:07 | 2021-02-21T18:09:07 | {} | MEMBER |
ClickHouse | ClickHouse | 782,907,649 | 21,000 | alexey-milovidov | Not relevant for this release. | 2021-02-21T19:00:57 | 2021-02-21T19:00:57 | {} | MEMBER |
ClickHouse | ClickHouse | 782,912,970 | 21,034 | azat | Yes, my bad (strange there were no tests), addressed here - #21050 | 2021-02-21T19:37:10 | 2021-02-21T19:37:10 | {} | MEMBER |
ClickHouse | ClickHouse | 783,359,481 | 15,572 | filimonov | Простите тикет кажется потерялся.
> Connection reset by peer
Это ошибка соединения. Проверьте адрес / порт / файерволл / ssl и прочие настройки соединения. | 2021-02-22T13:05:05 | 2021-02-22T13:05:05 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,399,495 | 9,781 | alexey-milovidov | It's working, I will add a test:
```
SELECT toDate(toDateTime64(today(), 0, 'UTC')) = toDate(toDateTime(today(), 'UTC'))
Query id: 455e479d-16fc-44ca-88dc-6de157360d3f
┌─equals(toDate(toDateTime64(today(), 0, 'UTC')), toDate(toDateTime(today(), 'UTC')))─┐
│ ... | 2021-02-22T14:06:15 | 2021-02-22T14:06:15 | {} | MEMBER |
ClickHouse | ClickHouse | 782,836,214 | 13,194 | alexey-milovidov | @den-crane It works in inconsistent fashion:
```
milovidov-desktop :) CREATE TEMPORARY TABLE t (x DateTime64(3))
CREATE TEMPORARY TABLE t
(
`x` DateTime64(3)
)
Query id: bd64042b-f59a-4239-98eb-17cdbb8c650d
Ok.
0 rows in set. Elapsed: 0.001 sec.
milovidov-desktop :) INSERT INTO t VALUES (1111... | 2021-02-21T10:43:04 | 2021-02-21T10:43:04 | {} | MEMBER |
ClickHouse | ClickHouse | 782,847,718 | 21,023 | alexey-milovidov | Requires #21022. | 2021-02-21T12:10:09 | 2021-02-21T12:10:09 | {} | MEMBER |
ClickHouse | ClickHouse | 782,909,822 | 21,044 | alexey-milovidov | Better not to backport to avoid potential issues. | 2021-02-21T19:15:03 | 2021-02-21T19:15:03 | {} | MEMBER |
ClickHouse | ClickHouse | 782,913,030 | 21,034 | azat | Cc: @Enmk | 2021-02-21T19:37:39 | 2021-02-21T19:37:39 | {} | MEMBER |
ClickHouse | ClickHouse | 782,915,438 | 13,194 | den-crane | @alexey-milovidov
I don't see consistency.
```
CREATE TEMPORARY TABLE t (x DateTime64(3));
INSERT INTO t VALUES (1111111111222);
ok
INSERT INTO t Format TSV 1111111111222
Error on processing query 'INSERT INTO t Format TSV 1111111111222':
Code: 27, e.displayText() = DB::ParsingException: Cannot parse inp... | 2021-02-21T19:54:26 | 2021-02-21T19:55:23 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,261,372 | 20,219 | mdianjun | @yiguolei
> But it could not deal with ReplacingMergeTree Engine.
Could you explain this reason more detailed? 3Q. | 2021-02-22T10:14:39 | 2021-02-22T10:14:46 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,379,282 | 11,461 | filimonov | @ortho your issue looks completely different. Please open the new one. | 2021-02-22T13:37:09 | 2021-02-22T13:37:09 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,396,589 | 17,079 | alexey-milovidov | It's unclear how we should support leap seconds - what the behaviour will be.
We are using unix timespamp internally - it is already aware of the leap seconds and Linux handles it in a way that some value of unix timespamp is either skipped or stretched to two seconds, so every minute interval makes a range of 60 ti... | 2021-02-22T14:01:40 | 2021-02-22T14:01:40 | {} | MEMBER |
ClickHouse | ClickHouse | 782,830,500 | 19,897 | alexey-milovidov | @funemy Hi! How is it going - maybe it's a good time to continue evaluation? | 2021-02-21T09:57:06 | 2021-02-21T09:57:06 | {} | MEMBER |
ClickHouse | ClickHouse | 782,831,545 | 17,939 | alexey-milovidov | @akuzm FYI this is the case for window functions. | 2021-02-21T10:05:19 | 2021-02-21T10:05:19 | {} | MEMBER |
ClickHouse | ClickHouse | 782,834,967 | 19,302 | alexey-milovidov | Duplicate. Fixed. | 2021-02-21T10:33:21 | 2021-02-21T10:33:21 | {} | MEMBER |
ClickHouse | ClickHouse | 782,870,050 | 20,217 | vzakaznikov | @tavplubix, I've added examples. | 2021-02-21T14:50:51 | 2021-02-21T14:50:51 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,870,493 | 19,570 | anmolarora | I've made changes for `system.parts` & `system.parts_columns` https://github.com/ClickHouse/ClickHouse/pull/21035
I'll make similar change for other system tables after this change is approved. | 2021-02-21T14:54:20 | 2021-02-21T14:54:20 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,890,409 | 21,022 | azat | >Performance — 12 slower, 28 unstable
Passed | 2021-02-21T17:09:58 | 2021-02-21T17:09:58 | {} | MEMBER |
ClickHouse | ClickHouse | 783,260,293 | 21,053 | alexey-milovidov | Performance test Ok. | 2021-02-22T10:13:01 | 2021-02-22T10:13:01 | {} | MEMBER |
ClickHouse | ClickHouse | 783,335,236 | 20,087 | ervikrant06 | @Felixoid Sorry to tag you I still can't understand why the old dates are not reducing the retention of metrics. Earlier it was mentioned that avg may not give right results hence I switched to any. is this could be the reason?
~~~
graphite_rollup ^gpfs\\.gpfs2graphite.* any 604800 600 4 0 ['sh... | 2021-02-22T12:20:22 | 2021-02-22T12:20:22 | {} | NONE |
ClickHouse | ClickHouse | 782,849,496 | 20,202 | zhaojintaozhao | > I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
>
> Changelog category (leave one):
>
> * New Feature
>
> Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
>
> Add projection support for MergeTree* tables.
>
> Detaile... | 2021-02-21T12:24:02 | 2021-02-21T12:24:02 | {} | NONE |
ClickHouse | ClickHouse | 782,852,670 | 21,018 | alexey-milovidov | Does it reproduce on version 21.2? | 2021-02-21T12:48:15 | 2021-02-21T12:48:15 | {} | MEMBER |
ClickHouse | ClickHouse | 782,907,518 | 21,013 | alexey-milovidov | Not relevant for this release. | 2021-02-21T19:00:08 | 2021-02-21T19:00:08 | {} | MEMBER |
ClickHouse | ClickHouse | 782,909,845 | 21,042 | alexey-milovidov | Better not to backport to avoid potential issues. | 2021-02-21T19:15:11 | 2021-02-21T19:15:11 | {} | MEMBER |
ClickHouse | ClickHouse | 783,127,615 | 21,054 | cyberhuman | I think it's because ClickHouse tries to drop metadata from the main ZK, not from auxiliary one:
https://github.com/ClickHouse/ClickHouse/blob/2a36d6cb55af14b0dcf87c1b806afbf5c7dec8be/src/Storages/StorageReplicatedMergeTree.cpp#L753 | 2021-02-22T06:37:06 | 2021-02-22T06:41:37 | {} | NONE |
ClickHouse | ClickHouse | 782,869,782 | 21,008 | peaksnail | It will read all partition if using partition by toYYYYMM(toDate(createDate/1000)),
Is there any way to speed up queries using storeId to query like
```
select ... from customer where storeId='xxx'
```
otherwise it will be slow when the data is big | 2021-02-21T14:48:40 | 2021-02-21T14:48:40 | {} | NONE |
ClickHouse | ClickHouse | 782,903,503 | 21,008 | den-crane | partition by toYYYYMM(toDate(createDate/1000))
order by (storeId, toDate(createDate/1000)) | 2021-02-21T18:31:45 | 2021-02-21T18:31:45 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,911,993 | 20,101 | alexey-milovidov | Fixed. | 2021-02-21T19:30:06 | 2021-02-21T19:30:06 | {} | MEMBER |
ClickHouse | ClickHouse | 782,834,509 | 19,376 | alexey-milovidov | Most likely will be fixed in #20479. | 2021-02-21T10:29:15 | 2021-02-21T10:29:15 | {} | MEMBER |
ClickHouse | ClickHouse | 782,843,295 | 11,819 | alexey-milovidov | @leosunli Does it help if you type
`ninja clickhouse`
instead of
`ninja`? | 2021-02-21T11:38:21 | 2021-02-21T11:38:21 | {} | MEMBER |
ClickHouse | ClickHouse | 782,870,110 | 12,571 | alexey-milovidov | This query requires a lot of RAM:
```
select q.id, p.id from testdb.xs q, testdb.xs p WHERE concat(p.name, '') = '';
```
And this query is working fine:
```
select q.id, p.id from testdb.xs q, testdb.xs p WHERE concat(q.name, '') = '';
```
| 2021-02-21T14:51:18 | 2021-02-21T14:51:18 | {} | MEMBER |
ClickHouse | ClickHouse | 782,870,722 | 19,897 | funemy | @alexey-milovidov Hi!
Thanks for the follow-up! Yes, we are very close to the next release, a release candidate should be available around next Tuesday.
I'll update you once it's published.
Sorry for being a bit slow here. As most of our main developers live in Texas and we just recovered from the winter storm l... | 2021-02-21T14:55:57 | 2021-02-21T14:55:57 | {
"hooray": 1
} | NONE |
ClickHouse | ClickHouse | 782,907,948 | 20,967 | alexey-milovidov | Not correctly merged. | 2021-02-21T19:02:41 | 2021-02-21T19:02:41 | {} | MEMBER |
ClickHouse | ClickHouse | 783,341,642 | 21,061 | amosbird | Same as dictionary. But the motivation is unclear. Is it to check whether Join table contains a given key? In that case, perhaps we need to provide `joinHas` similar to `dictHas`. | 2021-02-22T12:32:40 | 2021-02-22T12:32:40 | {} | COLLABORATOR |
ClickHouse | ClickHouse | 782,908,363 | 20,930 | alexey-milovidov | Not relevant for this release. | 2021-02-21T19:05:18 | 2021-02-21T19:05:18 | {} | MEMBER |
ClickHouse | ClickHouse | 782,908,870 | 20,911 | alexey-milovidov | Tests are not correctly merged. | 2021-02-21T19:08:38 | 2021-02-21T19:08:38 | {} | MEMBER |
ClickHouse | ClickHouse | 782,859,459 | 20,131 | alexey-milovidov | Unfortunately this PR did not fix the issue (see #20494) and also introduced a regression (see #21034). | 2021-02-21T13:36:50 | 2021-02-21T13:36:50 | {} | MEMBER |
ClickHouse | ClickHouse | 782,865,313 | 19,570 | anmolarora | Hi @alexey-milovidov, can you please assign this to me? | 2021-02-21T14:19:14 | 2021-02-21T14:19:14 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,907,536 | 21,010 | alexey-milovidov | Not relevant for this release. | 2021-02-21T19:00:13 | 2021-02-21T19:00:13 | {} | MEMBER |
ClickHouse | ClickHouse | 782,910,179 | 20,182 | alexey-milovidov | This has to be merged: #21009 | 2021-02-21T19:17:15 | 2021-02-21T19:17:15 | {} | MEMBER |
ClickHouse | ClickHouse | 782,921,428 | 13,194 | alexey-milovidov | @den-crane Yes, it is inconsistent:
> It works in inconsistent fashion | 2021-02-21T20:31:53 | 2021-02-21T20:31:53 | {} | MEMBER |
ClickHouse | ClickHouse | 782,989,453 | 21,029 | hexiaoting | > @hexiaoting This issue looks important.
>
> Fortunately, the Map data type is only available under experimental flag and is not suitable for production usages.
Sorry for the problems in my implementation. I will try to fix this. | 2021-02-22T02:07:37 | 2021-02-22T02:07:37 | {
"+1": 1
} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,064,463 | 21,054 | den-crane | 1. Why do you use Replicated Tables as temporary instead of MergeTree?
2. Why do you hardcode replica 0 , 1 ?
3 `show create database database_20201117` | 2021-02-22T04:16:06 | 2021-02-22T04:16:06 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,256,891 | 20,599 | alexey-milovidov | > Integration tests (thread) — fail: 1, passed: 1123, error: 0
Failed Kafka test - @filimonov | 2021-02-22T10:07:28 | 2021-02-22T10:07:28 | {} | MEMBER |
ClickHouse | ClickHouse | 783,352,848 | 18,563 | filimonov | @MaryamJFard
If you just compare the numbers from 2 tables consuming the same topic - why do you think one of table misses some data?
I would suspect first the other have some duplicates (duplicates are expected in some corner cases).
Without trace logs, I can't do anything with that issue. | 2021-02-22T12:54:07 | 2021-02-22T12:54:16 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,907,664 | 20,998 | alexey-milovidov | Not relevant for this release. | 2021-02-21T19:01:00 | 2021-02-21T19:01:00 | {} | MEMBER |
ClickHouse | ClickHouse | 782,911,709 | 21,016 | alexey-milovidov | > AST fuzzer (ASan) — 0x603000328861 is located 1 bytes to the right of 32-byte region [0x603000328840,0x603000328860)
https://github.com/ClickHouse/ClickHouse/issues/19233 CC @Enmk | 2021-02-21T19:28:12 | 2021-02-21T19:28:12 | {} | MEMBER |
ClickHouse | ClickHouse | 782,912,293 | 19,914 | alexey-milovidov | @KochetovNicolai has fixed this issue in #20073. | 2021-02-21T19:31:59 | 2021-02-21T19:31:59 | {} | MEMBER |
ClickHouse | ClickHouse | 783,211,551 | 12,454 | asafcombo | reproduced on 20.12.5 revision 54442 | 2021-02-22T08:58:45 | 2021-02-22T08:58:45 | {} | NONE |
ClickHouse | ClickHouse | 783,258,267 | 21,023 | alexey-milovidov | Performance test Ok. | 2021-02-22T10:09:48 | 2021-02-22T10:09:48 | {} | MEMBER |
ClickHouse | ClickHouse | 783,263,694 | 21,041 | alexey-milovidov | Need to check if ClickHouse at least tries to connect to this MongoDB instance.
1. Check the messages in logs. Also `SET send_logs_level = 'trace'` before executing the query in clickhouse-client.
2. Check tcpdump. | 2021-02-22T10:17:54 | 2021-02-22T10:17:54 | {} | MEMBER |
ClickHouse | ClickHouse | 783,377,454 | 12,709 | filimonov | > does kafka engine not support arrch64?
Support since: https://github.com/ClickHouse/ClickHouse/pull/19369 | 2021-02-22T13:34:17 | 2021-02-22T13:34:17 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,377,537 | 20,087 | Felixoid | 1. Run `OPTIMIZE shard_01.graphite FINAL` to see, if it works.
2. If your data still remains the same, I suspect the rollup configuration doesn't work as expected by some reason.
3. If works, inspect the logs of graphite-ch-optimizer and see if it launches optimizations. | 2021-02-22T13:34:25 | 2021-02-22T13:35:26 | {} | MEMBER |
ClickHouse | ClickHouse | 782,869,883 | 12,571 | alexey-milovidov | The query
```
SELECT
q.id,
p.id
FROM testdb.xs AS q
, testdb.xs AS p
WHERE (rand() % 100000000) = 123
```
works alright, the memory usage is minimal (4.70 GiB).
Something is related to the condition on `startsWith`. | 2021-02-21T14:49:40 | 2021-02-21T14:49:40 | {} | MEMBER |
ClickHouse | ClickHouse | 782,878,077 | 21,004 | vzakaznikov | That is currently the expected behavior as `WATCH` query will not get any updates. If you re-create a table again and do a new insert then you will see that you do get the updates.
@alexey-milovidov, is there a way to get a notification when a table is dropped? | 2021-02-21T15:43:57 | 2021-02-21T15:43:57 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,909,833 | 21,046 | alexey-milovidov | Better not to backport to avoid potential issues. | 2021-02-21T19:15:05 | 2021-02-21T19:15:05 | {} | MEMBER |
ClickHouse | ClickHouse | 782,915,349 | 20,599 | alexey-milovidov | The reason is "trivial". | 2021-02-21T19:53:52 | 2021-02-21T19:53:52 | {} | MEMBER |
ClickHouse | ClickHouse | 783,059,065 | 21,054 | cyberhuman | Hmm, no? Because the records in the example are from a few days ago, and new orphaned nodes are still being created and not removed. | 2021-02-22T03:58:32 | 2021-02-22T04:04:57 | {} | NONE |
ClickHouse | ClickHouse | 783,331,235 | 20,490 | traceon | @vdimir we've discussed this internally, and will probably research a possibility to propose a separate PR with a configurable support for `HTTP Trailer` first (metadata at the end of chunked messages). Then this PR will make more sense, hopefully. | 2021-02-22T12:13:16 | 2021-02-22T12:13:16 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,372,965 | 15,473 | filimonov | It seems it does not reproduce anymore on version >= 20.8. | 2021-02-22T13:27:14 | 2021-02-22T13:27:14 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,914,278 | 20,213 | MaxJPowers | @nikitamikhaylov The 1 minute is not okay for the timeout as I'm trying to find the maximum number of cached entries, which won't work if the timeout is longer than 1 minute since that puts an artificial cap on the size of the dictionary. So far I've found no way to change this in any of the settings and it seems to be... | 2021-02-21T19:46:02 | 2021-02-21T19:46:14 | {} | NONE |
ClickHouse | ClickHouse | 783,187,235 | 21,041 | OmarBazaraa | > Does MongoDB server actually receive the query?
No, I don't think MongoDB server is receiving the query.
> Maybe full scan query is just too hard and takes too long to process?
I am testing on a collection with only 1 record.
| 2021-02-22T08:22:31 | 2021-02-22T08:22:31 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,263,459 | 17,806 | liubo0127 | joinGet('two','word', id) seems to find the `default.two` table by default, change it to joinGet(‘db.two','word', id) and it is normal. | 2021-02-22T10:17:31 | 2021-02-22T10:17:31 | {} | NONE |
ClickHouse | ClickHouse | 783,345,050 | 20,548 | filimonov | Analyzed log in details:
1) The consumer group existed and was committed at the position 9606141231.
2) then started to fetch it from that position it responded "Broker: Offset out of range"
3) then offset reset happen "offset reset (at offset 9606141231) to BEGINNING: Broker: Offset out of range: Broker: Offset... | 2021-02-22T12:38:58 | 2021-02-22T12:47:45 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 783,391,508 | 21,067 | den-crane | Check with version 21.3.1.6083 https://repo.yandex.ru/clickhouse/deb/testing/main/ | 2021-02-22T13:53:36 | 2021-02-22T13:53:36 | {} | CONTRIBUTOR |
ClickHouse | ClickHouse | 782,830,655 | 19,579 | alexey-milovidov | Fixed. | 2021-02-21T09:58:31 | 2021-02-21T09:58:31 | {} | MEMBER |
ClickHouse | ClickHouse | 782,852,517 | 21,026 | alexey-milovidov | See #21028. | 2021-02-21T12:47:21 | 2021-02-21T12:47:21 | {} | MEMBER |
ClickHouse | ClickHouse | 782,912,470 | 19,279 | alexey-milovidov | Duplicate #19303 | 2021-02-21T19:33:04 | 2021-02-21T19:33:04 | {} | MEMBER |
ClickHouse | ClickHouse | 783,075,022 | 21,054 | cyberhuman | Thank you for looking into this issue!
> 1. Why do you use Replicated Tables as temporary instead of MergeTree?
I will check with my colleagues why and let you know.
> 2. Why do you hardcode replica 0 , 1 ?
In the main table, it's hardcoded because it's created by the code instead of the configuration. It's... | 2021-02-22T04:42:26 | 2021-02-22T04:43:02 | {} | NONE |
ClickHouse | ClickHouse | 782,835,120 | 19,398 | alexey-milovidov | Fixed in #19532. | 2021-02-21T10:34:32 | 2021-02-21T10:34:32 | {} | MEMBER |
ClickHouse | ClickHouse | 782,852,444 | 21,028 | alexey-milovidov | Category: harmful feature.
Map data type should not support Nullable keys at all. | 2021-02-21T12:46:47 | 2021-02-21T12:46:47 | {} | MEMBER |
ClickHouse | ClickHouse | 782,853,351 | 21,029 | alexey-milovidov | @hexiaoting This issue looks important.
Fortunately, the Map data type is only available under experimental flag and is not suitable for production usages. | 2021-02-21T12:52:28 | 2021-02-21T12:52:28 | {} | MEMBER |
ClickHouse | ClickHouse | 782,854,927 | 20,182 | alexey-milovidov | Blocked by https://github.com/ClickHouse/ClickHouse/issues/21034. | 2021-02-21T13:03:46 | 2021-02-21T13:03:46 | {} | MEMBER |
ClickHouse | ClickHouse | 782,907,510 | 21,014 | alexey-milovidov | Not relevant for this release. | 2021-02-21T19:00:06 | 2021-02-21T19:00:06 | {} | MEMBER |
ClickHouse | ClickHouse | 782,913,908 | 20,599 | alexey-milovidov | @KochetovNicolai Performance test results are reproduced.
```
CREATE TABLE simple_mergetree (EventDate Date, x UInt64) ENGINE = MergeTree ORDER BY x;
INSERT INTO simple_mergetree SELECT number, today() + intDiv(number, 10000000) FROM numbers_mt(100000000);
OPTIMIZE TABLE simple_mergetree FINAL;
```
```
click... | 2021-02-21T19:43:42 | 2021-02-21T19:44:55 | {} | MEMBER |
ClickHouse | ClickHouse | 783,260,430 | 21,053 | alexey-milovidov | > Integration tests (thread) — fail: 1, passed: 1123, error: 0
Broken Kafka test, @filimonov | 2021-02-22T10:13:15 | 2021-02-22T10:13:15 | {} | MEMBER |
ClickHouse | ClickHouse | 783,268,632 | 21,055 | alexey-milovidov | This behaviour is correct - it protects you from mistakes in table definition.
`PARTITION BY today()` can lead to surprising results - some queries won't be able to find records in table.
Instead you should create `insert_date DEFAULT today()` field in table and `PARTITION BY ifNull(day,insert_date)` | 2021-02-22T10:25:55 | 2021-02-22T10:25:55 | {} | MEMBER |
ClickHouse | ClickHouse | 783,397,243 | 17,079 | alexey-milovidov | I'm adding "need info" and also closing with "won't fix" in case no info will be provided :) | 2021-02-22T14:02:36 | 2021-02-22T14:02:36 | {} | MEMBER |
ClickHouse | ClickHouse | 788,343,028 | 6,093 | alexey-milovidov | No progress so far. | 2021-03-01T22:20:54 | 2021-03-01T22:20:54 | {} | MEMBER |
ClickHouse | ClickHouse | 788,496,175 | 18,583 | alexey-milovidov | @jart
I see that there are AVX non-temporal stores: https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=stream_si256&expand=5673,5672,5673
but we don't use them.
Are they beneficial? | 2021-03-02T01:29:56 | 2021-03-02T01:29:56 | {} | MEMBER |
ClickHouse | ClickHouse | 788,823,847 | 21,334 | alesapin | Slightly more changes than I expected. | 2021-03-02T11:02:50 | 2021-03-02T11:02:50 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.