zzsmdfj
a0f391745d
to 15357_MaterializeMySQL_support_drop_mulit_table-fix style-black
2022-11-21 11:48:57 +08:00
zzsmdfj
e177927efb
to 15357_MaterializeMySQL_support_drop_mulit_table-fix code-style
2022-11-19 12:05:27 +08:00
zzsmdfj
6a998917b0
to MaterializeMySQL_support_drop_mulit_table
2022-11-18 21:29:13 +08:00
Kruglov Pavel
4ecbcbf5e1
Merge branch 'master' into MaterializedMySQL_improvement_bug_fix
2022-11-11 12:54:02 +01:00
zzsmdfj
a9a208c3cd
to MaterializedMySQL_improvement_bug_fix-fix code style
2022-11-11 11:46:22 +08:00
zzsmdfj
0e614aec12
to MaterializedMySQL_improvement_bug_fix-fix code sytle
2022-11-11 11:24:29 +08:00
zzsmdfj
d4e270b522
to MaterializedMySQL_improvement_bug_fix-fix codestyle
2022-11-11 10:44:16 +08:00
Stig Bakken
9020631826
Ignore SAVEPOINT queries in MaterializedMySQL
2022-11-10 23:27:21 +01:00
zzsmdfj
eeb9c57c59
to fix issue 42856 and MaterializedMySQL improvement
2022-11-03 20:21:02 +08:00
Alexey Milovidov
b42d26acfe
Remove one line from XML, because we do not care
2022-08-28 02:44:02 +02:00
Roman Vasin
ac2a42cfb0
Fix test 00189_time_zones_long and integration test test_materialized_mysql_database
2022-07-26 10:44:58 +00:00
Alexander Tokmakov
2c5a88faba
deprecate Ordinary database
2022-06-23 10:20:14 +02:00
Nikita Taranov
41ba0118b5
Bring back #36396 ( #38110 )
...
* Revert "Revert "More parallel execution for queries with `FINAL` (#36396 )""
This reverts commit 5bfb15262c
2022-06-22 15:05:07 +02:00
Mikhail f. Shiryaev
e6f5a3f98b
Apply black formatter to all *.py files in the repo
2022-03-22 17:39:58 +01:00
alesapin
1eefdc8df6
Fix more test
2022-03-15 17:31:33 +01:00
zzsmdfj
e7f567ddfd
to #31469_MaterializedMysql_mysqlDate2CkDate32-adjust code-style
2022-03-08 18:25:21 +08:00
zzsmdfj
67b9f81104
to #31469_MaterializedMysql_mysqlDate2CkDate32
2022-03-08 18:17:22 +08:00
zzsmdfj
4d9bdfa58c
to 32977_MaterializedMySQL_add_table_list_settings
2022-03-01 10:21:58 +08:00
zzsmdfj
2fa5289637
MaterializedMySQL add table_list_settings-update test
2022-02-10 17:29:51 +08:00
zzsmdfj
ac264e33d5
MaterializedMySQL_add_table_list_settings
2022-02-10 13:52:13 +08:00
zzsmdfj
f54d607b3b
to MaterializeMySQL_support_set_and_other_dataType
2022-01-21 12:24:13 +08:00
zzsmdfj
e380e59b16
MaterializeMySQL support SET YEAR TIME GEOMETRY dataType
2022-01-21 12:24:11 +08:00
Stig Bakken
4b109e5399
Add integration test for EXPLAIN TABLE OVERRIDE
2022-01-03 10:58:05 +01:00
Kseniia Sumarokova
764bb1181f
Merge pull request #33017 from stigsb/table-overrides-drop-add-column-support
...
Remove the possibility of adding columns with table overrides
2021-12-22 22:30:21 +03:00
tavplubix
4ba76dd8e3
Update materialize_with_ddl.py
2021-12-22 12:19:51 +03:00
Stig Bakken
1cc70ad524
Remove the possibility of adding columns with table overrides
...
(except ALIAS columns)
Supporting this properly requires more comprehensive changes.
2021-12-22 08:20:14 +01:00
zzsmdfj
4a0554c963
to #15182_MaterializeMySQL_support_bit_type-fix-flakey-test
2021-12-17 18:30:09 +08:00
zzsmdfj
e9eed1f927
to #15182_MaterializeMySQL_support_bit_type
2021-12-17 15:03:24 +08:00
Stig Bakken
bb521cd363
Add TABLE OVERRIDE feature for MaterializedMySQL databases
2021-12-07 09:45:02 +01:00
Stig Bakken
f7578e7b9d
Fix flaky test for MaterializedMySQL CREATE TABLE LIKE
2021-12-01 13:40:22 +01:00
Haavard Kvaalen
fa7b547212
Always quote table name
...
This fixes an issue if the database contained a table named 'table'.
We would previously generate a query that ClickHouse could not parse.
2021-11-25 11:49:23 +01:00
Stig Bakken
ff46e8bb51
Drop support for DatabaseOrdinary in MaterializedMySQL
...
1. Dropped support for DatabaseOrdinary for MaterializeMySQL. It
is marked as experimental, and dropping support makes the code
more maintaible, and speeds up integration tests by 50%.
2. Get rid of thread name logic for StorageMaterializeMySQL wrapping,
use setInternalQuery instead (similar to MaterializedPostgreSQL).
2021-11-18 11:46:51 +01:00
Stig Bakken
3eac620d4d
Handle CREATE TABLE LIKE in MaterializedMySQL
2021-11-15 14:43:50 +01:00
Haavard Kvaalen
c41923c595
MaterializedMySQL: Update GTID set at end of transaction
...
We would update the set of seen GTIDs as soon as we saw a GTID_EVENT,
which arrives before a transaction. This would mostly work fine, but
if we lost the connection to MySQL in the middle of a large transaction
we would persist that the transaction had been processed as soon as the
transaction had started. When the connection was reestablished, we
would not process the transaction again, which meant that we only
applied parts of it.
Fix this by updating the seen GTIDs at the end of the transaction
instead.
2021-10-07 14:09:00 +02:00
Alexey Milovidov
e513a5db32
Change <yandex> to <clickhouse> in configs
2021-09-20 01:38:53 +03:00
Alexander Tokmakov
a7e644f774
support old name
2021-07-26 21:24:32 +03:00
Alexander Tokmakov
63ab38ee09
rename MaterializeMySQL to MaterializedMySQL
2021-07-26 21:17:28 +03:00
