Mailing-List: contact chukwa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chukwa-dev@incubator.apache.org
Date: Mon, 16 Apr 2012 22:52:16 +0000 (UTC)
From: "Abhijit Dhar (Updated) (JIRA)" <jira@apache.org>
To: chukwa-dev@incubator.apache.org
Message-ID: 
 <1550623105.30777.1334616736997.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1146066018.5211.1328221377799.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CHUKWA-632) Logs getting lost in hbase using
 TsProcessor
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Abhijit Dhar updated CHUKWA-632:
--------------------------------

    Status: Patch Available  (was: Open)
    
> Logs getting lost in hbase using TsProcessor
> --------------------------------------------
>
>                 Key: CHUKWA-632
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-632
>             Project: Chukwa
>          Issue Type: Bug
>    Affects Versions: 0.5.0
>            Reporter: Abhijit Dhar
>         Attachments: patch.txt
>
>
> When collector writes to hbase using TsProcessor, it is using timestamp as the key. If there are multiple log statements with the same timestamp, which is the key, it looses them in hbase.
> As a fix, I extended AbstractProcessor and built my key using timestamp and the AbstractProcessor.startOffset. But, for that, it has to be protected or a getter on it in AbstractProcessor class to be able to use it.
> Also, the way OutputCollector.collect method works, it might need to redo the way rowKey is created.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira