You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/11/06 06:56:33 UTC

[jira] [Commented] (TAJO-1026) Implement Query history persistency manager.

    [ https://issues.apache.org/jira/browse/TAJO-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199844#comment-14199844 ] 

ASF GitHub Bot commented on TAJO-1026:
--------------------------------------

Github user babokim commented on the pull request:

    https://github.com/apache/tajo/pull/179#issuecomment-61930943
  
    I'm sorry for late rebase. I just rebase.


> Implement Query history persistency manager.
> --------------------------------------------
>
>                 Key: TAJO-1026
>                 URL: https://issues.apache.org/jira/browse/TAJO-1026
>             Project: Tajo
>          Issue Type: New Feature
>          Components: query master, tajo master
>            Reporter: Hyoungjun Kim
>            Assignee: Hyoungjun Kim
>            Priority: Minor
>             Fix For: 0.9.1
>
>
> Currently query history stored in the memory of TajoMaster or QueryMaster. Query detail information is disappeared when the cluster is restarted. And because of memory limitations, only a few hours or a few days histories are kept.
> I suggest the following features for the query history.
> - Worker saves a query task history to the HDFS after finishing a query.
> - QueryMaster saves a query history to the HDFS after finishing a query.
> - If query is finished, Information Web server in TajoMaster shows query history in the web page, If query is running  TajoMaster forward to QueryMaster.
> - History data will be saved to HDFS with JSON format.
> - JSON format has history file version for backward compatibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)