Jihoon Son created TAJO-367:
-------------------------------
Summary: Separate the locality information from Fragment
Key: TAJO-367
URL: https://issues.apache.org/jira/browse/TAJO-367
Project: Tajo
Issue Type: Improvement
Components: master, storage, worker
Reporter: Jihoon Son
Fix For: 0.8-incubating
Fragment is designed to represent a portion of the abstracted input source.
However, since It is currently used for the task scheduling and the task
allocation, it includes the locality information as well as the abstraction of
the input data.
The locality information is used only in the task scheduling, and thus the
locality information should be separated from Fragment.
The locality information is used in the task scheduling to assign tasks to
workers closes to the data regardless of the kind of the storage layer.
To consider input data and their locality in the task scheduler, we need to
design a new class including a Fragment and the locality information such as
FragmentWithHost.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
