tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihoon Son (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAJO-269) Change the de/serialization protocol of LogicalPlan of QueryUnitAttempt from Json to ProtocolBuffer
Date Sun, 20 Oct 2013 08:02:41 GMT

     [ https://issues.apache.org/jira/browse/TAJO-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jihoon Son updated TAJO-269:
----------------------------

    Description: 
In the current implementation, the logical plan is serialized into a JSON object and sent
to each worker.
However, the transmission of JSON object incurs the high overhead due to its large size.
ProtocolBuffer is a good alternative because its overhead is quite small and already used
in other modules of Tajo.

  was:
In the current implementation, the logical plan is serialized into a JSON object and sent
to each worker.
However, the transmission of JSON object incurs the high overhead due to its large size.
ProtocolBuffer is a good alternative because it's overhead is quite small and already used
in other modules of Tajo.


> Change the de/serialization protocol of LogicalPlan of QueryUnitAttempt from Json to
ProtocolBuffer
> ---------------------------------------------------------------------------------------------------
>
>                 Key: TAJO-269
>                 URL: https://issues.apache.org/jira/browse/TAJO-269
>             Project: Tajo
>          Issue Type: Task
>          Components: master, worker
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>             Fix For: 0.3-incubating
>
>
> In the current implementation, the logical plan is serialized into a JSON object and
sent to each worker.
> However, the transmission of JSON object incurs the high overhead due to its large size.
> ProtocolBuffer is a good alternative because its overhead is quite small and already
used in other modules of Tajo.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message