Post Merge Fix

Update the result file of the ndb_statistics1 test. The change
is due to fix for Bug #23259872: OPTIMIZER CHOOSES TO USE NON
PRIMARY INDEX, EVEN THOUGH COST IS HIGHER. The optimizer now
chooses a range access rather than a ref access in this
particular case

Author: arnabray21

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

@@ -141,7 +141,7 @@ id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
 EXPLAIN
 SELECT * FROM t10000 WHERE J = 0 AND K < 1;
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
-1	SIMPLE	t10000	ref	PRIMARY,J	J	5	const	2	Using where with pushed condition
+1	SIMPLE	t10000	range	PRIMARY,J	J	9	NULL	2	Using where with pushed condition; Using MRR
 EXPLAIN
 SELECT * FROM t10000 WHERE J = 0 AND K BETWEEN 1 AND 10;
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra