Bug #77949 In Delete_rows_event size of null_bits is wrong
Submitted: 5 Aug 2015 16:40 Modified: 12 Nov 2015 13:54
Reporter: NEHA KUMARI Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Utilities: Binlog Events Severity:S3 (Non-critical)
Version:1.0.0 OS:Any
Assigned to: CPU Architecture:Any

[5 Aug 2015 16:40] NEHA KUMARI
Description:
When we try to DELETE something from a table that has 24 columns and 12 of them are primary key, DELETE_ROWS_EVENT will affect 12 columns (because it only affects primary key, and this table has primary key that
spans across 12 columns) the number of bytes required to store the number of columns getting affected is = int((24+7)/8) = 3 which is wrong it should be = int((12 +7)/8) = 2.

How to repeat:
Fire a Delete_rows_event which changes number of columns less than the total number of columns and in such a way that it changes the number of bytes needed to store the number of columns getting affected.