[
https://issues.apache.org/jira/browse/HBASE-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-3462.
--------------------------------
Resolution: Fixed
Hadoop Flags: Incompatible change,Reviewed (was: Reviewed)
Release Note: UI pages for splitting/merging now operate by taking a row
key prefix from the user rather than a full region name.
> 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
> Assignee: Balazs Meszaros
> Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-3462-BM-01.patch, HBASE-3462-BM-01.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)
