[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Fix Version/s: 2.0.0 > 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: 2.0.0-alpha-3, 2.0.0 > > 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, > HBASE-18106.master.011.patch, HBASE-18106.master.012.patch, > HBASE-18106.master.012.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 (v7.6.3#76005)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed. Actually resolving. > 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: 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, > HBASE-18106.master.011.patch, HBASE-18106.master.012.patch, > HBASE-18106.master.012.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- I ran the test locally on master and branch-2 and both passed for me too. Pushed to master and branch-2. Thanks for keeping at this awkward patch [~balazs.meszaros]. Its great cleanup sir. This patch is also an enabler. Views on locks and procedures can be built out of the JSON we are pushing out. > 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: 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, > HBASE-18106.master.011.patch, HBASE-18106.master.012.patch, > HBASE-18106.master.012.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Attachment: HBASE-18106.master.012.patch Retry again before [~balazs.meszaros] wakes up > 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: 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, > HBASE-18106.master.011.patch, HBASE-18106.master.012.patch, > HBASE-18106.master.012.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Attachment: HBASE-18106.master.012.patch > 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: 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, > HBASE-18106.master.011.patch, HBASE-18106.master.012.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Fix Version/s: (was: 3.0.0) > 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: 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, > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Attachment: HBASE-18106.master.011.patch Retry while reviewing. > 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, > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.010.patch > 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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.011.patch > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Attachment: HBASE-18106.master.009.patch Fix license and javadoc. Test failures seem unrelated. The complaints from jruby cop and lint seem real against new .rb files. Want to have a go at them [~balazs.meszaros] ? Thanks boss. > 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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.008.patch > 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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[
https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18106:
--
Hadoop Flags: Incompatible change,Reviewed
Release Note:
Admin.listProcedures and Admin.listLocks were renamed to getProcedures and
getLocks (listProcedures was added to hbase 1.2). This change was done in an
incompatible way -- we just yanked listProcedures (Because Admin Interface is
not compatible with hbase1).
Main changes:
- ProcedureInfo and LockInfo were removed, we use JSON instead of them
- Procedure and LockedResource are their server side equivalent
- Procedure protobuf state_data became obsolate, it is only kept for
reading previously written WAL
- Procedure protobuf contains a state_message field, which stores the
internal
state messages (Any type instead of bytes)
- Procedure.serializeStateData and deserializeStateData were changed
slightly
- Procedures internal states are available on client side
- Procedures are displayed on web UI and in shell in the following jruby
format:
{ ID => '1', PARENT_ID = '-1', PARAMETERS => [ ..extra state
information.. ] }
was:
Admin.listProcedures and Admin.listLocks were renamed to getProcedures and
getLocks.
listProcedures permission has been renamed to getProcedures and getLocks
permission was introduced.
Marked as an incompat change.
> 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
>
>
> 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.007.patch > 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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Release Note: Admin.listProcedures and Admin.listLocks were renamed to getProcedures and getLocks. listProcedures permission has been renamed to getProcedures and getLocks permission was introduced. > 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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.006.patch > 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 >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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.005.patch > 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 >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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.004.patch > 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 >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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-18106: -- Fix Version/s: (was: 2.0.0) 2.0.0-alpha-3 > 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 >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 > > > 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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.003.patch > 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 >Priority: Critical > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18106.master.001.patch, > HBASE-18106.master.002.patch, HBASE-18106.master.003.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Fix Version/s: 3.0.0 Status: Patch Available (was: Open) > 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 >Priority: Critical > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18106.master.001.patch, > HBASE-18106.master.002.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.002.patch > 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 >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18106.master.001.patch, > HBASE-18106.master.002.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balazs Meszaros updated HBASE-18106: Attachment: HBASE-18106.master.001.patch > 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 >Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-18106.master.001.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)
[jira] [Updated] (HBASE-18106) Redo ProcedureInfo and LockInfo
[ https://issues.apache.org/jira/browse/HBASE-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-18106: -- Priority: Critical (was: Major) > 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 >Priority: Critical > Fix For: 2.0.0 > > > 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)
