What Are The Implications Of Modifying Attribute Mapping For Source When Docs Exist In SES
Last updated on MARCH 08, 2017
Applies to:Oracle Secure Enterprise Search - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
What are the implications vis-a-vis previously crawled and indexed documents of changing the attribute mapping for a source ?
A source has been set up (in your case, this is UCM -- WebCenter Content, using SESCrawlerExport component of UCM).
Custom search attributes have been defined.
Custom attribute mapping for the source has been defined.
UCM snapshot taken and crawled by SES, so SES has indexed all documents for this UCM source.
What happens to existing documents (in SES) for the source when the attribute mapping for the source is modified ?
(No change has been made to the content of the document, so no new information is coming from UCM).
The change is only within SES, i.e. to the attribute mapping.
Question 1 :
If doc attribute A1 was previously mapped to search attribute S1, and now we change that to map doc attribute A1 to search attribute S2,
how can we make sure that SES reflects this new mapping for previously indexed documents ?
No change in the corresponding row of EQ$ATTR_VAL_TAB has been observed.
Question 2 :
Doc attribute A1 was previously mapped to search attribute S1, and documents exist with information in EQ$ATTR_VAL_TAB reflecting this mapping.
then, we change the source attribute mapping to map A1 to search attribute S2.
We now delete search attribute S1.
a) Will S1 now no longer show up in the query UI as a choice for attribute filtering ?
b) Will filtering on S2 include previously indexed documents (indexed when the mapping was from A1 to S1) ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms