Users have the ability to analyze issues or problems with Datameer's JDBC-based:
- Import jobs
- Export jobs
This can be accomplished by turning on debug logging for the artifacts.
Debug Logging for All JDBC Artifacts
Add to the following lines to the log4j.properties file
Reboot the Datameer server.
Example log printout:
These log entries can be found in the
job.log of the
job-trace-log when Datameer is configured in the local execution mode. They can be found in the YARN application logs when Datameer is configured to execute against Tez, Spark, or MapReduce.
Debug Logging for Specific Jobs
You can also configure debug logging on the job level to target specific artifacts. A reboot of Datameer isn't required.
- Create a new artifact or edit an existing artifact.
- On the Schedule page, expand the Advanced section.
- From the Default log severity menu, select Debug.
In the Logging Customization field, enter the following properties:
- Save the artifact.