8 Commits

Author	SHA1	Message	Date
Yatsishin Ilya	ce1e2b18a3	Fix codespell warnings. Split style checks. Update style checks docker	2020-12-24 13:17:52 +03:00
Vasily Nemkov	e5ec81f7cd	Single quotes around column names	2020-12-19 20:58:23 +02:00
Vasily Nemkov	e166aae3f9	Using CSV-like strings for list of columns to deduplicate by instead of JSON-like notation.	2020-12-18 13:44:56 +02:00
Vasily Nemkov	8c5daf0925	Fixed building tests with GCC-10 ... Also a minor cleanup of the test code.	2020-12-08 13:15:18 +03:00
Vasily Nemkov	168155eeec	Minor: cleanup	2020-12-07 18:07:40 +03:00
Vasily Nemkov	dbdc018ab8	Fixed and refined unite-test ... * no more undefined values for attributes in ReplicatedMergeTreeLogEntry * validation of string serialization format	2020-12-07 17:38:25 +03:00
Vasily Nemkov	70ea507dae	OPTIMIZE DEDUPLICATE BY columns ... Extended OPTIMIZE ... DEDUPLICATE syntax to allow explicit (or implicit with asterisk/column transformers) list of columns to check for duplicates on. Following syntax variants are now supported: OPTIMIZE TABLE table DEDUPLICATE; -- the old one OPTIMIZE TABLE table DEDUPLICATE BY *; OPTIMIZE TABLE table DEDUPLICATE BY * EXCEPT colX; OPTIMIZE TABLE table DEDUPLICATE BY * EXCEPT (colX, colY); OPTIMIZE TABLE table DEDUPLICATE BY col1,col2,col3; OPTIMIZE TABLE table DEDUPLICATE BY COLUMNS('column-matched-by-regex'); OPTIMIZE TABLE table DEDUPLICATE BY COLUMNS('column-matched-by-regex') EXCEPT colX; OPTIMIZE TABLE table DEDUPLICATE BY COLUMNS('column-matched-by-regex') EXCEPT (colX, colY); Note that * behaves just like in SELECT: MATERIALIZED, and ALIAS columns are not used for expansion. Also, it is an error to specify empty list of columns, or write an expression that results in an empty list of columns, or deduplicate by an ALIAS column. Column transformers other than EXCEPT are not supported.	2020-12-07 09:44:07 +03:00
Nicolae Vartolomei	af76ff1dbf	RFC: Add metadata section to MergeTreeWriteAheadLog ... Current WAL format doesn't seem to be extendable without breaking reverse compatibility. This PR proposes to introduces a metadata section for each action in the WAL to which optional fields can be added. Adding new fields is trivial and doesn't have to break backwards compatibility if these are not critical for correctness. Metadata contains the minimum version of the reader allowed to interpret it. Removing fields is not supported.	2020-10-19 12:16:31 +01:00