| 程序包 | 说明 |
|---|---|
| net.wicp.tams.common.binlog.parser | |
| net.wicp.tams.common.binlog.parser.event | |
| net.wicp.tams.common.binlog.parser.event.mariadb |
| 限定符和类型 | 方法和说明 |
|---|---|
LogEvent |
LogDecoder.decode(LogBuffer buffer,
LogContext context)
Decoding an event from binary-log buffer.
|
static LogEvent |
LogDecoder.decode(LogBuffer buffer,
LogHeader header,
LogContext context)
Deserialize an event from buffer.
|
| 限定符和类型 | 类和说明 |
|---|---|
class |
AppendBlockLogEvent
Append_block_log_event.
|
class |
BeginLoadQueryLogEvent
Event for the first block of file to be loaded, its only difference from
Append_block event is that this event creates or truncates existing file
before writing data.
|
class |
CreateFileLogEvent
Create_file_log_event.
|
class |
DeleteFileLogEvent
Delete_file_log_event.
|
class |
DeleteRowsLogEvent
Log row deletions.
|
class |
ExecuteLoadLogEvent
Execute_load_log_event.
|
class |
ExecuteLoadQueryLogEvent
Event responsible for LOAD DATA execution, it similar to Query_log_event but
before executing the query it substitutes original filename in LOAD DATA
query with name of temporary file.
|
class |
FormatDescriptionLogEvent
For binlog version 4.
|
class |
GtidLogEvent |
class |
HeartbeatLogEvent
Replication event to ensure to slave that master is alive.
|
class |
IgnorableLogEvent
Base class for ignorable log events.
|
class |
IncidentLogEvent
Class representing an incident, an occurance out of the ordinary, that
happened on the master.
|
class |
IntvarLogEvent
An Intvar_log_event will be created just before a Query_log_event, if the
query uses one of the variables LAST_INSERT_ID or INSERT_ID.
|
class |
LoadLogEvent
This log event corresponds to a "LOAD DATA INFILE" SQL query on the following
form:
(1) USE db;
(2) LOAD DATA [CONCURRENT] [LOCAL] INFILE 'file_name'
(3) [REPLACE | IGNORE]
(4) INTO TABLE 'table_name'
(5) [FIELDS
(6) [TERMINATED BY 'field_term']
(7) [[OPTIONALLY] ENCLOSED BY 'enclosed']
(8) [ESCAPED BY 'escaped']
(9) ]
(10) [LINES
(11) [TERMINATED BY 'line_term']
(12) [LINES STARTING BY 'line_start']
(13) ]
(14) [IGNORE skip_lines LINES]
(15) (field_1, field_2, ..., field_n)
Binary Format: The Post-Header consists of the following six components.
|
class |
PreviousGtidsLogEvent |
class |
QueryLogEvent
A Query_log_event is created for each query that modifies the database,
unless the query is logged row-based.
|
class |
RandLogEvent
Logs random seed used by the next RAND(), and by PASSWORD() in 4.1.0. 4.1.1
does not need it (it's repeatable again) so this event needn't be written in
4.1.1 for PASSWORD() (but the fact that it is written is just a waste, it
does not cause bugs).
|
class |
RotateLogEvent
This will be deprecated when we move to using sequence ids.
|
class |
RowsLogEvent
Common base class for all row-containing log events.
|
class |
RowsQueryLogEvent |
class |
StartLogEventV3 |
class |
StopLogEvent
Stop_log_event.
|
class |
TableMapLogEvent
In row-based mode, every row operation event is preceded by a
Table_map_log_event which maps a table definition to a number.
|
class |
UnknownLogEvent
Unknown_log_event
|
class |
UpdateRowsLogEvent
Log row updates with a before image.
|
class |
UserVarLogEvent
User_var_log_event.
|
class |
WriteRowsLogEvent
Log row insertions and updates.
|
class |
XidLogEvent
Logs xid of the transaction-to-be-committed in the 2pc protocol.
|
| 限定符和类型 | 类和说明 |
|---|---|
class |
AnnotateRowsEvent
mariadb的ANNOTATE_ROWS_EVENT类型
|
class |
BinlogCheckPointLogEvent
mariadb10的BINLOG_CHECKPOINT_EVENT类型
|
class |
MariaGtidListLogEvent
mariadb的GTID_LIST_EVENT类型
|
class |
MariaGtidLogEvent
mariadb的GTID_EVENT类型
|
Copyright © 2017. All rights reserved.