I noted the other day that a developer I was working with used the prefix "old:" in the search box. I'd never seen this before. He mentioned it was something he'd picked up from someone else. I got curious and opened up the activitiy (pzSearchResults) where lo and behold I found references to the abiltiy to switch between the old and new searches, where available.
I guess my real question here is - does anyone know if this is documented somewhere?
Are there any plans for this to go away or plans to stop Lucene from working?
***Updated by moderator: Lochan to add Categories***
As far I know old: is neither lucene nor elastic search, it is just a notation we use to get search results from Database instead from the indexing files. However getting results from DB directly by using old: could be a costly process sometimes, so we go for indexing and store as file system.
I can understand that this hack shouldn't be available atleast when indexing is completed and index/search are enabled. So as I understand you want to get the search enhanced and avoid such hacks in PRPC? Please correct if I am wrong.
Posted: 6 years ago
Posted: 6 Oct 2016 7:02 EDT
Joel McLeish (JoelMcLeish)
Senior Director, Service Assurance
It is recommended not to use the "old:" due to it directly searching the database, however when a search fails but it is accessable via the "old:" prefix and it is not an internal rule its a good indicator if there are issues with the normal search.
Posted: 6 years ago
Posted: 7 Oct 2016 7:42 EDT
Rajiv Nistala (nistr)
Senior Manager - Engineering
I agree and it is not recommended to use this "hack". The normal full text search, when it doesn't have the Lucene or Elastic Search indices accessible, will fall back to DB query based search. When that happens, the search results will no longer have the drop down filters in the UI.
So ideally, you should never have to use old:. This has been around since multiple major releases of the product and some developers are picked it up and passed it on to others to avoid the setting up on the full text search index via the search landing page.
Note that this is available on for searches in the designer studio but not in other end user portals like manager or user.