Last updated on FEBRUARY 21, 2017
Applies to:Identity Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Following are use case related to stopwords in text index which customers can encounter:
1. Access Request Catalog search using Stopwords (like a, d, I, s, t etc.) is very slow, and sometimes leads to UI going to hang state.
2. Catalog Search of entitlements with "_" (underscore) character are not displayed correctly. A catalog search for items with an underscore returns incorrect results.
Example:- Create several requestable items with names like A_Req01, A_Req02, B_Req01, C_Req01. After catalog sync is done, search the catalog for A_Req*.
Expected results would be: A_Req01 and A_Req02, but instead, all of the above items are returned.
"A_Req01" is interpreted as "A followed by Req01" and since A is a stopword, this transforms to just "Req01" which matches any of "<something>_Req01".
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