Hi Hong!

What are you seeking to do with the rate data after extracting?  Is the
number of rates fixed?  If not, not sure there is an easy path forward with
just EvaluateJsonPath to make this happen.

I am wondering if SplitJson might be appropriate to use as a follow-on, but
could use some more context to see how these items are handled in terms of
their flow.

Thanks!

--aldrin

On Wed, Apr 6, 2016 at 1:44 PM, Hong Li <[email protected]>
wrote:

> The issue I run into there is when I specify under EvaluationJsonPath,
>
> firstRateValue = $.rate[0]
>
> $.rate[0] is a scalar value that is assigned to the processor property
> firstRateValue, which is also a scalar.  But $.rate[*] is an array or
> vector.  Nifi will send error there and the process will fail if I do this
> under EvaluationJsonPath:
>
> rateValue = $.rate[*]
>
>
> Any further comment and suggestion?
>
> Thanks.
> Hong
>
>
>
>
> *Hong Li*
>
> *Centric Consulting*
>
> *In Balance*
> (888) 781-7567 office
> (614) 296-7644 mobile
> www.centricconsulting.com | @Centric <https://twitter.com/centric>
>
> On Wed, Apr 6, 2016 at 12:54 PM, Thad Guidry <[email protected]> wrote:
>
>> $.rate[*]
>>
>> sorry, forget to tell you your answer.
>>
>> Thad
>> +ThadGuidry <https://www.google.com/+ThadGuidry>
>>
>>
>>
>

Reply via email to