-
Notifications
You must be signed in to change notification settings - Fork 35
Logging
timrdf edited this page Feb 5, 2011
·
32 revisions
Two types of logging. The first one always happens, the second should rarely happen.
$CSV2RDF4LOD_HOME/bin/convert.sh and $CSV2RDF4LOD_HOME/bin/convert-aggregate.sh always log messages to:
CSV2RDF4LOD_LOG="doc/logs/csv2rdf4lod_log_e${eID}_`date +%Y-%m-%dT%H_%M_%S`.txt"
The number of logs in this directory is asserted as conversion:num_invocation_logs in the aggregated data dump Turtle file publish/<dataset-id>-<version-id>.ttl
In debugging situations, I might have you turn this on.
The Java implementation uses java.util.logging to log.
Turning logging on is parameterized by the CSV2RDF4LOD_CONVERT_DEBUG_LEVEL environment variable and takes affect within $CSV2RDF4LOD_HOME/bin/convert.sh:
javaprops="-Djava.util.logging.config.file=$CSV2RDF4LOD_HOME/bin/logging/finest.properties"
#javaprops=""
CSV2RDF4LOD_HOME/bin/logging/ contains fine, finer, and finest.properties.