You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2026/02/15 15:14:00 UTC
[jira] [Updated] (HBASE-29223) Migrate Master Status Jamon page back to JSP
[ https://issues.apache.org/jira/browse/HBASE-29223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Duo Zhang updated HBASE-29223:
------------------------------
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.5
2.5.14
> Migrate Master Status Jamon page back to JSP
> --------------------------------------------
>
> Key: HBASE-29223
> URL: https://issues.apache.org/jira/browse/HBASE-29223
> Project: HBase
> Issue Type: Sub-task
> Components: UI
> Reporter: Dávid Paksy
> Assignee: Dávid Paksy
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5, 2.5.14
>
>
> While I was working on HBASE-28832 to migrate Bootstrap I noticed that HBase have a mix of JSP and Jamon code. Looks like HBASE-3835 started the work in 2011 of converting from JSP to Jamon, but the work didn't finish.
>
> After the discussion of this in [https://lists.apache.org/thread/0c9to6rxzbf5f2x6t0x20408n15rdvmt] it seems that it would be a good idea to move the Jamon code back to JSP and get rid of the Jamon compiler dependency.
>
> As a first step we could just move back the Jamon code to JSP (this Jira).
> Then we can extract the Java code from JSP files to some backing beans (under new Jiras).
>
> Since we have 14 Jamon files 3850 line of code so this Jira is for the fist step to migrate Master Status page.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)