[
https://issues.apache.org/jira/browse/HBASE-22039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791522#comment-16791522
]
Hadoop QA commented on HBASE-22039:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 2m 10s{color}
| {color:red} HBASE-22039 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-22039 |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/16376/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Should add the synchronous parameter for the XXXSwitch method in AsyncAdmin
> ---------------------------------------------------------------------------
>
> Key: HBASE-22039
> URL: https://issues.apache.org/jira/browse/HBASE-22039
> Project: HBase
> Issue Type: Sub-task
> Components: Admin, asyncclient, Client
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
> Attachments: HBASE-22039-v1.patch, HBASE-22039.patch
>
>
> For now we always pass true to HMaster, maybe the decision is that user just
> do not need to calling get on the returned Future if it wants asynchronous.
> But the problem here is that, the return value is not void, it is a boolean,
> which is the previous state of the flag, sometimes users do not need to wait
> until the previous transitions or split/merge to complete, but they still
> want to get the previous value of the flag.
> So we still need to provide the synchronous parameter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
