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

Bug 335143

Summary:	[Help][Search] Use prebuilt indexes directly instead of merging them into one
Product:	[Eclipse Project] Platform	Reporter:	Holger Voormann <eclipse>
Component:	User Assistance	Assignee:	platform-ua-inbox <platform-ua-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	cgold, remy.suen
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Holger Voormann

2011-01-23 21:48:50 EST

Is:
To compute the search results of the very first query all contributed prebuilt indexes are merged into one master index which is stored in the configuration area (configuration/org.eclipse.help.base/index). Then the master index is used to compute the search result for the very first and later queries.

Should:
The master index should only contain indexed help content of plug-ins without prebuilt indexes. Each query is executed on each index and the search results are merged.

Contras:
Execution time for a query (except the very first one) will increase but will still be fast enough (< 1 second).

Pros:
(My customer has a couple of very large help content plug-ins with 15 MB indexes; there is only one Eclipse installation for all Linux users but the master index will be created for each user in his or her configuration area. Due to home directories on slow network drives merging the prebuilt indexes into the master index takes a couple of minutes.)
- Less disk space (no duplicates per user and configuration)
- Faster first query (no master index files have to be created)
- Faster querying after installing or updating

Comment 1 Chris Goldthorpe

2011-01-24 16:01:41 EST

It would be interesting to get some hard data on the search times with and without merged search indexes. I'll see if I can find time to prototype this.

Comment 2 Lars Vogel

2019-09-24 13:49:48 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.