Skip to main content
T
TomU23-Emerald IV
23-Emerald IV
May 14, 2014
Question

host indexing engine (Solr)

  • May 14, 2014
  • 1 reply
  • 727 views
I'm looking for opinions about the "host indexing engine (Solr)" available with Windchill 10.2. What are the benefits of using this over normal database searches? For smaller companies (< 50 users), does the benefit justify the overhead and potential nightmares during future upgrades and/or rehost scenarios?

I come across a knowledge base article that said the index search only indexes the latest iteration of each object (CS137106<).">https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS137106>). The search methodology also appears be very different (CS41207<">https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS41207> and CS169814<).">https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS169814>).

Thoughts?

Thanks,

Tom U.

1 reply

M
MikeLockwood22-Sapphire I
22-Sapphire I
May 19, 2014
We've done bulk indexing of production multiple times with various configurations - currently we have it backed out and have deleted the results. Can discuss our experience w/you if you like.

Primary issues:

1. Our primary use case is to find "where used" info for any typed-in document / part number. When there are indexing failures there is no way to find out which objects they are - and so no way to trust that searches are complete.

2. We've seen inconsistent, bizarre results with wildcards when indexing is enabled. Have also done many tests with a large number of criteria - hard to get confidence in the results when indexing is added to the mix.

3. When indexing is enabled, users have to change their preference each time they want to use it - quite a few clicks. Would be much better if the default was not to use the index search and users could check a box if they wanted to.

Searching here
[cid:image001.png@01CF7341.2630BAF0]

results in the entered value here
[cid:image002.png@01CF7341.2630BAF0]

Terms & ConditionsAccessibility statement