Information about the search application Lucene

[Zia 7]

I am looking for an information about the search application Lucene. I am very much interested in knowing about it. I just know that Lucene is a service optimized by Akamai EdgeComputing based on Jakarta Lucene, an open source search application created by the Apache Software Foundation. I am posting here expecting that you guys will help me more in collecting an information. Please provide detailed information about the same.

[X-Ray]

Jakarta Lucene is a library of full text search engine, completely written in Java. The engine uses powerful search algorithms, accurate and effective. Lucene includes the following features:

• Multilingual Search Capability
• Indexing any text file (eg HTML) or any file converted to text
• Supports ranked search to return the best results in the first
• Querying Boolean and phrase
• Ability to search by field (s), that is to say that research can focus on the title, author, content, etc..
• Allows search by date range to access the information in time

[Shell]

Creating an index file is an essential step towards the implementation of a Search Application with Lucene. An index is a special database, which contains a compiled version of the content of a website. When the Lucene indexing API automates the creation of the index, the content must be included in text format. For each type of document to be included in an index, the client must use a scanner or a fan. Lucene analyzer includes a sample HTML that receives a URL or location of a file on a hard drive, parses, extracts the text of HTML tags and creates a Java object String class that is passed to the API of Lucene indexing.

[Khushal]

To better understand how the indexing, consider the example of Akamai and its use Lucene for search sites. The first stage of the indexing process is to identify the content to be indexed. Lucene creates a "Document object" for each piece of content indexed, that is to say a series of name-value pairs called fields. For example, one field may be the title, the name-value pair will be "Title" - Home Akamai. A "form object" is assigned to each field and determines if the text associated with the field should be indexed, stored and / or be a token.

[DllD]

The "form object" determines how Lucene should use the information field:

• Indexed: when a field is indexed, then there may be searched. For the implementation of Lucene Akamai.com on the "Title" field has been indexed so that the user input can be sought in the Title field. Lucene allows you to define which fields are indexed and searched by default which are reserved for smaller research.
• Stored: when a field is stored in the index, which means that its contents can be displayed in search results. The summary linked to a page is often stored in the index, as is the case for the implementation Akamai.com. A brief description can be integrated with the title page in the search results.
• Token: when a field is the subject of a token, that means it goes through an analyzer that converts the content into a sequence of tokens. The token is the basic unit of indexing, and represents an individual word to index. In the process token, the parser extracts the text to be indexed by applying the logic of transformation (removing stop words such as "one" or "the" indexing roots, converting all text to lowercase research-insensitive, etc..). The index size is reduced, because the text associated with the fields is limited to its essential elements.

[Allan.d]

The last step of the process of indexing is to use the Lucene IndexWriter object to create the index. The purpose IndexWriter uses a parser to reprocess the text entered. Note that the analyzer is used to create and search the index. The search text should be treated the same way that the indexed text, it is essential to use the same analyzer for indexing and searching. Akamai.com uses Lucene Analyzer Standard.

[Warner]

Lucene is written entirely in Java, it can be fully deployed and executed on EdgePlatform, Akamai EdgeComputing using the service. In this model, the client displays the search index and the rest of the search application (usually including a search page and a page of search results) in a WAR file, which will be deployed and run from all J2EE application servers Akamai around the world.

[MELTRONICS]

Deployed on the platform, Akamai EdgePlatform, Lucene can be fully executed as a demand service without any application execution time to the origin. Therefore, it is possible to continue the search with Lucene, even when the source is unavailable. Figure 2 (below) presents a diagram of the end user queries to the search performed on Akamai.com. As with all applications deployed with Lucene search powered by Akamai EdgeComputing, the application is performed wholly EdgePlatform, without sending requests to the origin.