Description
Seems the current approach of implementing AsyncTable is in trouble as we expose some netty classes in our public interfaces.
I agree that we should not do this. The AsyncTable should be implemented using the asynchronous protobuf stub, and we could use CompletableFuture or Deferred instead of netty's Future. I think the problem of netty's future is that it is tighten with netty's executor. This makes it impossible to use without netty.
Attachments
Issue Links
- blocks
-
HBASE-13784 Add Async Client Table API
-
- Closed
-
-
HBASE-15921 Add first AsyncTable impl and create TableImpl based on it
-
- Closed
-
1.
|
Remove AsyncRpcChannel related stuffs |
|
Closed | Duo Zhang |
2.
|
Reset RpcController before retry |
|
Closed | Duo Zhang |
3.
|
Revisit the implementation of PayloadCarryingRpcController |
|
Closed | Duo Zhang |
4.
|
Add more ipc tests |
|
Closed | Duo Zhang |
5.
|
Move cell block related code out of IPCUtil |
|
Closed | Duo Zhang |
6.
|
Implement RpcChannel for RpcClientImpl |
|
Closed | Duo Zhang |
7.
|
Refactor and reimplement RpcClient |
|
Closed | Duo Zhang |