Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 377300

Summary:

global search - the caching confuses me...what is the lifecycle?

Product:

[ECD] Orion

Reporter:

Susan McCourt <susan>

Component:

Client

Assignee:

libing wang <libingw>

Status:

RESOLVED WONTFIX

QA Contact:

Severity:

normal

Priority:

CC:

john.arthorne, libingw

Version:

0.5

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
screenshot of stale search results	none

Description Susan McCourt

2012-04-20 12:51:25 EDT

Created attachment 214312 [details]
screenshot of stale search results

In bug 377238, about 50 of my files got corrupted when I replaced "nihilo" with "claro".  After seeing some confusing things in git status, diffs that did not reflect what I had updated manually, etc., I decided to reset my working directory and start over.

Then I global searched on "nihilo" expecting to see a bunch of hits, since I had reset the files in git.  

But global search told me I had no hits.  When I searched on "claro" to see what happened, I saw a bunch of hits, but they were all gray (out of date?).  I reloaded the page, thinking this would perform the search again.  But it did not.

So my question is...when I am looking at search results (like the ones attached) and most everything is gray, how do I redo the search against the latest content?  In the moment, I expected reload to rerun the search, but I recall discussion about caching strategies....

Comment 1 Susan McCourt

2012-04-20 12:56:10 EDT

I think it must be timing dependent, but this causes really strange results if you are in the middle of bulk changes that have manual intervention.

I refreshed my page and went from 40 stale hits to 16 stale hits.  I would have expected that if it refreshed, it would have been current, vs. partially current.

Then when I refreshed, I had 2 stale hits.  

Eventually it cleared up.

Comment 2 John Arthorne

2012-04-20 13:22:35 EDT

It's not a matter of caching. The search runs against the index, and index is updated periodically in the background. It can take a couple of minutes for the indexer to catch up to your changes. The grey result means the index found a match, but when we actually retrieved the file we found no match.

Comment 3 libing wang

2012-04-20 13:52:00 EDT

I think Susan/user's confusion is that she did not know what "grey out" means.
Should we pop up a hint saying "There are files not synced yet with search engine, please wait" as status message? Ideally if we can get notifications from server that a speficic workspace got resynced, we can reload the result page automatically.

Comment 4 Susan McCourt

2012-04-20 16:12:35 EDT

Actually, I knew that gray meant it was stale.
I wasn't so much thinking about the index, but I guess what I wanted was to  force a reindexing because I'd just made a huge swath of changes and I wanted to make sure I'd gotten them all.

Comment 5 John Arthorne

2015-05-05 14:53:52 EDT

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html