PDavid opened a new pull request, #6542: URL: https://github.com/apache/hbase/pull/6542
Cherry-picked the following patches which were missing on branch-2.5 branch. Most of these applied as a clean cherry-pick (without conflicts). Unfortunately there were some which had conflicts and I manually resolved them. Each commit message contains from which commit it was cherry-picked from. - HBASE-27406 Make /prometheus endpoint accessible from HBase UI (#4833) - HBASE-27814 Add support for dump and process metrics servlet in REST InfoServer (#5215) - HBASE-18382 add transport type info into Thrift UI (#880) - HBASE-20693 Refactor thrift jsp's and extract header and footer (#5732) - HBASE-24624 Optimize table.jsp code (#1963) - :warning: This was not clean - had to resolve conflicts - HBASE-25402 Sorting order by start key or end key is not considering empty start key/end key (#2955) - HBASE-27309 Add major compact table or region operation on master web table page (#4793) - HBASE-28778 NPE may occur when opening master-status or table.jsp or procedure.jsp while Master is initializing (#6152) - HBASE-28305 Add "Uncompressed StoreFileSize" column to the table.jsp (#5620) - :warning: This was not clean - had to resolve conflicts - HBASE-20452 Master UI: Table merge button should validate required fields before submit Is it OK to have multiple patches in one PR like this or would you prefer having a separate PR for each commit? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
