analytics service in the world › Most popular analytics service in Russia › 800’000 RPS › ≈80 billion events per day › 98% processed less than 5 minutes › More than 1000 servers running ClickHouse 9 / 97 Production: Badoo › Dating-focused social network › More than 550’000’000 users › More than 1.8 M/sec events in peak › Max processing time 15 minutes › 12 servers running ClickHouse https://badoo.com/ 26 Production: Badoo HTTP Server Aggregation Services HDFS Storage MR Aggregation Old Events Pusher Events Storage Old Events Database PHP API Client Graphs User User User Browser Mobile App 27 / 97 ClickHouse

cluster upgrade cluster_name version Events of the plugin TiDB audit plugin divides all the events into 3 categories: CONNECTION: Connection events and authentication events. Example of the CONNECTION logs: [SQL_STATEMENTS=DropTable] Note: ● TABLE_ACCESS events are NOT logged by default. See “5. Modify audit configuration” on how to configure those events. ● If the statement fails, they are NOT logged. file ● Version: plugin version Enable or disable auditing By default, the CONNECTION and GENERAL events are audited after enabling the plugin. You can enable or disable the plugin on any TiDB node, because

binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported innodb_ft_enable_stopword NotSupported innodb_ft_user_stopword_table NotSupported m to a VStream to receive change events from other shards. The VStream pulls events from one or more VStreamer instances on VTTablet instances, which in turn pulls events from the binary log of the underlying for efficient execution of functions such as VReplication where a subscriber can indirectly receive events from the 28 binary logs of one or more MySQL instance shards, and then apply it to a target instance

binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported innodb_ft_enable_stopword NotSupported 22 System variable Handled innodb_ft_user_stopword_table to a VStream to receive change events from other shards. The VStream pulls events from one or more VStreamer instances on VTTablet instances, which in turn pulls events from the binary log of the underlying receive events from the binary logs of one or more MySQL instance shards, and then apply it to a target instance. An user can leverage VStream to obtain in-depth information about data change events for given

the audit plugin 1 Obtain the database auditing feature 2 The range of database auditing 2 The events of database auditing 3 Recorded information in audit logs 5 General information 5 SQL statement Auditing can record information such as query statements, transaction operations, and user login events. This information can be stored in the audit log for future queries and analysis, thus ensuring the statements are audited) ● Operations of starting, stopping, scaling up or scaling down the database. The events of database auditing TiDB database auditing classifies SQL operations into several Event Classes

binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported innodb_ft_enable_stopword NotSupported innodb_ft_user_stopword_table NotSupported m to a VStream to receive change events from other shards. The VStream pulls events from one or more VStreamer instances on VTTablet instances, which in turn pulls events from the binary log of the underlying receive events from the binary logs of one or more MySQL instance shards, and then apply it to a target instance. An user can leverage VStream to obtain in-depth information about data change events for given

Columns · · · · · 804 6.5.3 Filter Binlog Events· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 811 6.5.4 Filter DML Events Using SQL Expressions · · · · · · · · · and add a RestoreTS field in the logs #53645 @dveeden • TiCDC • Support directly outputting raw events when the downstream is a Message Queue (MQ) or cloud storage #11211 @CharlesCheung96 2.2.5 Bug fixes features on TiDB Playground. 2.4.1 Unsupported features • Stored procedures and functions • Triggers • Events • User-defined functions • FULLTEXT syntax and indexes #1793 • SPATIAL (also known as GIS/GEOMETRY)

Columns · · · · · 802 6.5.3 Filter Binlog Events· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 809 6.5.4 Filter DML Events Using SQL Expressions · · · · · · · · · maintain connections to TiDB so that they live �→ through rolling restarts, upgrades, or scaling events. �→ Data Migration in-band schema tracking capabilities by embedding table �→ schema information in DDL and BOOTSTRAP events. TiCDC supports the Debezium

Columns · · · · · 882 6.5.3 Filter Binlog Events· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 889 6.5.4 Filter DML Events Using SQL Expressions · · · · · · · · · Delete events #10969 @3AceShowHand Starting from v8.4.0, TiDB and TiCDC introduce the Checksum V2 algorithm to address issues of Checksum V1 in verifying old values in Update or Delete events after ADD #55906 @Rustin170506 • Introduce a DDL notifier to allow the statistics module to subscribe to DDL events #55722 @fzzf678 @lance6716 @Rustin170506 • Force new TiDB nodes to take over DDL ownership during

Columns · · · · · 807 6.5.3 Filter Binlog Events· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 814 6.5.4 Filter DML Events Using SQL Expressions · · · · · · · · · features on TiDB Playground. 2.4.1 Unsupported features • Stored procedures and functions • Triggers • Events • User-defined functions • FULLTEXT syntax and indexes #1793 • SPATIAL (also known as GIS/GEOMETRY) bundle: npm run build 3. Invoke the sample Lambda function: sam local invoke --env-vars env.json -e events/event.json " �→ tidbHelloWorldFunction" 4. Check the output in the terminal. If the output is similar