Commit Graph
130 Commits
Author SHA1 Message Date
Pedro Ferreira a0722cbe71 Improved lambda expressions and cleaned dump table oracle 2025-07-15 07:27:41 +00:00
Pedro Ferreira b0fe7d2ca9 Add possibility to ignore error codes when oracles fail due to a certain error 2025-07-11 12:26:58 +00:00
Pedro Ferreira 072718011f Don't run oracles as often 2025-07-09 09:15:47 +00:00
Pedro Ferreira ddcf8bc0f8 While re-reading the SQL log, restart if that happened 2025-07-04 11:11:15 +00:00
Pedro FerreiraandGitHub 6ece4113aa Merge pull request #82654 from PedroTadim/next-fuzz-upt
Next fuzzer fixes
2025-06-30 08:05:15 +00:00
Pedro Ferreira af81951bf4 Generalize string length and property update 2025-06-25 07:57:02 +00:00
Raúl Marín d6ac63c8d2 Style: Forbid the use of quotes for includes (partial) 2025-06-24 13:20:10 +02:00
Pedro Ferreira 77108d6b3c Fixing async inserts in BuzzHouse 2025-06-18 12:37:12 +00:00
Pedro FerreiraandGitHub 7927b9e710 Merge pull request #80244 from PedroTadim/test-server2
First iteration for La Casa Del Dolor
2025-06-04 07:16:58 +00:00
Raúl Marín 3cd4ad0d16 Remove usage of settings.h 2025-06-02 18:00:25 +02:00
Pedro FerreiraandGitHub 215fa9b00d Merge branch 'master' into test-server2 2025-05-28 11:28:38 +02:00
Pedro Ferreira e17931a66a Make dump table oracle completely optional 2025-05-27 09:36:32 +00:00
Pedro Ferreira 1376339f38 Fix 2025-05-23 08:19:07 +00:00
Pedro Ferreira d198d9fb24 Give more details 2025-05-23 08:12:35 +00:00
Pedro Ferreira 5a9fa20f8d CI fix 2025-05-21 14:47:36 +00:00
Pedro Ferreira 79e2265973 Add "disallowed_error_codes" setting, more powerful than fail_on_timeout 2025-05-21 14:27:04 +00:00
Pedro Ferreira 0a92a3ff41 Real fix 2025-05-12 16:49:45 +00:00
Pedro Ferreira 505fba8876 Merge remote-tracking branch 'origin/master' into test-server2 2025-05-01 15:28:07 +00:00
Pedro Ferreira 7de1abb917 Add optimize option for dump oracle 2025-04-30 09:50:25 +00:00
Pedro Ferreira c2199e2d20 Added parallel with queries 2025-04-22 12:14:55 +00:00
Pedro Ferreira a99a4d1ce6 Added steps for PARALLEL WITH 2025-04-22 11:15:08 +00:00
Pedro Ferreira 2a889151b5 Added first version for server fuzzer and modifications needed for existing client fuzzers 2025-04-17 15:43:46 +00:00
Pedro Ferreira 29483f0a02 Not needed 2025-04-17 11:03:34 +00:00
Pedro FerreiraandGitHub d1c0564f13 Merge branch 'ClickHouse:master' into next-update 2025-04-15 10:10:07 +02:00
Pedro Ferreira 167fb1e35a Use system commands in multi-setting oracle 2025-04-11 16:47:38 +00:00
Azat Khuzhin a595877d02 Fix handling INSERTs after async_insert handling from server for fuzzer
Rewrite API one more time, since in case of fuzzer that assertion could
not be satisfied, due to it fuzz the query, but leave the insert->data,
and if we will parse query from formatted we will loose insert->data

And also cleanup interface, remove report_error that is unused, and move
echo_query out.

CI: https://s3.amazonaws.com/clickhouse-test-reports/json.html?PR=77578&sha=296cda664bb7288f786ef98e2af9ea1e0e5094fd&name_0=PR&name_1=AST%20fuzzer%20%28amd_debug%29
2025-04-11 14:46:11 +02:00
Azat Khuzhin 296cda664b Re-introduce query_to_execute for processParsedSingleQuery()
The problem is that without this distinction we have a query with
trailing comments (due to applied adjustQueryEnd())
2025-04-11 10:43:49 +02:00
Azat Khuzhin c6f93e16bb Pass query for execution as string_view
The data that ASTPtr may refer to (in case of INSERT) should point to
the same memory region, since in case of async_insert, we need to
calcualte the end of the query, and we cannot do this without this.
2025-04-10 17:52:28 +02:00
Azat Khuzhin bafa45a7b1 Fix applying async_insert from server (via apply_settings_from_server)
The problem is that async_insert is checked during parsing, to know what
to send to the server, even before server settings available. And this
leads to "Unknown packet 11 from server" errors.

So, first approach will be to simply ignore async_insert for
apply_settings_from_server, but this setting is interesting to apply
from the server (since this may have performance impact).

Another is to detect what part of the query we should after server
settings had been received, this patch follows this approach.
2025-04-10 16:37:26 +02:00
Pedro Ferreira 3cc4fc757b Implement fail on timeout 2025-04-09 15:00:14 +00:00
Pedro Ferreira 58ae24324e More const 2025-04-08 14:32:34 +00:00
Pedro Ferreira 5c6208ae1d More settings and fix tidy compilation 2025-03-27 12:50:41 +00:00
Pedro Ferreira cf82890c3e Fix and better answer 2025-03-26 17:39:15 +00:00
Pedro Ferreira d17e2d887d Sometimes use other settings when reading the data when not validating content 2025-03-26 17:18:09 +00:00
Pedro Ferreira 570f73386f Increase probability and keep lists sorted 2025-03-26 16:15:23 +00:00
Pedro Ferreira 98fa5a4757 Cleanup and rename setting 2025-03-26 15:47:41 +00:00
Pedro Ferreira 68a32ca839 Attempt to dump and read into another table to test formats with bad inputs 2025-03-26 15:08:00 +00:00
Raúl Marín fa763588c1 Fix buzzhouse build 2025-03-20 19:34:30 +01:00
Nikita Mikhailov f6694387bc Fix build 2025-03-14 20:15:47 +01:00
Nikita Mikhailov 450c8ba2a8 Remove formatAST completely 2025-03-14 20:04:45 +01:00
Nikita Mikhailov b600314abb Rename method and add another one 2025-03-14 19:57:10 +01:00
Nikita Mikhailov 050135d5c9 Remove queryToString 2025-03-14 19:57:10 +01:00
Pedro Ferreira a7a764f642 Merge remote-tracking branch 'origin/master' into ast-update 2025-03-13 11:59:57 +00:00
Pedro Ferreira fee5e405c7 Use avaialble Parquet readers when possible 2025-03-10 15:37:46 +00:00
Pedro Ferreira c789154767 Settings are now propagated from the server to the client 2025-03-10 13:29:54 +00:00
Pedro FerreiraandGitHub 3432fbccbb Merge branch 'master' into ast-update 2025-03-10 08:56:33 +01:00
Pedro Ferreira b719f75b65 Fix peer check 2025-03-05 16:28:53 +00:00
Pedro Ferreira 9953bad215 More features added in v25.2 2025-03-03 12:09:02 +00:00
Pedro Ferreira bd47f63996 Removing duplicated code 2025-03-03 10:40:59 +00:00
Pablo Marcos cb988ef115 Remove unnecessary include
If no destructor is added, an implicit destructor is automatically
generated in the header file for every translation unit including
the header. Since it's the destructor the one that needs to know
the size of what std::unique_ptr points to in order to know how
to destroy it, the best thing we can do is to define a default
destructor in the .cpp to prevent any automatic destructors
being generated via header include.
2025-02-27 08:55:06 +00:00