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 (JIRA)" <ji...@apache.org> on 2010/10/18 23:58:32 UTC
[jira] Created: (HBASE-3120) [rest] content transcoding
[rest] content transcoding
--------------------------
Key: HBASE-3120
URL: https://issues.apache.org/jira/browse/HBASE-3120
Project: HBase
Issue Type: Improvement
Components: rest
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
We have a reasonable user request for support for decoding of base64 encoded values into raw/binary when servicing GET requests with an Accept header of {{application/octet-stream}}.
We can introduce a table schema attribute for column families that instructs the REST gateway to perform input and/or output transcoding, with base64->binary (for GET) and vice versa (for PUT or POST) as the first supported option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3120) [rest] content transcoding
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-3120:
----------------------------------
Attachment: HBASE-3120.patch
A working sketch of how this could be done.
> [rest] content transcoding
> --------------------------
>
> Key: HBASE-3120
> URL: https://issues.apache.org/jira/browse/HBASE-3120
> Project: HBase
> Issue Type: Improvement
> Components: rest
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: HBASE-3120.patch
>
>
> We have a reasonable user request for support for decoding of base64 encoded values into raw/binary when servicing GET requests with an Accept header of {{application/octet-stream}}.
> We can introduce a table schema attribute for column families that instructs the REST gateway to perform input and/or output transcoding, with base64->binary (for GET) and vice versa (for PUT or POST) as the first supported option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-3120) [rest] content transcoding
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-3120.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.90.0
Hadoop Flags: [Reviewed]
Committed.
> [rest] content transcoding
> --------------------------
>
> Key: HBASE-3120
> URL: https://issues.apache.org/jira/browse/HBASE-3120
> Project: HBase
> Issue Type: Improvement
> Components: rest
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.90.0
>
> Attachments: HBASE-3120.patch
>
>
> We have a reasonable user request for support for decoding of base64 encoded values into raw/binary when servicing GET requests with an Accept header of {{application/octet-stream}}.
> We can introduce a table schema attribute for column families that instructs the REST gateway to perform input and/or output transcoding, with base64->binary (for GET) and vice versa (for PUT or POST) as the first supported option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3120) [rest] content transcoding
Posted by "HBase Review Board (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926549#action_12926549 ]
HBase Review Board commented on HBASE-3120:
-------------------------------------------
Message from: "Andrew Purtell" <ap...@apache.org>
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/1136/
-----------------------------------------------------------
Review request for hbase.
Summary
-------
Introduce a table schema attribute for column families that instructs the REST gateway to perform input and/or output transcoding, with base64->binary (for GET) and vice versa (for PUT or POST) as the first supported option.
This addresses bug HBASE-3120.
http://issues.apache.org/jira/browse/HBASE-3120
Diffs
-----
src/main/java/org/apache/hadoop/hbase/rest/ExistsResource.java d83dc20
src/main/java/org/apache/hadoop/hbase/rest/RegionsResource.java 54f2dc7
src/main/java/org/apache/hadoop/hbase/rest/RowResource.java 1bf17b8
src/main/java/org/apache/hadoop/hbase/rest/ScannerResource.java 5bb90ef
src/main/java/org/apache/hadoop/hbase/rest/SchemaResource.java 7262229
src/main/java/org/apache/hadoop/hbase/rest/TableResource.java 5f305db
src/main/java/org/apache/hadoop/hbase/rest/transform/Base64.java PRE-CREATION
src/main/java/org/apache/hadoop/hbase/rest/transform/NullTransform.java PRE-CREATION
src/main/java/org/apache/hadoop/hbase/rest/transform/Transform.java PRE-CREATION
Diff: http://review.cloudera.org/r/1136/diff
Testing
-------
Created a test table. Modified the HCD of a column family by adding a custom attribute of 'Transform$1' => '*:Base64'. Used curl to store the string "Testing 1, 2, 3" using content type application/octet-stream. Confirmed with shell the value was base64 encoded in table. Used curl to retrieve the value using accept header of application/octet-stream and confirmed the response body was the decoded string.
Thanks,
Andrew
> [rest] content transcoding
> --------------------------
>
> Key: HBASE-3120
> URL: https://issues.apache.org/jira/browse/HBASE-3120
> Project: HBase
> Issue Type: Improvement
> Components: rest
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: HBASE-3120.patch
>
>
> We have a reasonable user request for support for decoding of base64 encoded values into raw/binary when servicing GET requests with an Accept header of {{application/octet-stream}}.
> We can introduce a table schema attribute for column families that instructs the REST gateway to perform input and/or output transcoding, with base64->binary (for GET) and vice versa (for PUT or POST) as the first supported option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3120) [rest] content transcoding
Posted by "HBase Review Board (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926681#action_12926681 ]
HBase Review Board commented on HBASE-3120:
-------------------------------------------
Message from: stack@duboce.net
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/1136/#review1727
-----------------------------------------------------------
Ship it!
Looks good Andy. Theres a bit of white space. Try squash it on commit. You don't have a test of the new facility. Would that be hard to add?
- stack
> [rest] content transcoding
> --------------------------
>
> Key: HBASE-3120
> URL: https://issues.apache.org/jira/browse/HBASE-3120
> Project: HBase
> Issue Type: Improvement
> Components: rest
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: HBASE-3120.patch
>
>
> We have a reasonable user request for support for decoding of base64 encoded values into raw/binary when servicing GET requests with an Accept header of {{application/octet-stream}}.
> We can introduce a table schema attribute for column families that instructs the REST gateway to perform input and/or output transcoding, with base64->binary (for GET) and vice versa (for PUT or POST) as the first supported option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-3120) [rest] content transcoding
Posted by "HBase Review Board (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927183#action_12927183 ]
HBase Review Board commented on HBASE-3120:
-------------------------------------------
Message from: "Andrew Purtell" <ap...@apache.org>
bq. On 2010-10-30 22:24:29, stack wrote:
bq. > Looks good Andy. Theres a bit of white space. Try squash it on commit. You don't have a test of the new facility. Would that be hard to add?
Thanks for the review. I'll squash WS add a unit test before commit.
- Andrew
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/1136/#review1727
-----------------------------------------------------------
> [rest] content transcoding
> --------------------------
>
> Key: HBASE-3120
> URL: https://issues.apache.org/jira/browse/HBASE-3120
> Project: HBase
> Issue Type: Improvement
> Components: rest
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Attachments: HBASE-3120.patch
>
>
> We have a reasonable user request for support for decoding of base64 encoded values into raw/binary when servicing GET requests with an Accept header of {{application/octet-stream}}.
> We can introduce a table schema attribute for column families that instructs the REST gateway to perform input and/or output transcoding, with base64->binary (for GET) and vice versa (for PUT or POST) as the first supported option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.