[
https://issues.apache.org/jira/browse/NIFI-4561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291838#comment-16291838
]
ASF GitHub Bot commented on NIFI-4561:
--------------------------------------
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2243#discussion_r157098806
--- Diff:
nifi-commons/nifi-write-ahead-log/src/test/java/org/wali/TestMinimalLockingWriteAheadLog.java
---
@@ -538,7 +538,7 @@ public void
testRecoverFileThatHasTrailingNULBytesAndTruncation() throws IOExcep
@Test
public void testRecoverFileThatHasTrailingNULBytesNoTruncation()
throws IOException {
final int numPartitions = 5;
- final Path path =
Paths.get("target/testRecoverFileThatHasTrailingNULBytes");
+ final Path path =
Paths.get("target/testRecoverFileThatHasTrailingNULBytesNoTruncation");
--- End diff --
This change doesn't look like it belongs?
> ExecuteSQL Stopped Returning FlowFile for non-ResultSet Queries
> ---------------------------------------------------------------
>
> Key: NIFI-4561
> URL: https://issues.apache.org/jira/browse/NIFI-4561
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Peter Wicks
> Assignee: Peter Wicks
>
> While most people use ExecuteSQL for Select statements, some JDBC drivers
> allow you to execute any kind of statement, including multi-statement
> requests.
> This allowed users to submit multiple SQL statements in one JDBC Statement
> and get back multiple result sets. This was part of the reason I wrote
> [NIFI-3432].
> After having NIFI-3432 merged, I found that some request types no longer
> cause a FlowFile to be generated because there is no ResultSet. Also, if
> request types are mixed, such as an insert followed by a Select, then no
> ResultSet is returned because the first result is not a result set but an
> Update Count.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
