Closed wanghangyu817 closed 1 year ago
what version of maxwell? and can you recover the exact original SQL?
I am currently using version 1.35.0, and when I test 1.38.0, I get the same error message, raw sql: CREATE INDEX device_id_idx ON event_tracking_info_extra(event, create_time)
. It is found in debug that a specific comment has been added to the executed sql, which is the cause of the error
can you run liike show binlog events from ...
and recover the exact original SQL? Your PR would just make it so that maxwell will never process any sql that contained a # comment
style comment, which isn't right. I can't reproduce your issue without the full, original sql (including comments.)
I get sql :
# POLARX_ORIGIN_SQL=CREATE INDEX device_id_idx ON event_tracking_info_extra (event, create_time)
# POLARX_TSO=698905756181096044815201227773638819850000000000000000
CREATE INDEX device_id_idx ON event_tracking_info_extra (event, create_time)
If '--output_ddl=false' does the processing in pr solve the problem (which I'm using now and don't need to output ddl), or does the processing in pr cause other problems
no that won't solve your problem.
On Wed, Nov 2, 2022 at 6:31 AM Rain丨xiyang @.***> wrote:
If '--output_ddl=false' does the processing in pr solve the problem (which I'm using now and don't need to output ddl), or does the processing in pr cause other problems
— Reply to this email directly, view it on GitHub https://github.com/zendesk/maxwell/issues/1927#issuecomment-1300411048, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAB7P5EPZW4XAR7XEVXMQ63WGJULJANCNFSM6AAAAAARN37FXI . You are receiving this because you commented.Message ID: @.***>
I'm currently using pr code in a production environment, and I'm worried about other issues. I think only ddl statements go into this regular expression
fixed in latest
Execute SQL : CREATE INDEX device_id_idx ON event_tracking_info_extra (event, create_time)
Exception: