Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. Internally each Indexer will make calls to the SearchEngineUtil which handles all the intricacies of the engine implementation.
For the purpose of this document, we won't delve into the internals of SearchEngineUtil. But suffice it to say that all traffic to and from the search engine implementation passes through this class, and so when debuging problems it is often beneficial to enable debugging level logging on this class. Once an Indexer instance has been obtained, searches are performed by calling its search SearchContext searchContext method.
The result of the search method is an instance of the com. Hits class. This object contains any search results in the form of an array or list of com. Document instances. The results display typically involves iterating over this array. Each Document is effectively a hash map of the indexed fields and values. Facet rendering is done by getting Facets from the SearchContext after the search has completed and passing each to a template as defined by the FacetConfiguration:.
A Facet's details are obtained by calling it's getFacetCollector method which returns an instance of com. FacetCollector class. The primary responsibility of this class is to in turn provide access to TermCollector instances primarily by calling the getTermCollectors method, but also by getting a TermCollector by term value using the getTermCollector String term method. There will be a TermCollector for each term that matches the search criteria, as well as the facet configuration.
And finally, the com. TermCollector class provides the getFrequency method. Rendered facet views i. At the core of all content management lies search and so I'm really excited about the potential of this new search API. As we work on 6. What follows is a list of features provided by Faceted Search via the Search Portlet.
Aggregation of assets into a single result set : Results from all portlets are returned as a single set and the relevance is normalized among the entire set, regardless of type i. Searching has a more linear cost due to the fact that only a single query is performed. Searching is therefore faster, more intuitive, and more relevant. In previous versions of the portal, each Portlet implemented it's own search and returned a separate result set which resulted in several issues: Each portlet invoked it's own query, and each portlet was called in turn resulting in a single portal request generating potentially N queries to the index each with it's own processing time.
This lead to increased time to produce the final view. Depending on the order of how portlet searches were called, the results near the bottom may be the most relevant and due to positioning could appear to have less value than those of portlets positioned physically higher up on the page.
These defaults make finding content on the most common facets simple and powerful. Facets details are displayed in the left column of the search portlet and provide information in context of the current search. Asset Type : Performing a search for the term "htc" may return Asset Type facet details which appear as follows: The value in parenthesis is the frequency with the term appearing on the left.
You may notice that as you perform different searches, the Asset Type terms may disappear and re-appear. When a term does not appear it means; a it was not be found among the results, b it did not meet the frequency threshold property, or c it was beyond the maxTerms property these properties will be discussed more later.
Asset Tags : If tags have been applied to any document which appear in the result set, they may appear in the Asset Tag facet: Note : Not all tags may appear. In the example above, there are many more than the 10 tags that are listed, but the default configuration for this facet is to show the top 10 most frequently occuring terms as set by it's maxTerms property.
Asset Categories : If categories have been applied to any document which appear in the result set, they may appear in the Asset Categories facet: Note : Not all categories may appear.
In the example above, there are many more than the 10 categories that are listed, but the default configuration for this facet is to show the top 10 most frequently occuring terms as set by it's maxTerms property.
Modified Time : All documents appearing in the result set should have an indexed field called "modified" which indicates when the document was created or updated. The Modified Time facet is a range facet which provides several pre-configured ranges as well as an option for the user to specify a range. All results in the subsequent query should then fall within this range. Drill down : The next feature allows refining results by selecting terms from each facet thereby adding more criteria to the search to narrow results referred to as "drilling down" into the results.
Clicking on terms adds them to the search criteria currently only one term per facet. They are then listed in what is known as "token style" just below the search input box for convenience and clarity.
Clicking the any token's X removes it from the currently selected criteria. Selected the tag "liferay": e. Additionally, selected the type "Web Content": Advanced operations : These are supported directly in the search input box. Most of the advanced operations supported by Lucene are supported with only slight variations.
Searching in specific fields : By default, searches are performed against a long list of fields this is different from Lucene which searches a single specific field by default. Sometimes you want results for a term within a particular field. Wildcard Searches : The Search Portlet supports single and multiple character wildcard searches within single terms not within phrase queries.
To perform a single character wildcard search use the "? The single character wildcard search looks for terms that match that with the single character replaced. For example, to search for "text" or "test" you can use the search: te? An additional optional parameter can specify the required similarity. The value is between 0 and 1, with a value closer to 1 only terms with a higher similarity will be matched.
Range Searches : Ranges allow one to match documents whose field s values are between the lower and upper bound specified by the range. Ranges can be inclusive or exclusive of the upper and lower bounds. Skip to content. Sign in Sign up. Instantly share code, notes, and snippets. Last active Dec 24, Code Revisions 9 Forks 1. Embed What would you like to do? Embed Embed this gist in your website.
Share Copy sharable link for this gist. Learn more about clone URLs. Download ZIP. Create a folder PluginSDK and unzip the above zip.
Create a file with name build. Its simple…. Click the bellow screen shot for the details 4. Add the bellow lines in the above file app. Now you are ready for development. Follow the next Liferay IDE. Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here
0コメント