If you want to configure logging using the driver, you can use either of the following approaches:
Use a single properties file for all Cassandra connections.
Use a different properties file for each relational map of your native Cassandra data. For example, if you have two configuration files, such asC:\data\db\mydb1.config and C:\data\db\mydb2.config, you can load one properties file for the mydb1.config schema map and load another properties file for the mydb2.config schema map.
Note: You must specify the name and path of the relational map using the SchemaMap property.
If a properties file is specified for the LogConfigFile connection property, the driver uses the following process to determine which file to load:
1. The driver looks for the file specified by the LogConfigFile property.
2. If the driver cannot find the file in Step 1, it looks for a properties file named schema_name.logging.properties in the directory containing the schema map configuration file, where schema_name is the name of the schema map configuration file.
3. If the driver cannot find the file in Step 2, it looks for a properties file named ddlogging.properties in the current working directory.
4. If the driver cannot find the file in Step 3 , it abandons its attempt to load a properties file.
If any of these files exist, but the logging initialization fails for some reason while using that file, the driver writes a warning to the standard output (System.out), specifying the name of the properties file being used.
A sample properties file is installed in the install_dir/testforjdbc.
Use a single properties file for all Cassandra connections.