Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/706
Tested out the trigger serially and appears to be working as expected. I am
a +1 to merge this in, do you want to squash the commits first?
---
If your project is set up for it, you can reply to this e
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/706
TriggerSerially sounds fair knowing that we should be able to remove it in
the future
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/706
Yeah I think that's a bug in this version of Hive:
https://issues.apache.org/jira/browse/HIVE-13725
For now I'd like to make the processor TriggerSerially (unless there are
any objections),
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/706
Error handling on the relationships is looking good, thanks for making
those updates.
One more thing I ran into, when I set concurrent tasks to 2 on the
PutHiveStreamingProcessor and I was gene
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/706
Yes that's a good idea, will update, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/706
Latest update is looking good... one thing I noticed, if you send in an
Avro file that does not have the partition columns of the table, it throws an
IOException around line 435 when trying to extract t
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/706
Per an offline discussion with @bbende, we decided a good way to handle the
outgoing flow files is to have a "success", "failure", and "retry"
relationship. If a connection / environment error occurs
