Bug 68519 - [Search] [Scalability] Put limits upon wildcard search results
Summary: [Search] [Scalability] Put limits upon wildcard search results
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-24 14:16 EDT by John Camelon CLA
Modified: 2020-09-04 15:21 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Camelon CLA 2004-06-24 14:16:43 EDT 
1. * should not be allowed as an input in the search dialog, particularly in 
use w/Any Element.  
2. A user preference should be added (defaulting at say 1000) limitting the 
number of search results found.
Comment 1 John Camelon CLA 2004-08-17 10:24:31 EDT 
Moved off to 2.1
Comment 2 Andrew Niefer CLA 2005-04-25 13:59:06 EDT 
with search moving to index, is this still an issue?
Comment 3 Bogdan Gheorghe CLA 2005-04-25 15:28:47 EDT 
Well it's no longer a burden on the parser, just on the scalability of Eclipse's
UI facilties.

I've done searches with the new search engine that got 30k matches within 5
seconds and it seemed to be OK. 

However, I think it's still a valid requirement - how useful is being able to
return 50K matches?
Comment 4 John Camelon CLA 2005-04-25 15:33:42 EDT 
The problem is that we will run out of memory w/large workspaces.  
That being said, we don't know what a good default limit should be for all clients.
I'm OK with this being closed or lowered in priority.
Comment 5 John Camelon CLA 2005-04-25 21:38:01 EDT 
FYI, if I do a search on all occurrences of types in the JDT (including matches
in external jar files) it spins until doomsday.