Skip to main content

Eclipse plugin: InstaSearch – for quick search


InstaSearch is an Eclipse plug-in for performing quick and advanced search of workspace files. This will index the files and when you search for some file contents, it will look with in this index and the search results will be faster, just like the Goolge instant search. It uses Lucene ( http://lucene.apache.org/ ) for indexing and fast searching of files in the workspace. Each search result file then can be previewed using few most matching and relevant lines. A double-click on the match leads to the matching line in the file.

Main Features

  1. Instantly shows search results
  2. Shows a preview using relevant lines
  3. Periodically updates the index
  4. Matches partial words (e.g. case in CamelCase)
  5. Opens and highlights matches in files
  6. Searches JAR source attachments
  7. Supports filtering by extension/project/working set










Download / Installation

In Eclipse Helios (3.6) please install using the  Eclipse Marketplace from the Help menu
http://marketplace.eclipse.org/search/apachesolr_search/instasearch?filters=tid:31

Alternatively you can install using the update site http://code.inf.unibz.it/instasearch/downloads/

Java 1.6 or newer is required. It is suing the below TimeUnit.Hours, which is available only @ Java 6



Search Tips( check  http://lucene.apache.org/java/1_9_1/queryparsersyntax.html )

  1. If you search the text “MyTestJava”,it will look for My*, My*Java, Test*Java, Java* in files
  2. If you search the text “mytestjava”,it will look for mytestjava in files
  3. Wildcard searches Eg: app* initialize
  4. Excluding words Eg: application -initialize
  5. Limit by location – directory, projects or working set Eg: proj:MyProject,OtherProject  application  init
  6. Limit by filename, extension or modification time   Eg: name:app*  ext:java,xml,txt  modified:yesterday
  7. Search by file name initials (e.g. FOS to find FileOutputStream.java)   Eg: name:FOS
  8. If you are looking for term “index” in “java” files with file name starting with “SearchFacet”, use: index name:SearchFacet* ext:java

Labels:

Comments

Post a Comment

Popular posts from this blog

Check your PF balance

You can check your PF balance from the site :   http://www.epfkerala.in/ Go to the menu :  “ My Epf Balance ” .  This will lead to the url :  http://www.epfindia.com/MembBal.html Select the EPFO office where your account is maintained and furnish your PF Account number.You will be asked to enter your name and mobile number. The given mobile number will be recorded along with the PF Account Number. On successful submission of above information, the details will be sent through SMS to the given mobile number. Please find below some screen shots:
2 comments
Read more

Google Chrome shortcut keys

If you are a Google Chromey guy, please find below the list of shortcut keys for some of the most used features  :-) Find more shortcut keys @  http://www.google.com/support/chrome/bin/static.py?page=guide.cs&guide=25799&topic=28650
4 comments
Read more

ATG Search architectural flow : Search and Index

I would like to explain the high level ATG Search implementation architecture ( for an online store) through the above diagram. In this diagram 1.x denotes the search functionality and 2.x denotes the indexing functionality. I have given JBoss as the application server. Physical Boxes and Application Servers in the diagram ( as recommended by ATG )  : Estore ( Commerce ) Box --> The box with the estore/site ear (with the site JSPs and Java codes). Search Engine Box --> The box with the search engine application running. Indexing Engine Box --> The box with the indexing engine application running. CA (Content Administration) Box --> The box with the ATG CA ear ( where we could take CA -BCC - Search Administration and configure the search projects) . Search Indexer Box --> The box with the ATG Search Index ear ( to fetch the index data from repository). Note that the engine performing indexing will need access ...
7 comments
Read more

ATG Search - performance decisions in Enterprise search

Read more about the basic design decisions for a commerce search setup @  http://tips4ufromsony.blogspot.in/2012/03/basic-design-decisions-for-commerce.html Read more about search engine tuning @  http://tips4ufromsony.blogspot.in/2012/02/atg-search-search-engine-tuning.html Following items will affect search performance:  number of items to be searched, quantity of content for each item, number of meta tags, number of facets, Search Merchandising settings, constraints, number of returned results,... You could find a detailed analysis below : 1. Decide how many search engines you need :   Based on the performance requirement of the ecommerce site, create the Search Project @ BCC - Search Admin and add the search engine hosts. Read more about search project creation and search engine host set up @   http://tips4ufromsony.blogspot.com/2012/01/atg-search-how-to-create-search-project.html . 2. Decide the search indexing properties :   Search i...
Post a Comment
Read more

ATG Search and Search engine activity log

We could use the SearchEngineActivity log files to get the request/response to the search engine from a commerce instance. This folder is located in each commerce instance or the instances from which the call to the search engine is done. The SearchEngineActivity log file folder can be configured @ SearchEngineService component ( /dyn/admin/nucleus/atg/search/routing/SearchEngineService). To get the log files for the search engine calls, you need to specify the SearchEngineService.dumpingRequests as true. Then you need to specify the engineActivityPath as the folder in which you need the SearchEngineActivity logs. Below you could find my SearchEngineActivity log folder. Each successful call to the search engine from the commerce instance will create 5 files in the SearchEngineActivity folder : namely  request, response, search engineinfo, stack trace and response row . Each file name start with a specific sequence. You ...
1 comment
Read more