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

Posted to dev@hbase.apache.org by "Skigh (JIRA)" <ji...@apache.org> on 2010/02/12 20:58:28 UTC

[jira] Commented: (HBASE-1830) HbaseObjectWritable methods should allow null HBaseConfigurations for when Writable is not Configurable

    [ https://issues.apache.org/jira/browse/HBASE-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833136#action_12833136 ] 

Skigh commented on HBASE-1830:
------------------------------

The problem still seems to be around, after applying patch 1828 and patch 1830.

I am on 0.20.0, and applied the two patches.  I was trying to use a SingleColumnValueFilter wrapped by a SkipFilter, and I am still getting this EOFException after retries exhausted.  are we sure it is fixed?
or am I missing something?

Thanks!

> HbaseObjectWritable methods should allow null HBaseConfigurations for when Writable is not Configurable
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-1830
>                 URL: https://issues.apache.org/jira/browse/HBASE-1830
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: io
>    Affects Versions: 0.20.0
>            Reporter: Jonathan Gray
>            Assignee: stack
>             Fix For: 0.20.1, 0.21.0
>
>         Attachments: 1830.patch
>
>
> HBASE-1828 dealt with a broken scanner because we were passing null for HBaseConfiguration.  Previous patches attempted to make it so HbaseObjectWritable would work with null HBC but it appears there is still a problem here.  Fix it so we allow null HBC.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.