Jason,
Sorry to hear of the troubles. With respect to bug #1, you shouldn't have
to recreate the entire instance. Having said that, InvokeScriptedProcessor
(ISP) is a strange beast in terms of its configuration lifecycle, since a
scripted processor is enclosed and managed by its parent
Jason,
Sorry to hear you had a frustrating experience with InvokeScriptedProcessor.
While it is marked with the “Experimental” annotation for just this reason
(it’s performed well with standard behaviors but we’re sure there are still
some edge cases remaining), no one should accept
wasted for nothing) for me with InvokeScriptedProcessor:
1) After correcting syntax errors in my property definitions, I had to
completely delete and recreate my InvokeScriptedProcessor instance instead of
just updating the text in the processor - otherwise the error still reoccurs
even after
pertyDescriptor descriptor, String oldValue,
String newValue) { }
@Override
List getPropertyDescriptors() {
return [DBCP_SERVICE, DB_QUERY, FILENAME] as
List
}
@Override
String getIdentifier() { return 'MySQLToJSON-InvokeScr
:
---
InvokeScriptedProcessor[id=b5e567cf-0157-1000-cea6-4dc6cbaed0e3]
InvokeScriptedProcessor[id=b5e567cf-0157-1000-cea6-4dc6cbaed0e3] failed to
process session due to java.lang.reflect.UndeclaredThrowableException:
java.lang.reflect.UndeclaredThrowableException
---
I have debugging log.info lines on every call
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/211
---
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
enabled and wishes so, or if the feature is
Github user mattyb149 commented on the pull request:
https://github.com/apache/nifi/pull/211#issuecomment-182162160
LGTM, to @joewitt for the +1 and merge
---
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
