You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (Updated) (JIRA)" <ji...@apache.org> on 2012/01/18 23:26:41 UTC
[jira] [Updated] (HBASE-5228) [REST] Rip out "transform" feature
[ https://issues.apache.org/jira/browse/HBASE-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-5228:
----------------------------------
Attachment: HBASE-5228.patch
> [REST] Rip out "transform" feature
> ----------------------------------
>
> Key: HBASE-5228
> URL: https://issues.apache.org/jira/browse/HBASE-5228
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0, 0.94.0, 0.90.5
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Attachments: HBASE-5228.patch
>
>
> The 'transform' feature, where REST can be instructed, via a table attribute, to apply a transformation (e.g. base64 encoding or decoding) to a (sub)set of column values before serving them up to a client or storing them into HBase, was added some time ago at the request of Jack Levin. I have since come to regret it, it was not a well thought out feature:
> - This is really an application concern.
> - It adds significant overhead to request processing: Periodically a HBaseAdmin is used to retrieve the table descriptor, in order to scan through table attributes for transformation directives.
> I think it is best to rip it out, its a real problem area, and REST should be no more concerned about data formats than the Java API.
> I doubt anyone uses this, not even Jack. Will need to follow up with him to confirm.
--
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