t;>> there's no point in keeping it in the commitlog as well.
>>>
>>> Try without flushing and see if you can see your operations there.
>>>
>>> Regards
>>>
>>> On Wed, 23 Nov 2016 at 11:04 Kamesh <kam.iit...@gmail.com> wrote:
>&
you can see your operations there.
>>
>> Regards
>>
>> On Wed, 23 Nov 2016 at 11:04 Kamesh <kam.iit...@gmail.com> wrote:
>>
>> Hi All,
>> I am trying to read cassandra commit log files, but unable to do it. I
>> am experimenting this with 1 node clus
> Hi All,
> I am trying to read cassandra commit log files, but unable to do it. I am
> experimenting this with 1 node cluster(laptop)
>
> Cassandra Version : *3.8*
> Updated cassadra.yaml with *cdc_enabled: true*
>
> After executing the below statments and flushing me
am.iit...@gmail.com> wrote:
>
>> Hi All,
>> I am trying to read cassandra commit log files, but unable to do it. I
>> am experimenting this with 1 node cluster(laptop)
>>
>> Cassandra Version : *3.8*
>> Updated cassadra.yaml with *cdc_enabled: true*
>>
sandra Version : *3.8*
> Updated cassadra.yaml with *cdc_enabled: true*
>
> After executing the below statments and flushing memtables, tried reading
> commit log files, but there are no cdc events correpsonding to *test*
> keyspace.
>
> CREATE KEYSPACE *test* WI
Hi All,
I am trying to read cassandra commit log files, but unable to do it. I am
experimenting this with 1 node cluster(laptop)
Cassandra Version : *3.8*
Updated cassadra.yaml with *cdc_enabled: true*
After executing the below statments and flushing memtables, tried reading
commit log files
