- 27 4月, 2020 3 次提交
-
-
由 alexey-milovidov 提交于
Add tasks/memory metrics for distributed/buffer schedule pools
-
由 Alexey Milovidov 提交于
-
由 Alexey Milovidov 提交于
-
- 26 4月, 2020 19 次提交
-
-
由 alexey-milovidov 提交于
IRowInputFormat performance fix
-
由 alexey-milovidov 提交于
Fix overflow in simpleLinearRegression
-
由 alexey-milovidov 提交于
WIP. Flush output format on each block in executeQuery
-
由 alexey-milovidov 提交于
-
由 Alexey Milovidov 提交于
-
由 Alexey Milovidov 提交于
-
由 Andrew Onyshchuk 提交于
-
由 Alexey Milovidov 提交于
-
由 alexey-milovidov 提交于
Fix "odbc-bridge" test
-
由 alexey-milovidov 提交于
Markdown format
-
由 Alexey Milovidov 提交于
-
由 alexey-milovidov 提交于
Tiny kafka fixes
-
由 alexey-milovidov 提交于
Fix visible drift of MemoryTracking metric
-
由 alexey-milovidov 提交于
Split fuzzers and sanitizers
-
由 alexey-milovidov 提交于
Update developer_instruction.md
-
由 alexey-milovidov 提交于
Elixir 3rd-party client - Pillar
-
由 alexey-milovidov 提交于
Proper Distributed shutdown (fixes UAF, avoid waiting for sending all batches)
-
由 Dmitry 提交于
-
由 Ruzal Ibragimov 提交于
Fix creating testing databases.
-
- 25 4月, 2020 15 次提交
-
-
由 alexey-milovidov 提交于
Add link to clickhouse-plantuml
-
由 Alexey Milovidov 提交于
-
由 Azat Khuzhin 提交于
This will just pollute the output log. And this is significant for kafka streaming, since it will print this message for each message (due to how ReadBufferFromKafkaConsumer/KafkaBlockInputStream works). You can see this in the server log of the test_storage_kafka (integration test), for the table with kafka_skip_broken_messages > 0, it will have 52 lines of such message, 2 with "Skipped 1 rows" and 50 with "Skipped 0 rows" (since there are 52 messages in summary, 2 malformed and 50 correct).
-
由 Mikhail f. Shiryaev 提交于
-
由 Eldar Zaitov 提交于
-
由 Azat Khuzhin 提交于
Since later requires full specification (engine and so on).
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
StorageDistributed::shutdown() does not acquire the lock, that controls access to the cluster_nodes_data, thus it does not synced with the requireDirectoryMonitor(), hence some monitors can be untracked that will trigger UAF (use-after-free) after DROP TABLE dist: This is for the SIGSEGV from the DirectoryMonitor (with already destroyed storage): 0 0x0000000008e9f760 in std::__1::__cxx_atomic_load<int> (__order=std::__1::memory_order::seq_cst, __a=0x0) 1 std::__1::__atomic_base<int, false>::load (__m=std::__1::memory_order::seq_cst, this=0x0) <-- this is nullptr 2 std::__1::__atomic_base<int, false>::operator int (this=0x0) 3 DB::ActionBlocker::isCancelled (this=0x7f85e31c9bb8) at ../src/Common/ActionBlocker.h:18 4 DB::StorageDistributedDirectoryMonitor::run (this=0x7f85f93b2a00) at ../src/Storages/Distributed/DirectoryMonitor.cpp:140
-
由 alexey-milovidov 提交于
Fix docs of 'generateRandom' function
-
由 Anton Popov 提交于
-
由 Avogar 提交于
-
由 Ivan Blinkov 提交于
-
由 tavplubix 提交于
DatabaseAtomic
-
由 Alexander Tokmakov 提交于
-
由 Ivan Blinkov 提交于
-
- 24 4月, 2020 3 次提交
-
-
由 Anton Popov 提交于
add CA certificates to clickhouse-server docker image
-
由 Ivan Blinkov 提交于
-
由 Avogar 提交于
-