Excerpt |
---|
Contains how-to information referenced from other chapters in this guide. |
...
Table of Contents | ||||
---|---|---|---|---|
|
...
Code Block | ||
---|---|---|
| ||
# Move to the directory where you want to install the Trafodion source code. cd mysource # Clone the Trafodion source code git clone git://gitgithub.com/apache.org/incubator-trafodion.git # Change to the source-tree directory cd incubator-trafodion # Register your fork as a remote branch git remote add <your-github-id>_fork git@github.com:<your-github-id>/incubator-trafodion |
Code Block | ||||
---|---|---|---|---|
| ||||
# Move to the directory where you want to install the Trafodion source code. cd mysource # Clone the Trafodion source code git clone git://gitgithub.com/apache.org/incubator-trafodion.git # Register your fork as a remote branch cd incubator-trafodion git remote add trafdeveloper_fork git@github.com:trafdeveloper/incubator-trafodion |
Create Task Branch
...
You can force Trafodion to abort and core dump on a specific error. Use this method.
- edit ms.env file (before running sqlci)
...
:
If you want to catch errors in processes other than sqlci, edit the $MY_SQROOT/etc/ms.env file and add the following line
Code Block ABORT_ON_ERROR=<error-number>
There is only one error number that will take effect, so if you have two lines of ABORT_ON_ERROR, the last one wins.
If you want to catch errors on all nodes of the cluster, copy the edited file to all nodes of the cluster:
Code Block pdsh $MY_NODES $MY_SQROOT/etc/ms.env $MY_SQROOT/etc
If you want to catch errors in the sqlci program, export this environment variable, then run sqlci:
Code Block language bash export ABORT_ON_ERROR=<error-number> sqlci
win.This will help you to debug when a query run into a SQL error, and it is hard to figure out which code path it runs into.
...
Note that the changes in ms.env will affect all processes on that node and therefore could disrupt operation of your cluster.