I am a little bit on the fence as to what exactly you are looking for. Typically, when it comes to debugging data within the CloverDX framework, the data can be either viewed directly in the Designer or as Eva mentioned previously, the edge debug data can be pulled from the debug files. Producing the debug files is a viable option in our open source engine as well. This is an example of how the debugging can be turned on:
Code: Select all
<Edge debugMode="all" fromNode="UNIVERSAL_DATA_READER:0" guiBendpoints="" guiRouter="Manhattan" id="Edge0" inPort="Port 0 (in)" metadata="Metadata0" outPort="Port 0 (output)" toNode="REFORMAT:0"/>
After the graph run, debug files (*.dbg) will be generated (by default) in the Java temp directory and since they contain binary data they need to be further read by CloverDataReader.
Another simpler option is to modify your graph in a way that you fork the data flow at the desired point by SimpleCopy component and write it to some temp file using a writer component.
If none of these options is what you were looking for, kindly clarify a couple of additional details:
- By the Java application, do you mean the CloverDX Designer or a different Java application that you develop?
- If the latter is the case, how do you execute the graph? For instance, by using the runGraphclass.
- Could you elaborate on which part of your transformation requires the edge debug data and how you intend to use them?
- You mentioned that you want to get the data passing through the edge between connected etl components from java code. Could you elaborate more on the "from Java code" part of your question?