You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2009/07/24 02:56:14 UTC
[jira] Created: (HBASE-1695) [stargate] differentiate PUT and POST
processing for schema upload
[stargate] differentiate PUT and POST processing for schema upload
------------------------------------------------------------------
Key: HBASE-1695
URL: https://issues.apache.org/jira/browse/HBASE-1695
Project: Hadoop HBase
Issue Type: Task
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 0.20.0
The Stargate documentation states the following regarding PUT and POST to a table schema resource:
bq. PUT or POST creates table as necessary. PUT fully replaces schema. POST modifies schema (add or modify column family). Supply the full table schema for PUT or a well formed schema fragment for POST in the desired encoding.
Current implementation punts and treats both PUT and POST as equivalent. Fix before release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1695) [stargate] differentiate PUT and
POST processing for schema upload
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735744#action_12735744 ]
Andrew Purtell commented on HBASE-1695:
---------------------------------------
I do and I should have something committed today.
> [stargate] differentiate PUT and POST processing for schema upload
> ------------------------------------------------------------------
>
> Key: HBASE-1695
> URL: https://issues.apache.org/jira/browse/HBASE-1695
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.20.0
>
>
> The Stargate documentation states the following regarding PUT and POST to a table schema resource:
> bq. PUT or POST creates table as necessary. PUT fully replaces schema. POST modifies schema (add or modify column family). Supply the full table schema for PUT or a well formed schema fragment for POST in the desired encoding.
> Current implementation punts and treats both PUT and POST as equivalent. Fix before release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-1695) [stargate] differentiate PUT and POST
processing for schema upload
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-1695:
----------------------------------
Attachment: HBASE-1695.patch
> [stargate] differentiate PUT and POST processing for schema upload
> ------------------------------------------------------------------
>
> Key: HBASE-1695
> URL: https://issues.apache.org/jira/browse/HBASE-1695
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: HBASE-1695.patch
>
>
> The Stargate documentation states the following regarding PUT and POST to a table schema resource:
> bq. PUT or POST creates table as necessary. PUT fully replaces schema. POST modifies schema (add or modify column family). Supply the full table schema for PUT or a well formed schema fragment for POST in the desired encoding.
> Current implementation punts and treats both PUT and POST as equivalent. Fix before release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-1695) [stargate] differentiate PUT and
POST processing for schema upload
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735667#action_12735667 ]
stack commented on HBASE-1695:
------------------------------
You think this necessary to the release Andrew?
> [stargate] differentiate PUT and POST processing for schema upload
> ------------------------------------------------------------------
>
> Key: HBASE-1695
> URL: https://issues.apache.org/jira/browse/HBASE-1695
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.20.0
>
>
> The Stargate documentation states the following regarding PUT and POST to a table schema resource:
> bq. PUT or POST creates table as necessary. PUT fully replaces schema. POST modifies schema (add or modify column family). Supply the full table schema for PUT or a well formed schema fragment for POST in the desired encoding.
> Current implementation punts and treats both PUT and POST as equivalent. Fix before release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HBASE-1695) [stargate] differentiate PUT and POST
processing for schema upload
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell resolved HBASE-1695.
-----------------------------------
Resolution: Fixed
Committed.
> [stargate] differentiate PUT and POST processing for schema upload
> ------------------------------------------------------------------
>
> Key: HBASE-1695
> URL: https://issues.apache.org/jira/browse/HBASE-1695
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: HBASE-1695.patch
>
>
> The Stargate documentation states the following regarding PUT and POST to a table schema resource:
> bq. PUT or POST creates table as necessary. PUT fully replaces schema. POST modifies schema (add or modify column family). Supply the full table schema for PUT or a well formed schema fragment for POST in the desired encoding.
> Current implementation punts and treats both PUT and POST as equivalent. Fix before release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.