Bug #40165 trace for sql to ndb-api translation
Submitted: 20 Oct 2008 9:45 Modified: 22 Oct 2008 17:19
Reporter: Oli Sennhauser Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: NDB API Severity:S4 (Feature request)
Version:mysql-5.1-telco-7.0 OS:Any
Assigned to: CPU Architecture:Any

[20 Oct 2008 9:45] Oli Sennhauser 
Description:
Sometimes customers do not know how to implement some features in ndb-api but they  could easily do it in SQL.

So it would be very convenient for them if they could see how a sql command in mysql is translated into ndb-api calls.

How to repeat:
n/a

Suggested fix:
set session ndb_api_trace = 1 | 0
set session ndb_api_trace_file = ndb_api.trace
[22 Oct 2008 17:19] Valeriy Kravchuk 
Thank you for a reasonable feature request.
[22 Apr 2009 9:14] Frazer Clement 
Can you clarify the sort of information you'd like to see traced out.
e.g. give an example output.

Perhaps this would include :
 - SQL parsing, optimisation and planning decision trace?
 - Mapping to the Storage Engine API.
 - Mapping from Storage Engine API calls to NDBAPI calls with rationales
 - Key and attribute data and row count information.
 - Signal traces to/from NDBD nodes

If you can clarify what it is that you would like to see then the scope of the feature request becomes clearer.
Also note that some of the above information is already available today.  Maybe it would be useful to document how these elements can be traced today before looking at what needs to be added.