You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Rajesh Balamohan (JIRA)" <ji...@apache.org> on 2014/11/06 14:49:34 UTC

[jira] [Resolved] (TEZ-1738) tez tfile parser for log parsing

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

Rajesh Balamohan resolved TEZ-1738.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.6.0
     Hadoop Flags: Reviewed

Thanks [~gopalv]. Committed to master.
>>
Commit: 7b55e380895203406c01896b2c577fa12e621390
>>


> tez tfile parser for log parsing
> --------------------------------
>
>                 Key: TEZ-1738
>                 URL: https://issues.apache.org/jira/browse/TEZ-1738
>             Project: Apache Tez
>          Issue Type: Improvement
>    Affects Versions: 0.6.0
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>             Fix For: 0.6.0
>
>         Attachments: TEZ-1738.1.patch, TEZ-1738.2.patch
>
>
> It can be time consuming to download logs via "yarn logs -applicationId <appId> | grep something".  Also mining large volumes of logs can be time consuming on single node.
> A simple pigloader would be useful to have in tez-tools which can parse TFiles and provide line by line format (tuple of (machine, key, line)) for distributed processing of logs.



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