Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
References: <CAOi=ZKQpSLCz+NLJNcNCSqwjL9bS9LRRf1brndTQ6K0QwTJnFA@mail.gmail.com>
 <CAGctwUDW0=L9d-0RCVJJaAZc0iG5QVhxo3Eq0ibY0z1f2ZHXNQ@mail.gmail.com> <CAOi=ZKTWW4vJmmVfBZWfmBDJ=_1iQ4nRL+akiN2LwgX+dWz=sA@mail.gmail.com>
In-Reply-To: <CAOi=ZKTWW4vJmmVfBZWfmBDJ=_1iQ4nRL+akiN2LwgX+dWz=sA@mail.gmail.com>
From: Jim Witschey <jim.witschey@datastax.com>
Date: Tue, 07 Jun 2016 15:35:25 +0000
Message-ID: <CAGctwUCgXuokXcuQgCQswt4Lke05Ha2dLeaQSFmNDkm0cjGG2A@mail.gmail.com>
Subject: Re: Subscribe to Cassandra Commit Log
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a113d306aa6d4b30534b1f00d
archived-at: Tue, 07 Jun 2016 15:35:41 -0000

--001a113d306aa6d4b30534b1f00d
Content-Type: text/plain; charset=UTF-8

>
> is there any documentation for this feature
>

I'm not sure what the state of documentation is for Change Data Capture.
The best docs may be the design document linked in the comments on the
ticket, which I think is current.


> perhaps what I am looking for is the reading the commit logs in real time
> to capture all the updates fired to the corresponding tables.
>

I believe this sounds like a CDC use case. Trust the discussion on the
ticket more than my summary here, but: the changes in CASSANDRA-8844 expose
some previously-internal commitlog-reading behavior. This allows users to
implement their own code to consume changes to commitlogs on tables where
the feature is enabled.

Also any update on the tentative release of this branch?
>

The patch is currently under review, but currently targeting a 3.8 release.
3.8 should be released in the next two months as part of the tick-tock
release schedule.

--001a113d306aa6d4b30534b1f00d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"ltr"><div>is there any documentation for this feature</div></di=
v></blockquote><div><br></div><div>I&#39;m not sure what the state of docum=
entation is for Change Data Capture. The best docs may be the design docume=
nt linked in the comments on the ticket, which I think is current.</div><di=
v>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>perhaps =
what I am looking for is the reading the commit logs in real time to captur=
e all the updates fired to the corresponding tables.</div></div></blockquot=
e><div><br></div><div>I believe this sounds like a CDC use case. Trust the =
discussion on the ticket more than my summary here, but: the changes in CAS=
SANDRA-8844 expose some previously-internal commitlog-reading behavior. Thi=
s allows users to implement their own code to consume changes to commitlogs=
 on tables where the feature is enabled.</div><div><br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div dir=3D"ltr"><div>Also any update on the tentative rel=
ease of this branch?</div></div></blockquote><div><span style=3D"line-heigh=
t:1.5"><br></span></div><div><span style=3D"line-height:1.5">The patch is c=
urrently under review, but currently targeting a 3.8 release. 3.8 should be=
 released in the next two months as part of the tick-tock release schedule.=
</span><br></div></div></div>

--001a113d306aa6d4b30534b1f00d--