[
https://issues.apache.org/jira/browse/CHUKWA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhijit Dhar updated CHUKWA-632:
--------------------------------
Attachment: patch.txt
Patch attached
> 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
