You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2010/09/08 19:05:33 UTC
[jira] Updated: (HBASE-2942) Custom filters should not require
registration in HbaseObjectWritable
[ https://issues.apache.org/jira/browse/HBASE-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Helmling updated HBASE-2942:
---------------------------------
Attachment: HBASE_2942.patch
The attached patch uses the Writable class code for Writable implementations if no other code is found, and adds some unit tests around problem cases. I believe this should fix any remaining problems that would have required added class codes to HbaseObjectWritable.
> Custom filters should not require registration in HbaseObjectWritable
> ---------------------------------------------------------------------
>
> Key: HBASE-2942
> URL: https://issues.apache.org/jira/browse/HBASE-2942
> Project: HBase
> Issue Type: Bug
> Components: filters
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Priority: Minor
> Attachments: HBASE_2942.patch
>
>
> Some of the filter RPC serialization still requires that code -> class mappings be added to HbaseObjectWritable. FilterList in particular requires this for it's child filters, since it calls HbaseObjectWritable.writeObject() on each. This makes developing custom filters a big pain, as HbaseObjectWritable must be modified and the hbase core jar re-staged to the cluster.
> We should fix this so that all filters can be written as a class name + data if no code exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.