[
https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156809#comment-16156809
]
Balazs Meszaros commented on HBASE-18106:
-----------------------------------------
I did my best with JRuby issues.
> Redo ProcedureInfo and LockInfo
> -------------------------------
>
> Key: HBASE-18106
> URL: https://issues.apache.org/jira/browse/HBASE-18106
> Project: HBase
> Issue Type: Sub-task
> Components: proc-v2
> Affects Versions: 2.0.0
> Reporter: stack
> Assignee: Balazs Meszaros
> Priority: Critical
> Fix For: 3.0.0, 2.0.0-alpha-3
>
> Attachments: HBASE-18106.master.001.patch,
> HBASE-18106.master.002.patch, HBASE-18106.master.003.patch,
> HBASE-18106.master.004.patch, HBASE-18106.master.005.patch,
> HBASE-18106.master.006.patch, HBASE-18106.master.007.patch,
> HBASE-18106.master.008.patch, HBASE-18106.master.009.patch,
> HBASE-18106.master.010.patch, HBASE-18106.master.011.patch
>
>
> ProcedureInfo was introduced as a lowest-common-denominator POJO that could
> be used as a facade on PB Procedures. It was good for showing state of
> Procedure framework in shell and UI.
> Its a bit weird though. Its up in hbase-common rather than in Procedure and
> it can only ever show a subset of the Procedure info.
> I was thinking we could use the pb3.1 pb->JSON utility instead and emit a
> JSON String wherever we need to export a view on procedure internals.
> This issue is about exploring this possibility. Would depend on our having an
> upgraded guava (so probably depends on the 'pre-build' project).
> From ProcedureInfo and LockInfo need fixing in
> https://docs.google.com/document/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=h.kid1jzo114xw
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
