Tips for troubleshooting record search

This topic includes tips for troubleshooting record search.

Due to the user-specified interaction of this feature (as opposed to the system-controlled interaction of Guided Navigation in which the Oracle Endeca Server controls the refinement values presented to the user), a user is allowed to submit a keyword search that does not match any records. Therefore, it is possible for a user to make a dead-end request with zero results when using record search. Applications utilizing record search need to account for this.

In production systems, these attributes are typically hard-coded at the application level, because the application requires specific search keys to be used for specific functionality.

If an attribute is not enabled for record searching but an application attempts to perform a record search against this attribute, the Oracle Endeca Server successfully returns a null result set. The Dgraph process error log, however, outputs the following message: In fulltext search: [Wed Sep 3 12:28:02 2010] [Warning] Invalid fulltext search key "Description" requested.

The -v flag to the Dgraph causes the Dgraph process to output detailed information about its record search configuration. If you are unsure whether the Dgraph is recognizing a particular parameter, start it with the -v flag and check the output.

Finally, record search can be enabled for standard attributes and for managed attribute values.