[
https://issues.apache.org/jira/browse/HBASE-14015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612890#comment-14612890
]
Ashish Singhi commented on HBASE-14015:
---------------------------------------
[[email protected]], this seems to be introducing a compilation error in at
least branch-1.
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hbase-procedure: Compilation failure:
Compilation failure:
[ERROR]
/home/root1/Code/H-b-1/hbase-procedure/src/test/java/org/apache/hadoop/hbase/procedure2/TestProcedureToString.java:[28,49]
error: cannot find symbol
[ERROR] symbol: class MasterTests
[ERROR] location: package org.apache.hadoop.hbase.testclassification
[ERROR]
/home/root1/Code/H-b-1/hbase-procedure/src/test/java/org/apache/hadoop/hbase/procedure2/TestProcedureToString.java:[33,11]
error: cannot find symbol
{noformat}
> Allow setting a richer state value when toString a pv2
> ------------------------------------------------------
>
> Key: HBASE-14015
> URL: https://issues.apache.org/jira/browse/HBASE-14015
> Project: HBase
> Issue Type: Improvement
> Components: proc-v2
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments:
> 0001-HBASE-14015-Allow-setting-a-richer-state-value-when-.patch
>
>
> Debugging, my procedure after a crash was loaded out of the store and its
> state was RUNNING. It would help if I knew in which of the states of a
> StateMachineProcedure it was going to start RUNNING at.
> Chatting w/ Matteo, he suggested allowing Procedures customize the String.
> Here is patch that makes it so StateMachineProcedure will now print out the
> base state -- RUNNING, FINISHED -- followed by a ':' and then the
> StateMachineProcedure state: e.g. SimpleStateMachineProcedure
> state=RUNNABLE:SERVER_CRASH_ASSIGN
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
