Cassandra Loader Configuration

Configuration Logic

The loader's configuration is set in the config.ini file which includes the loader and session configuration sections. Each section includes configuration parameters, such as queue size, number of threads, etc. which can be updated during the loader's fine-tuning optimization process.

The loader execution modes are:

Note that writing into the Cassandra DB can be disabled for testing purposes. This is controlled by the IS_NOP loader's configuration parameters.

Work by Priority

The loader works according to the following priority:

• Batch_process
  • Look for [LU type]_batch_process_loader section.
  • If not exist, user batch_process_loader section.
  • if not exist, use default_loader section.
• Parser
  • Look for [LU type]_[parser name]_loader section.
  • if not exist, use parser_loader section.
  • If not exist, user default_loader section.
• iidFinder
  • Look for iid_finder_loader section.
  • If not exist, use default_loader section.

The session works according to the following priority:

• Fabric internal
  • Use the default_session section.
• Batch_process
  • Look for [LU type]_batch_process_session section.
  • If not exist, use batch_process_session section.
  • If not exist, use loader_session section.
  • If not exist, use default_session section.
• Parser
  • Look for [LU type]_[parser name]_session section.
  • If not exist, use parser_session section.
  • If not exist, use loader_session section.
  • If not exist, use default_session section.
• iidFinder
  • Look for iid_finder_session section.
  • If not exist, use loader_session section.
  • If not exist, use default_session section.