In previous releases of CAS, the following fatal exceptions resulted in commands finishing without errors or warnings. The CAS service log contained reports of fatal exceptions that occurred at the start of a crawl.
In CAS 11.2, exception handling has been improved by adding proper messaging when the following tasks are run:
Note
Many of these exceptions are also invoked in the deployment template.
The following list contains some of the exceptions that generate informative messages on the command line, CAS Console, or CAS Server log.
Seed property specified in the crawl configuration does not exist or is empty.
ModulePropertiesinOutputconfigin the crawl configuration are missing.Outputconfigis defined, but theOutputdirectoryproperty in the crawl configuration is missing.If
unavailableIncrementalSwitchesToFullCrawlis false and any one of the following scenarios is true:Outputconfigis MDEX-compatible but there are no permissions to access theinputDirectoryoroutputDirectory.The
dimvals.xmlfile is empty whenload_baseline_test_datais run.The
recordstore-config.xmlfile does not hold any configuration when set-configuration task is performed.Outputconfigis MDEX-compatible, butInputDirectoryproperty value does not exist.The
InputFile pathof theDelimitedorEndecaRecordFiledata source does not exist.The precedence rules configuration in the
index-config.jsonis not valid. For example, it does not have an associatedtriggerDimensionValueSpecto a trigger dimension."precedence_rule1" : { "targetDimension" : "product.category", "triggerDimensionValueSpec" : "575", "triggerDimension" : "product.price_range", "isLeafTrigger" : false }
