Difference between revisions of "Search Framework 2.0"

From Gcube Wiki
Jump to: navigation, search
(Search 2 Framework)
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Search 2 Framework ==
 
== Search 2 Framework ==
Search Framework consists of all the components that offer information retrieval functionality in a gCube infrastructure. Queries expressed in the [[http://www.loc.gov/standards/sru/specs/cql.html| Contextual Query Language]], are submitted to the entry point of the Search framework, the Search System Orchestrator. Search Orchestrator will first use the gCQLParser to parse the query submitted. Then it will involve the Search Planner to produce a plan sufficient for answering the query. The plan produced will be given as input to the Workflow Engine. Workflow layer abstracts over the low level details associated with the Execution Engine. As a result, workflow engine generates the execution plan that is realized by the Execution Engine. The entities invoked by the execution engine, in order to gather the results for the initial query, are the Data Sources and the Search Operators. Figure 1 shows the interactions between the different layers that compose the query answering process.
+
Search Framework consists of all the components that offer information retrieval functionality in a gCube infrastructure. Queries expressed in the [http://www.loc.gov/standards/sru/specs/cql.html Contextual Query Language], are submitted to the entry point of the Search framework, the [[Search Orchestrator | Search System Orchestrator]]. Search Orchestrator will first use the [[gCQLParser]] to parse the query submitted. Then it will involve the [[Search Planner]] to produce a plan sufficient for answering the query. The plan produced will be given as input to the [[WorkflowEngine | Workflow Engine]]. Workflow layer abstracts over the low level details associated with the [[ExecutionEngine | Execution Engine]]. As a result, workflow engine generates the execution plan that is realized by the Execution Engine. In order to produce the results for the initial query, the Execution Engine will invoke specific instances of [[Data Sources]] and [[Search Operators]]. The final outcome of the execution stage is a [[GRS2 | gRS2]] result set endpoint reference(EPR). This result set EPR will be used by the client that submitted the query, to obtain the results. Figure 1 shows the interactions between the different layers that compose the query answering process.
 +
 
 +
[[Image:Search2Framework.jpg|frame|center|Figure 1. Search Workflow]]
 +
 
 +
In the following sections we discuss the functionality, implementation details and the key design choices for each layer of the search process:
 +
 
 +
* [[gCQLParser]] - Small introduction for the Contextual Query Language, CQL enhancements in the gCube framework and description of the parser's implementation.
 +
* [[Search Orchestrator]] - Describes the entry point of the Search Framework, which is implemented as a gCube Web Service.
 +
* [[Search Planner]] - Design, algorithms and techniques applied in the search planning/optimization phase.
 +
* [[WorkflowEngine | Workflow Engine]]
 +
* [[ExecutionEngine | Execution Engine]]
 +
* [[Data Sources]] - Description of the Data Sources involved in a search operation.
 +
* [[Search Operators]] - Description of the functionality and implementation of the Search Operators.

Latest revision as of 16:33, 23 July 2013

Search 2 Framework

Search Framework consists of all the components that offer information retrieval functionality in a gCube infrastructure. Queries expressed in the Contextual Query Language, are submitted to the entry point of the Search framework, the Search System Orchestrator. Search Orchestrator will first use the gCQLParser to parse the query submitted. Then it will involve the Search Planner to produce a plan sufficient for answering the query. The plan produced will be given as input to the Workflow Engine. Workflow layer abstracts over the low level details associated with the Execution Engine. As a result, workflow engine generates the execution plan that is realized by the Execution Engine. In order to produce the results for the initial query, the Execution Engine will invoke specific instances of Data Sources and Search Operators. The final outcome of the execution stage is a gRS2 result set endpoint reference(EPR). This result set EPR will be used by the client that submitted the query, to obtain the results. Figure 1 shows the interactions between the different layers that compose the query answering process.

Figure 1. Search Workflow

In the following sections we discuss the functionality, implementation details and the key design choices for each layer of the search process:

  • gCQLParser - Small introduction for the Contextual Query Language, CQL enhancements in the gCube framework and description of the parser's implementation.
  • Search Orchestrator - Describes the entry point of the Search Framework, which is implemented as a gCube Web Service.
  • Search Planner - Design, algorithms and techniques applied in the search planning/optimization phase.
  • Workflow Engine
  • Execution Engine
  • Data Sources - Description of the Data Sources involved in a search operation.
  • Search Operators - Description of the functionality and implementation of the Search Operators.