Bug#19912988 NDB : ONLINE REORG RELATED ROW CHANGES ARE BINLOGGED

A new value of the reorg flag is passed down to LQH to allow it
to differentiate between :
 - Reorg copy driven operations
 - All other operations

Reorg copy driven operations should not result in SUMA
triggers being fired.

Test ndb_addnode_withbinlog improved to show behaviour with
binlogging :
 - Reorg of table with no concurrent activity results in
   no binlogging
 - Reorg of table with concurrent activity results in
   binlog content

Change-Id: I3cd46575871f720569f521d497d3a6d6b0a860c9

Author: frazerclement

mysql-test/suite/ndb/r/ndb_addnode.result

@@ -56,15 +56,27 @@ insert into t10 values (1,1,1), (2,2,2), (3,3,3), (4,4,4), (5,5,5), (6,6,6),(7,7
 "Table t1 Partition info"
 TABLE_INFO
 PartitionCount: 8
+select count(0) as row_count from t1;
+row_count
+10000
 "Table t2 Partition info"
 TABLE_INFO
 PartitionCount: 8
+select count(0) as row_count from t2;
+row_count
+10000
 "Table t5 Partition info"
 TABLE_INFO
 PartitionCount: 8
+select count(0) as row_count from t5;
+row_count
+10000
 "Table t6 Partition info"
 TABLE_INFO
 PartitionCount: 8
+select count(0) as row_count from t6;
+row_count
+10000
 "Table t6 blob dat Partition info"
 TABLE_INFO
 PartitionCount: 8
@@ -388,9 +400,15 @@ test/def/t10	Unique hash index	37	4	4	15
 "Table t1 Partition info"
 TABLE_INFO
 PartitionCount: 16
+select count(0) as row_count from t1;
+row_count
+10000
 "Table t2 Partition info"
 TABLE_INFO
 PartitionCount: 16
+select count(0) as row_count from t2;
+row_count
+10000
 "Table t3 Partition info"
 TABLE_INFO
 PartitionCount: 16
@@ -400,6 +418,9 @@ PartitionCount: 16
 "Table t5 Partition info"
 TABLE_INFO
 PartitionCount: 16
+select count(0) as row_count from t5;
+row_count
+10000
 select count(0) as row_count from t6;
 row_count
 10000