Hi,
Thanks a lot for the suggestion. I didn’t know about jsonpath EL functions. I
can easily implement that in my use case.
- Ashwin
On 2018/11/27 18:52:05, Bryan Bende wrote:
> Unfortunately I don't think there is a good way to interpret the value>
> of the key when it is Avro because we
Kevin,
thank you for your answer and sorry for the long delay.
I agree that paging is a concern and I thought about it as well but I also
agree that in this case it's probably not worth the hassle.
I'll go ahead and create a Jira. I plan on providing a patch but not sure
when I'll get to it.
Unfortunately I don't think there is a good way to interpret the value
of the key when it is Avro because we don't have any expression
language functions that understand Avro or record-oriented values.
The main option would be to change how the data is being produced in some way...
- Put the
Hi,
Its not encoding issue. I am not able to figure out how to read Kafka key
itself.
eg.
Kafka key = {type: foo, meta: etc, etc }
Kafka message = {Avro Payload}
I want to use RouteOnAttribute processor based on type = foo or bar. For this
to happen, I need to extract value foo from Kafka.key
I have small cluster with 3 instances of NiFi, and found some problem, as I
think.
Processor QueryDatabaseTable set to work on PrimaryNode only and Concurent
tasks set to 1. Run Schedule set to large value (something like 20
minutes), so I expect only one execution at a time. While query is
