Bug #35908 NDBAPI : Old API ordered Index scan on secondary index not ordered
Submitted: 8 Apr 2008 17:21 Modified: 9 Jul 2008 8:55
Reporter: Frazer Clement Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: NDB API Severity:S1 (Critical)
Version:5.1-telco-6.3+ OS:Any
Assigned to: Frazer Clement CPU Architecture:Any

[8 Apr 2008 17:21] Frazer Clement 
Description:
Ordered index scan using old api should return tuples in-order, but it can return tuples out of order. 

How to repeat:
Run testOIBasic with fix to bug 35876.

Ordered scan on a secondary index fails verifyOrdering() check.

Suggested fix:
Ensure correct info is requested from kernel to perform merge sort in API.
[8 Apr 2008 22:19] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/45091

ChangeSet@1.2544, 2008-04-08 23:18:05+01:00, frazer@forth.ndb.mysql.com +1 -0
  Bug #35908 : Ordered index scan should return tuples in order
  
  Retrieve indexed columns by using column mask from index table, not from base table.
[8 Apr 2008 23:38] Frazer Clement 
Pushed to mysql-5.1-telco-6.2-merge, mysql-5.1-telco-6.3.
[12 Apr 2008 16:57] Jon Stephens 
Documented in the 5.1.24-ndb-6.3.13 changelog as follows:

        Some ordered index scans could return tuples out of order.

Left in Patch Pending status, pending additional merges.
[9 Jul 2008 8:55] Jon Stephens 
Since this is marked telco-6.3+, there appears to be no need for additional documentation. Closed.
[12 Dec 2008 23:27] Bugs System 
Pushed into 6.0.6-alpha  (revid:sp1r-frazer@forth.ndb.mysql.com-20080408221805-29697) (version source revid:jonas@mysql.com-20080808094047-4e1yiarqa2t3opg3) (pib:5)