xiaochen-zhou commented on code in PR #8279:
URL: https://github.com/apache/seatunnel/pull/8279#discussion_r1882020496
##########
seatunnel-connectors-v2/connector-hbase/src/main/java/org/apache/seatunnel/connectors/seatunnel/hbase/client/HbaseClient.java:
##########
@@ -77,7 +80,31 @@ private HbaseClient(Connection connection, HbaseParameters
hbaseParameters) {
hbaseParameters.getNamespace(),
hbaseParameters.getTable()))
.pool(HTable.getDefaultExecutor(hbaseConfiguration))
-
.writeBufferSize(hbaseParameters.getWriteBufferSize());
+
.writeBufferSize(hbaseParameters.getWriteBufferSize())
+ .listener(
+ (e, mutator) -> {
+ for (int i = 0; i <
e.getNumExceptions(); i++) {
Review Comment:
> what's happend when all retry failed?
It is indeed a bug, and I haven't thought of a good way to prevent this
situation from occurring. Moreover, there is currently no relevant log
information when HBase write failures happen.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
