You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "sishen (JIRA)" <ji...@apache.org> on 2008/10/26 13:58:44 UTC
[jira] Created: (HBASE-960) REST interface: more generic column
family configure and also get Rows using offset and limit
REST interface: more generic column family configure and also get Rows using offset and limit
----------------------------------------------------------------------------------------------
Key: HBASE-960
URL: https://issues.apache.org/jira/browse/HBASE-960
Project: Hadoop HBase
Issue Type: Improvement
Components: rest
Affects Versions: 0.19.0
Reporter: sishen
Fix For: 0.19.0
The update column family operation in REST interface will overwrite the default metadata using the default value which is unexpected.
We should use the column family to get the old value and then do update if requested by the users.
Also, for non-default metadata value, such as "hbase.hregion.majorcompaction", we should still be enable to create/update it using REST interface.
For RowHandler, the user can request with offset and limit and get the rows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-960) REST interface: more generic column
family configure and also get Rows using offset and limit
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sishen updated HBASE-960:
-------------------------
Status: Patch Available (was: Open)
> REST interface: more generic column family configure and also get Rows using offset and limit
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-960
> URL: https://issues.apache.org/jira/browse/HBASE-960
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: rest
> Affects Versions: 0.19.0
> Reporter: sishen
> Fix For: 0.19.0
>
> Attachments: 960.trunk.update_column_descriptor.patch
>
>
> The update column family operation in REST interface will overwrite the default metadata using the default value which is unexpected.
> We should use the column family to get the old value and then do update if requested by the users.
> Also, for non-default metadata value, such as "hbase.hregion.majorcompaction", we should still be enable to create/update it using REST interface.
> For RowHandler, the user can request with offset and limit and get the rows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HBASE-960) REST interface: more generic column
family configure and also get Rows using offset and limit
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack reassigned HBASE-960:
---------------------------
Assignee: sishen
> REST interface: more generic column family configure and also get Rows using offset and limit
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-960
> URL: https://issues.apache.org/jira/browse/HBASE-960
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: rest
> Affects Versions: 0.19.0
> Reporter: sishen
> Assignee: sishen
> Fix For: 0.19.0
>
> Attachments: 960.trunk.update_column_descriptor.patch
>
>
> The update column family operation in REST interface will overwrite the default metadata using the default value which is unexpected.
> We should use the column family to get the old value and then do update if requested by the users.
> Also, for non-default metadata value, such as "hbase.hregion.majorcompaction", we should still be enable to create/update it using REST interface.
> For RowHandler, the user can request with offset and limit and get the rows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-960) REST interface: more generic column
family configure and also get Rows using offset and limit
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-960:
------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed. Thanks for the patch Sishen.
Maybe start thinking about unit tests for REST? I can help you. Would suggest that unit test startup a REST server and then run a client against it verifying results.
Good stuff.
> REST interface: more generic column family configure and also get Rows using offset and limit
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-960
> URL: https://issues.apache.org/jira/browse/HBASE-960
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: rest
> Affects Versions: 0.19.0
> Reporter: sishen
> Fix For: 0.19.0
>
> Attachments: 960.trunk.update_column_descriptor.patch
>
>
> The update column family operation in REST interface will overwrite the default metadata using the default value which is unexpected.
> We should use the column family to get the old value and then do update if requested by the users.
> Also, for non-default metadata value, such as "hbase.hregion.majorcompaction", we should still be enable to create/update it using REST interface.
> For RowHandler, the user can request with offset and limit and get the rows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HBASE-960) REST interface: more generic column
family configure and also get Rows using offset and limit
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644118#action_12644118 ]
sishen commented on HBASE-960:
------------------------------
Stack: ok. I'll add the unit tests following the styles of the current unit test.
> REST interface: more generic column family configure and also get Rows using offset and limit
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-960
> URL: https://issues.apache.org/jira/browse/HBASE-960
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: rest
> Affects Versions: 0.19.0
> Reporter: sishen
> Fix For: 0.19.0
>
> Attachments: 960.trunk.update_column_descriptor.patch
>
>
> The update column family operation in REST interface will overwrite the default metadata using the default value which is unexpected.
> We should use the column family to get the old value and then do update if requested by the users.
> Also, for non-default metadata value, such as "hbase.hregion.majorcompaction", we should still be enable to create/update it using REST interface.
> For RowHandler, the user can request with offset and limit and get the rows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-960) REST interface: more generic column
family configure and also get Rows using offset and limit
Posted by "sishen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sishen updated HBASE-960:
-------------------------
Attachment: 960.trunk.update_column_descriptor.patch
The TableHandler new example configure xml:
<?xml version="1.0" encoding="UTF-8"?>
<table>
<name>tables</name>
<columnfamilies>
<columnfamily>
<name>column_name</name>
<max-versions>1</max-versions>
<compression>BLOCK</compression>
<in-memory>false</in-memory>
<block-cache>true</block-cache>
<metadata>
<name>hbase.hregion.majorcompaction</name>
<value>1800</value>
</metadata>
<metadata>
<name>xxx</name>
<value>xxxx</value>
</metadata>
</columnfamily>
</columnfamilies>
</table>
The RowHandler new example request:
http://localhost:60010/api/table_name/row/row_name?offset=xx&limit=xx
the response will be
<?xml version="1.0" encoding="UTF-8"?>
<row>
<count></count>
<column>
<name>
a:
</name>
<value>
YQ==
</value>
<timestamp>xxxxxxxxxxx</timestamp>
</column>
<column>
<name></name>
<value></value>
<timestamp>xxxxxxxxx</timestamp>
</column>
</row>
> REST interface: more generic column family configure and also get Rows using offset and limit
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-960
> URL: https://issues.apache.org/jira/browse/HBASE-960
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: rest
> Affects Versions: 0.19.0
> Reporter: sishen
> Fix For: 0.19.0
>
> Attachments: 960.trunk.update_column_descriptor.patch
>
>
> The update column family operation in REST interface will overwrite the default metadata using the default value which is unexpected.
> We should use the column family to get the old value and then do update if requested by the users.
> Also, for non-default metadata value, such as "hbase.hregion.majorcompaction", we should still be enable to create/update it using REST interface.
> For RowHandler, the user can request with offset and limit and get the rows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.