-
Couldn't load subscription status.
- Fork 3.4k
HBASE-26867 Introduce a FlushProcedure #5353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
| // the hbase hadoop version does not match the running hadoop version or | ||
| // the FlushTableProcedure is disabled, if that happens, we need fall back | ||
| // to the old flush implementation. | ||
| legacyFlush(tableName, columnFamilies); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So when users call flushAsync directly, we can not fallback to legacyFlush automatically?
|
@frostruan Any updates here? Thanks. |
|
Sorry, Duo, I don't know what I should update here. If you mean the problem that the legacyFlush method can not fallback, I have already replied and explained my thoughts, would you mind looking it first? :) |
|
I can not see your reply, maybe you forget to push the submit button? |
|
oh sorry ... have no idea what went wrong, so let me copy the reply here. Yes. From the perspective of fallback, it's better to make |
XXXAsync methods are common in the Admin interface so we should provide it. And how could our users handle the unsupported exception in upper layer? We do not expose the legacyFlush method to them, they can only retry on the same method and then get the same exception again? |
Our user can fallback to the old flush implementation by calling flush method. If our users really need asynchronous calls, maybe we can suggest them to consider AsyncHBaseAdmin#flush API in the doc. Do you think it is necessary for us to implement fallback logic in the HBaseAdmin#flushAsync method? |
It will be confusing to users that flush and flushAsync are different. We should support the fallback logic also in flushAsync. |
Ok. Let me fix this. Thanks Duo. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
Please fix the spotless error? Thanks. |
|
Yes, I am working on fixing this problem. I executed the mvn spotless:apply before the last three commits, and this patch does not involve the problematic file. A bit strange .... let me dig more :) |
|
Maybe it is because others merged a PR without fixing all the spotless issues... |
|
Very possible. Let me check the git log. |
3540597 to
b722b2b
Compare
|
💔 -1 overall
This message was automatically generated. |
|
sorry Duo, I don't know how to fix this problem .... would you mind helping me to see how to solve it ? Thanks. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
It's OK now. The spotless result after this PR is OK. The problem is on branch-2 itself. Let me merge. |
No description provided.