[ https://issues.apache.org/jira/browse/HIVE-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669300#comment-16669300 ]
Eugene Ilchenko edited comment on HIVE-20679 at 10/30/18 8:47 PM: ------------------------------------------------------------------ [~anishek], found a 26MB single record in the MySQL table now. Seems like we found a root cause - "MSCK repair" for new external tables with many partitions. We have attached the insert statement to the original HW ticket. was (Author: diser555): [~anishek], found a 26MB single record in the MySQL table now. Seems like we found a root cause - "MSCK repair" for new tables. We have attached the insert statement to the original HW ticket. > DDL operations on hive might create large messages for DBNotification > --------------------------------------------------------------------- > > Key: HIVE-20679 > URL: https://issues.apache.org/jira/browse/HIVE-20679 > Project: Hive > Issue Type: Bug > Affects Versions: 3.1.0 > Reporter: anishek > Assignee: anishek > Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > Attachments: HIVE-20679.1.patch, HIVE-20679.2.patch, > HIVE-20679.3.patch, HIVE-20679.4.patch, HIVE-20679.5.patch, > HIVE-20679.6.patch, HIVE-20679.8.patch, HIVE-20679.9.patch, a.sql, b.sql > > > Certain type of ddl operations might create large messages as part of > DBNoitification, this might lead to the rdbms throwing an error when storing > the message since its size is to large. It will also increase the footprint > of the rdbms space usage. > We should try store compressed messages to allow handling these situations. > Edit: For notification_log table the message column for all supported > databases can store messages from 2GB to 4GB -- This message was sent by Atlassian JIRA (v7.6.3#76005)