-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use this service in Lookup attribute? #20
Comments
I can definitely help you out. What version of NiFi are you using? |
Hi, I am using NiFi 1.22 currently. I had to hack the source code a tiny bit to use the service with LookupAttribute as it requires a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I would like to use this service in LookupAttribute processor to find an Agent ID based on Agent Name and Agent Version that I get from FlowFile.
I've tried using this service in LookupAttribute but I don't know how to provide those two values to the service through the processor.
In your example you say that this service supports named parameters, for example:
So I've tried putting it in the service with following query:
I've tried many ways of trying to provide values for these two parameters, but couldn't get it to work with LookupAttribute.
Then I've tried to simplify the SQL query, just to see if I can get it to work and used:
In LookupAttribute I've defined the property agent _id and given it various values such as "agent_name", "${agent_name}", "agent_name=${agent_name}", "agent_name,${agent_name}", and more, but it didn't work, every time I got following error when I tried running the LookupAttribute processor:
I've tried looking through source code to figure out how to fix this, but I have no idea.
Could you help me?
The text was updated successfully, but these errors were encountered: