CaptureChangeMySQL - initial binlog filename not working?

[Katrina Henrie <kh...@imaginehealth.com>]

I have a flow working using the CaptureChangeMySQL processor, however, when
I set the Initial Binlog Filename to the most recent binlog (bin.000058
with position starting at 1), the processor still begins at bin.000001

Is this a bug? Am I entering the data wrong?

Any help would be appreciated!

Thanks

-- 
_Email Confidentiality Notice: The information contained in this 
transmission is confidential, proprietary or privileged and may be subject 
to protection under the law. The message is intended for the sole use of 
the individual or entity to whom it is addressed. If you are not the 
intended recipient, you are notified that any use, distribution or copying 
of the message is strictly prohibited and may subject you to criminal or 
civil penalties. If you received this transmission in error, please contact 
the sender immediately by replying to this email and delete the material 
from any computer._

Re: CaptureChangeMySQL - initial binlog filename not working?

[henriek <kh...@imaginehealth.com>]

<it helps when one reads> 
I just saw that on the processor note for the state update interval - sorry!
i'm having a blonde day.. week... life.

Thank you very much! Your answers are always informative, patient, helpful,
and appreciated :)

Katrina 



--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Re: CaptureChangeMySQL - initial binlog filename not working?

[Matt Burgess <ma...@apache.org>]

Katrina,

During one execution of the CDC processor, it will handle all
available CDC events. State is updated according to the setting of the
State Update Interval value. By default it is set to 0, which means
state will only be updated when an execution of the processor is
completed (or the processor is stopped). If CDC events are streaming
in quickly or there are a lot of them queued up, it could take a while
before state is updated for the NiFi instance/cluster. You could set
State Update Interval to something like 100 msec or whatever, and it
will update the state periodically while still processing incoming CDC
events.

Regards,
Matt

On Mon, Jul 23, 2018 at 12:36 PM henriek <kh...@imaginehealth.com> wrote:
>
> Matt,
>
> I knew I must have been missing something - the setting was set to true.
> You're my hero! <fangirling> Thank you!
>
> (PS - it is working, but does it normally take a while for the viewable
> state of the processor to update after it's been cleared? I've cleared state
> a couple of times in the past and noticed that it will be blank for a while
> before finally showing state...)
>
> Best,
> Katrina
>
>
>
> --
> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Re: CaptureChangeMySQL - initial binlog filename not working?

[henriek <kh...@imaginehealth.com>]

Matt,

I knew I must have been missing something - the setting was set to true.
You're my hero! <fangirling> Thank you!

(PS - it is working, but does it normally take a while for the viewable
state of the processor to update after it's been cleared? I've cleared state
a couple of times in the past and noticed that it will be blank for a while
before finally showing state...)

Best,
Katrina



--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Re: CaptureChangeMySQL - initial binlog filename not working?

[Matt Burgess <ma...@apache.org>]

Katrina,

What is "Retrieve All Records" set to? It defaults to true, which will
ignore the Initial Binlog Filename/Position settings. If you want to
"skip ahead" to bin.000058, you should clear the processor's state
(right-click on the processor and choose View State, then "Clear
state"), set "Retrieve All Records" to false, and enter bin.000058 as
the Initial Binlog Filename. Please let me know if that doesn't work
for you and I'll take a look.

Regards,
Matt

On Fri, Jul 20, 2018 at 12:54 PM Katrina Henrie
<kh...@imaginehealth.com> wrote:
>
> I have a flow working using the CaptureChangeMySQL processor, however, when I set the Initial Binlog Filename to the most recent binlog (bin.000058 with position starting at 1), the processor still begins at bin.000001
>
> Is this a bug? Am I entering the data wrong?
>
> Any help would be appreciated!
>
> Thanks
>
> Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.