About Queries With Mixed OLT And Latin-1 Subjects
(Doc ID 2356551.1)
Last updated on FEBRUARY 07, 2019
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.3 and later
Information in this document applies to any platform.
Qn1:How to Find Indexed Terms that are Unknown to OLT?
Qn2:Dgidx is run using 16 core hardware and "--thread 16" parameter
Would performance be better when specifying "--thread auto" at 11.3.1, more than specifying "--thread 16"?
Qn3:Even when ITEM_CODE contains a general word with half-width characters (for example: word123), as long as it doesn’t have a character which would be considered as a word boundary, it won’t be split?
(i.e. it will not be split into “word" and "123", correct?)
Qn4:When removing "-" and other punctuation from search_chars.xml, creating index as ITEM_CODE(example：A-123) in English:
We understand that it will be separated into "A" and "123", then it is indexed.
When there is no definition in search_chars.xml at all, what kind of characters･symbol divide the strings?
Qn5:If OLT parse target (for example: ITEM_CODE) is only using half-width characters, does it consider any character that is neither alphanumeric nor a non-spacing mark to be a word boundary, similarly to Latin 1 parser?
Qn6:When OLT parse target is only using half-width characters, whichever I use Latin1/English or OLT/Japanese to create index, will it match the way that it is parsed in an OLT Japanese query string?
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