[
https://issues.apache.org/jira/browse/NIFI-12137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-12137:
----------------------------
Description:
In a flow using a FlowFileTransform I am seeing data when I route it to
faillure also going to original. If routed to failure it should not go to
original. Original should only be when success is the chosen route.
We should change ExpressionLanguageScope.LIMITED to ENVIRONMENT.
We should try to use python conventions on all method names instead of Java
conventions.
Can we define the 'logger' that gets injected to implementations so code
completion can work in IDEs in the meantime?
was:
Built a python processor. Deployed as version 0.0.1. Updated to 0.0.2
replacing original file. Updated to 0.0.3. Then started just keeping same
version and restarting processor. However, on restart I received this output
{noformat}
2023-09-26 13:00:10 2023-09-26 20:00:06,984 ERROR [NiFi Web Server-140]
o.a.n.n.StandardExtensionDiscoveringManager Could not instantiate class of type
python.LookupAddress using ClassLoader for bundle
org.apache.nifi:python-extensions:0.0.1-SNAPSHOT
2023-09-26 13:00:10 py4j.Py4JException: An exception was raised by the Python
Proxy. Return Message: Traceback (most recent call last):
2023-09-26 13:00:10 File
"/opt/nifi/nifi-current/python/framework/py4j/java_gateway.py", line 2466, in
_call_proxy
2023-09-26 13:00:10 return_value = getattr(self.pool[obj_id],
method)(*params)
2023-09-26 13:00:10 File
"/opt/nifi/nifi-current/./python/framework/Controller.py", line 52, in
createProcessor
2023-09-26 13:00:10 processorClass =
self.extensionManager.getProcessorClass(processorType, version, work_dir)
2023-09-26 13:00:10 File
"/opt/nifi/nifi-current/python/framework/ExtensionManager.py", line 138, in
getProcessorClass
2023-09-26 13:00:10 raise ValueError('Invalid Processor Type: No module is
known to contain Processor of type ' + type + ' version ' + version)
2023-09-26 13:00:10 ValueError: Invalid Processor Type: No module is known to
contain Processor of type LookupAddress version 0.0.1-SNAPSHOT
2023-09-26 13:00:10
2023-09-26 13:00:10 at py4j.Protocol.getReturnValue(Protocol.java:476)
2023-09-26 13:00:09 tail: '/opt/nifi/nifi-current/logs/nifi-app.log' has been
replaced; following new file
{noformat}
In a flow using a FlowFileTransform I am seeing data when I route it to
faillure also going to original. If routed to failure it should not go to
original. Original should only be when success is the chosen route. Will
replicate and add more info here.
We should change ExpressionLanguageScope.LIMITED to ENVIRONMENT.
We should try to use python conventions on all method names instead of Java
conventions.
Can we define the 'logger' that gets injected to implementations so code
completion can work in IDEs in the meantime?
> Improve Java Python processor behaviors in NiFi 2x
> --------------------------------------------------
>
> Key: NIFI-12137
> URL: https://issues.apache.org/jira/browse/NIFI-12137
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Joe Witt
> Priority: Major
>
> In a flow using a FlowFileTransform I am seeing data when I route it to
> faillure also going to original. If routed to failure it should not go to
> original. Original should only be when success is the chosen route.
> We should change ExpressionLanguageScope.LIMITED to ENVIRONMENT.
> We should try to use python conventions on all method names instead of Java
> conventions.
> Can we define the 'logger' that gets injected to implementations so code
> completion can work in IDEs in the meantime?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
