mirror of https://github.com/apache/nifi.git
1898ad44be
Calls to `trigger()` may be called concurrently from different threads, however the PutKudu processor is storing the `kuduSession` in a class level field. This can result in the logging issue reported in NIFI-6895 and likely other unusual anomolies including performace issues depending on the processor configuration. Additionally the `operationType` was also stored in a class level field and could be set concurrently resulting in the incorrect operation type used. This patch fixes the issue by moving both kuduSession and operationType to be local. Additionaly some minor code cleanup was included. An integration test, ITPutKudu, was added and used to manual verify the logging issue existed and is fixed by this patch. I ran the test using `mvn -Pintegration-tests verify -Dtest=ITPutKudu` Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com> This closes #3910. |
||
|---|---|---|
| .. | ||
| nifi-kudu-controller-service | ||
| nifi-kudu-nar | ||
| nifi-kudu-processors | ||
| pom.xml | ||