Cyrine, The “nifi-api” dependency is not the official dependency, unfortunately. That is an unrelated project that is not associated with Apache NiFi. We have not yet published the api to PyPI because there hasn't been an official release of 2.0 yet - we’re still on Milestone releases, and unfortunately PyPI requires somewhat strict conventions on versioning.
I do think we should go ahead and publish the api, though, even if it means we use a somewhat unconventional name for the module, or establish a versioning scheme that’s slightly different than we’d normally use. In the meantime, I’ve just pointed my IDE to the source code for the FlowFileTransform, FlowFileTransformResult, etc. classes. Thanks -Mark > On Jul 9, 2024, at 7:19 AM, Cyrine ANENE <cyrine.an...@supcom.tn> wrote: > > Dear NiFi dev team, > > I hope this email finds you well. I am writing to seek your assistance > regarding an issue I am experiencing with the NiFiAPI in Python. > > Despite having verified that all the requirements are met and installing all > the required dependencies, I am encountering a problem where my VS Code does > not recognise the importation of NiFi api, it was installed with "pip install > nifi-api" and I used all the possible syntaxes possibles: > - from nifi_api.flowfiletransform import FlowFileTransform, > FlowFileTransformResult > - from nifiapi.flowfiletransform import FlowFileTransform, > FlowFileTransformResult > -from nifi-api.flowfiletransform import FlowFileTransform, > FlowFileTransformResult > > I also another problem with my custom processors. I have packaged my NiFi > custom processor in a NAR folder and added it to the lib/ directory, and > tried another method as adding it to the python/extensions and neither of > them worked as i still does not see my processor when i search for it in the > user interface. > > I am currently working with the nifi-2.0.0-M4 version. > > I would greatly appreciate any guidance or insights you can provide to help > resolve this issue. > > Thank you in advance for your support. I look forward to your response. > > Best regards, > Cyrine Anene.
