You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2011/01/21 15:43:44 UTC
[jira] Created: (HBASE-3462) Fix table.jsp in regards to splitting
a region/table with an optional splitkey
Fix table.jsp in regards to splitting a region/table with an optional splitkey
------------------------------------------------------------------------------
Key: HBASE-3462
URL: https://issues.apache.org/jira/browse/HBASE-3462
Project: HBase
Issue Type: Improvement
Components: master
Affects Versions: 0.90.0
Reporter: Lars George
Priority: Minor
Fix For: 0.90.1
After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
{quote}
This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
{quote}
I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in \.META\.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
{code}
2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
{code}
Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HBASE-3462) Fix table.jsp in regards to splitting
a region/table with an optional splitkey
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-3462:
-------------------------------
Description:
After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
{quote}
This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
{quote}
I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in .META.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
{code}
2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
{code}
Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
was:
After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
{quote}
This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
{quote}
I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in \.META\.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
{code}
2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
{code}
Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
> Fix table.jsp in regards to splitting a region/table with an optional splitkey
> ------------------------------------------------------------------------------
>
> Key: HBASE-3462
> URL: https://issues.apache.org/jira/browse/HBASE-3462
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.0
> Reporter: Lars George
> Priority: Minor
> Fix For: 0.90.1
>
>
> After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
> {quote}
> This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
> {quote}
> I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in .META.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
> {code}
> 2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
> {code}
> Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
> Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (HBASE-3462) Fix table.jsp in regards to splitting
a region/table with an optional splitkey
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-3462:
-------------------------
Priority: Major (was: Minor)
Fix Version/s: 0.92.0
> Fix table.jsp in regards to splitting a region/table with an optional splitkey
> ------------------------------------------------------------------------------
>
> Key: HBASE-3462
> URL: https://issues.apache.org/jira/browse/HBASE-3462
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.0
> Reporter: Lars George
> Fix For: 0.92.0
>
>
> After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
> {quote}
> This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
> {quote}
> I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in .META.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
> {code}
> 2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
> {code}
> Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
> Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3462) Fix table.jsp in regards to splitting
a region/table with an optional splitkey
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-3462:
-------------------------
Tags: noob
Fix Version/s: (was: 0.96.0)
Moving out of 0.96.
> Fix table.jsp in regards to splitting a region/table with an optional splitkey
> ------------------------------------------------------------------------------
>
> Key: HBASE-3462
> URL: https://issues.apache.org/jira/browse/HBASE-3462
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.0
> Reporter: Lars George
> Labels: noob
>
> After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
> {quote}
> This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
> {quote}
> I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in .META.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
> {code}
> 2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
> {code}
> Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
> Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3462) Fix table.jsp in regards to splitting
a region/table with an optional splitkey
Posted by "Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated HBASE-3462:
--------------------------
Fix Version/s: (was: 0.92.0)
0.94.0
> Fix table.jsp in regards to splitting a region/table with an optional splitkey
> ------------------------------------------------------------------------------
>
> Key: HBASE-3462
> URL: https://issues.apache.org/jira/browse/HBASE-3462
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.0
> Reporter: Lars George
> Fix For: 0.94.0
>
>
> After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
> {quote}
> This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
> {quote}
> I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in .META.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
> {code}
> 2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
> {code}
> Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
> Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-3462) Fix table.jsp in regards to splitting
a region/table with an optional splitkey
Posted by "Lars Hofhansl (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-3462:
---------------------------------
Fix Version/s: (was: 0.94.0)
0.96.0
Moving out of 0.94.
> Fix table.jsp in regards to splitting a region/table with an optional splitkey
> ------------------------------------------------------------------------------
>
> Key: HBASE-3462
> URL: https://issues.apache.org/jira/browse/HBASE-3462
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.0
> Reporter: Lars George
> Fix For: 0.96.0
>
>
> After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
> {quote}
> This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
> {quote}
> I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in .META.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
> {code}
> 2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
> {code}
> Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
> Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
--
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
[jira] [Updated] (HBASE-3462) Fix table.jsp in regards to splitting
a region/table with an optional splitkey
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-3462:
-------------------------
Labels: noob (was: )
Marking noob in case some one wants to have a go at it.
> Fix table.jsp in regards to splitting a region/table with an optional splitkey
> ------------------------------------------------------------------------------
>
> Key: HBASE-3462
> URL: https://issues.apache.org/jira/browse/HBASE-3462
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 0.90.0
> Reporter: Lars George
> Labels: noob
>
> After HBASE-3328 and HBASE-3437 went in there is also the table.jsp that needs updating to support the same features. Also, at the same time update the wording, for example
> {quote}
> This action will force a split of all eligible regions of the table, or, if a key is supplied, only the region containing the given key. An eligible region is one that does not contain any references to other regions. Split requests for noneligible regions will be ignored.
> {quote}
> I think it means it splits either all regions (that are splittable) or a specific one. It says though "the region containing the given key", that seems wrong in any event. Currently we do a split on the tablename when nothing was specified or else do an internal get(region), which is an exact match on the rows in .META.. In other words you need to match the region name exactly or else it fails. It reports it has accepted the request but logs internally
> {code}
> 2011-01-21 15:37:24,340 INFO org.apache.hadoop.hbase.client.HBaseAdmin: No server in .META. for csfsef; pair=null
> {code}
> Error reporting could be better but because of the async nature this is more difficult, yet it would be nice there is some concept of a Future to be able to poll the result if needed.
> Finally, when you go back to the previous page after submitting the split the entered values show up in the "compact" input fields, at least on my Chrome. The inputs in both forms are named the same so it seems to confuse it. This could be improved a lot by making the landing page reload the main one automatically or refresh on reload instead of submitting the request again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira