My Oracle Support Banner

JDBC CAS Crawler Error When Record Store Configuration IdPropertyName Is Not Endeca.Id (Doc ID 2128301.1)

Last updated on FEBRUARY 08, 2019

Applies to:

Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.0 and later
Information in this document applies to any platform.

Symptoms


JDBC CAS Crawler error when Record Store Configuration idPropertyName is not Endeca.Id

We are building a new JDBC CAS crawl.  In our application the unique identifier (or record spec property) is "common.id". In the CAS Record Store configuration it is desired to set the idPropertyName as "common.id" to match the record spec property, which the CAS Developer's Guide says is possible to do instead of using the default "Endeca.Id" property.

However, after changing the idPropertyName in the crawl config per the documentation to use "common.id", the following error is thrown by CAS:

Other types of CAS crawls have been able to successfully use a different idPropertyName property, until using the CAS JDBC Crawler. 



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.