[
https://issues.apache.org/jira/browse/FLUME-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gonglinglei updated FLUME-3215:
-------------------------------
Description:
using hive sink in hive version greater than 2.0.0, when write to a timeouted
txn, it will mark the whole txnBatch as dead, and doing abortRemaingingTxns in
a closed txnBatch is apparently illegal
TransactionBatch in version 1.0.0 didn't provide the close check, but I think
it can still cause HiveWriter close error maybe as a StreamingException
was:
using hive sink in hive version greater than 2.0.0, when write to a timeouted
txn, it will mark the whole txnBatch as dead, and doing abortRemaingingTxns in
a closed txnBatch is apparently illegal
TransactionBatch in version 1.0.0 didn't provide the close check, but I think
it can still cause HiveWriter close error maybe as a StreamingException, so my
suggestion is to upgrade hive api version to 2.0.0, and add close check in
abortRemaingingTxns method
> abortRemainingTxns when txnBatch is already closed
> --------------------------------------------------
>
> Key: FLUME-3215
> URL: https://issues.apache.org/jira/browse/FLUME-3215
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Reporter: gonglinglei
> Priority: Major
>
> using hive sink in hive version greater than 2.0.0, when write to a timeouted
> txn, it will mark the whole txnBatch as dead, and doing abortRemaingingTxns
> in a closed txnBatch is apparently illegal
>
> TransactionBatch in version 1.0.0 didn't provide the close check, but I think
> it can still cause HiveWriter close error maybe as a StreamingException
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
