Hi Matt,
Sorry for this inconvenience. The dynamic property support from version
1.0.0. Since, i am using 0.6.0 version.
Regards,
Ravisankar
On Fri, Sep 9, 2016 at 12:56 AM, Ravisankar Mani <rrav...@gmail.com> wrote:
> Hi Matt,
>
> Thanks for your reply.
> I can add the new property like initial.maxvalue.id and set the
> value(Like 1) using add property option in this processor. But i can see
> the error message like " 'initial.maxvalue.id' validated against '1' is
> invalid because 'initial.maxvalue.id' is not a supported property " . May
> be i have added the dynamic property in wrong way.
> Can you please help me to resolve the problem?
>
>
> Thanks,
> Ravisankar
>
>
> On Thu, Sep 8, 2016 at 8:43 AM, Matt Burgess <mattyb...@apache.org> wrote:
>
>> Ravisankar,
>>
>> The dynamic property needs to have a certain name, in general of the
>> form initial.maxvalue.{max_value_column}. So if you have a max value
>> column called last_updated, you will want to add a dynamic property
>> called initial.maxvalue.last_updated, and you set the value to
>> whatever you want the initial value to be. At that point the processor
>> will only fetch rows where last_update > the value you specified.
>>
>> Regards,
>> Matt
>>
>> On Thu, Sep 8, 2016 at 8:31 AM, Ravisankar Mani <rrav...@gmail.com>
>> wrote:
>> > Hi All,
>> >
>> > I have used 'QueryDatabaseTable' processor in my workflow(incremental
>> update
>> > ETL process), initially , Its working properly once executed the job
>> without
>> > setiing max value column(first time only) and then setting the max value
>> > columns(because the max value doesn't know processor) . But i need to
>> set
>> > the max value column initially , in this case , i saw the dynamic
>> property
>> > like 'Initial Max Value' in nifi guide. But i don't know how to set the
>> > property in this processor.
>> > Can you please help me to resolve the problem?
>> >
>> >
>> > Regards,
>> > Ravisankar
>>
>
>
