1 / 25

A proposal for Distributed Query Execution Engine in a Grid Environment to CoDIMS.

A proposal for Distributed Query Execution Engine in a Grid Environment to CoDIMS. Gustavo Gaburro Trevisol Alvaro C. P. Barbosa. Agenda. Introduction; Data Integration Middleware Systems; CoDIMS; Concepts; Proposal; Conclusions. Introduction.

adolph
Download Presentation

A proposal for Distributed Query Execution Engine in a Grid Environment to CoDIMS.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. A proposal for DistributedQuery Execution Engine in a Grid Environment to CoDIMS. Gustavo Gaburro Trevisol Alvaro C. P. Barbosa

  2. Agenda • Introduction; • Data Integration Middleware Systems; • CoDIMS; • Concepts; • Proposal; • Conclusions.

  3. Introduction • Increase of heterogeneous and distributed data; • Demand: necessity of integrated data view; • Solution: Data Integration Middleware Systems.

  4. Data Integration Middleware • Provide from distributed and heterogeneous data sources a single, uniform and homogeneous vision • Developing data integration middleware systems is not a simple task, due to the complexity of: • Supporting multiple data models; • Data semantic integration ; • Query processing strategies; • Transaction control techniques.

  5. Application Layer Scan Join Integration Layer (Middleware) Other Project Data Layer Data Integration Middleware Systems

  6. CoDIMS(Configurable Data Integration Middleware System) • Environment for generation of configurable data integration systems for a specific application; • Characteristics: • Based on framework, components and web services; • Flexible and configurable; • Uses only the necessary and tailored components. • “What you need is only what you get” (wynwyg).

  7. Reading only data sources Updating data sources Incorporating a new component for a specific application

  8. Concepts: Wrappers • Translation of the Native's Data Source Model to the Global/Canonic Data Model; • Communication with the data sources.

  9. Responsible for the processing of PEC (Query Execution Plain); Concepts: MEC (Query Execution Engine) Data Result PEC • A MEC is composed for operators and data types.

  10. In a relational MEC, its operators come from relational algebra; The operators are: Select; Project; Cartesian product; Natural Join. Concepts: MEC

  11. An operation of relational algebra can be implemented using different algorithms; Example: Natural Join Merge Join; Loop Nested Join. Concepts: MEC

  12. It defines the steps in which the operators are executed to process the query; A PEC is composed of operators that MEC can execute. Concepts: PEC (Query Execution Plan)

  13. The PEC structure is a Tree: Concepts: PEC

  14. Data integration Systems • They can be benefited of a Grid environment to increase performance: • Sending wrappers and operators to Nodes of Grid, to execute in a parallel way; • Distributing the execution of Sub-queries; • Distributing the execution of operatoins over sub-results.

  15. Wrapper-Grid Layer[Biancardi 2005] • Incorporating a Wrapper-Grid layer to CoDIMS: • Wrappers Distribution in Grid Nodes, allowing a parallel execution of the sub-queries; • Decrease the execution time of queries.

  16. Results [Biancardi 2005]

  17. Restrictions: • All wrappers are allocated in all Nodes: maintenance difficulty; • Distributing de execution only for sub-queries; • Sub-result from witch sub-query send back to MEC: sequential integration of sub-results;

  18. Proposal

  19. Chronology

  20. Example: Query Execution Application

  21. Example: Query Execution PEC

  22. Implementation • Grid Environment: Globus Toolkit 3; • Development of a sending object module (wrappers e Operators) to remote execute in Grid Nodes. • Problens with 4 do Globus Toolkit release 4; • Configuring the test environment; • Laboratory of Research in Networks and Multimedia (LPRM); • JAVA; • Apache Soap.

  23. Expected contributions • Distribute the integration of sub-results, decreasing the overload in the Query Processing Component (MEC); • Distribute/Allocate Operators in a Grid Environment; • Send dynamically wrappers to Grid Nodes; • Decrease the execution time of queries.

  24. Future Works • Implements a optimizer for distributed queries; • Implements a dynamic scheduler to send wrappers and operators to Grid Nodes to execute; • Incorporate a module execute Queries using pipeline and semi-join.

  25. e-mail: gtrevisol@inf.ufes.br Web Site: http://codims.lprm.inf.ufes.br/ Questions

More Related