You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Shawn Weeks (JIRA)" <ji...@apache.org> on 2019/03/20 15:39:00 UTC
[jira] [Comment Edited] (NIFI-5251) ExecuteGroovyScript Tries to
Set AutoCommit for Hive
[ https://issues.apache.org/jira/browse/NIFI-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797271#comment-16797271 ]
Shawn Weeks edited comment on NIFI-5251 at 3/20/19 3:38 PM:
------------------------------------------------------------
I think the whole autoCommit routine for this processor should be revisited. It appears that at the end of the process it sets autocommit to true even if it wasn't originally true. Shouldn't we be handling autocommit at either the dbcpconnection pool or just not messing with it at all?
was (Author: absolutesantaja):
I think the whole autoCommit routine for this processor should be revisited. It appears that at the end of the process it sets autocommit to true even if it wasn't originally true. Shouldn't be handling autocommit at either the dbcpconnection pool or just not messing with it at all?
> ExecuteGroovyScript Tries to Set AutoCommit for Hive
> ----------------------------------------------------
>
> Key: NIFI-5251
> URL: https://issues.apache.org/jira/browse/NIFI-5251
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: RedHat 6, HDP 2.6.4, assumed to affect current versions as well.
> Reporter: Shawn Weeks
> Priority: Trivial
>
> The onInitSQL method of ExecuteGroovyScript tries to set autoCommit to false on the connection. For Hive connections this causes a steady stream of warnings in the log.
>
> {code:java}
> 2018-05-29 12:23:04,407 WARN [Timer-Driven Process Thread-3] org.apache.hive.jdbc.HiveConnection Request to set autoCommit to false; Hive does not support autoCommit=false.{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)