enterprise-support team mailing list archive

Thread
Date

[Bug 1527232] [NEW] empty chunks logged as empty table

To: enterprise-support@xxxxxxxxxxxxxxxxxxx
From: Max Bubenick <max.bubenick@xxxxxxxxxxx>
Date: Thu, 17 Dec 2015 12:24:12 -0000
Reply-to: Bug 1527232 <1527232@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

When a chunk has no rows mydumper is logging it as empty table instead


** Message: Thread 3 dumping data for `db1`.`t1` where (`id` >= 538664524 AND `id` < 540676830)
** Message: Empty table db1.t1
** Message: Thread 3 dumping data for `db1`.`t1` where (`id` >= 540676830 AND `id` < 542689136)

Note: this is just a logging issue, backup is still consistent

** Affects: mydumper
     Importance: Low
     Assignee: Max Bubenick (max-bubenick)
         Status: Triaged

** Changed in: mydumper
       Status: New => Triaged

** Changed in: mydumper
   Importance: Undecided => Low

** Changed in: mydumper
     Assignee: (unassigned) => Max Bubenick (max-bubenick)

** Changed in: mydumper
    Milestone: None => 0.9.3

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1527232

Title:
  empty chunks logged as empty table

To manage notifications about this bug go to:
https://bugs.launchpad.net/mydumper/+bug/1527232/+subscriptions