Hi Eric, Here is brief summary of the Trafodion execution engine code structure. I hope this would help you to set the breakpoint.
cli directory contains the implementation of Call level Interfaces from the application like sqlci, mxosrvr. executor directory contains the implementation for all theTask Control Blocks (TCBs). These Tcbs tasks are scheduled by the scheduler (ExScheduler.cpp) to execute the given query. exp directory contains the implementation of the all the expressions that are evaluated as part of the executing above the tasks. In case of Hbase, the executor tasks implementation are in ExHBaseSelect.cpp ExHBaseAccess.cpp and ExHbaseIUD.cpp These tasks issue hbase API by transitioning from JNI to java. JNI portion of the code is HBaseClient_JNI.cpp and all the related java files are in the same directory. Try putting a breakpoint in the above JNI and java files. Selva On Wed, Jul 15, 2015 at 1:26 PM, Eric Owhadi <[email protected]> wrote: > I am getting familiar with the Trafodion code. In particular, I am > interested to see the hbase interfaces. So I installed the dev environment, > added Eclipse with the CDT pluggin to be able to debug both C++ and java > code. > > I was hoping to set a breakpoint at: > ExHBaseSelect.cpp, line 68, where I would have guessed > case SCAN_OPEN: > would be hit when I do from sqlci: > select * from trafodion.usr.t3; > > I set dbg on all mx* processes. > > No success, the code won't breat on the break point. > > Any clue would be greatly appreciated :-), > Regards, > Eric Owhadi >
