The virtual table could read the data out of the audit log, just like
it could read a hosts file or list the output of the ps command.
On Wed, Apr 3, 2019 at 8:02 PM Sagar wrote:
>
> Thanks Alex.
>
> I was going through the implementation of Virtual tables thus far and the
> data that we get
Thanks Alex.
I was going through the implementation of Virtual tables thus far and the
data that we get when we query against them seems to be more point in time
like CachesTable or fairly static like Settings. Having said that, audit
log's nature of data doesn't fall in either of the 2
Thanks for the recommendation Russell. Haven't looked into that code yet,
but the docs didn't seem to indicate if it wrote sstables directly instead
of going through normal write path.
On Wed, Apr 3, 2019, 11:11 AM Russell Spitzer
wrote:
> I would recommend using the Spark Cassandra Connector
Hi All
Initially the ASF as an organisation was planning to apply as a
mentoring organisation for Google Season of Docs on behalf of all Apache
projects but if accepted the maximum number of technical writers we
could allocated is two. Two technical writers would probably not be
enough to
I would recommend using the Spark Cassandra Connector instead of the Hadoop
based writers. The Hadoop code has not had a lot of love in a long time. See
https://github.com/datastax/spark-cassandra-connector
On Wed, Apr 3, 2019 at 12:21 PM Brett Marcott
wrote:
> Hi folks,
>
> I am noticing my
Hi folks,
I am noticing my spark jobs being stuck when using the
org.apache.cassandra.hadoop.cql3.CqlBulkRecordWriter/CqlBulkOutputFormat.
It seems that whenever there is a stream failure it may be expected behavior
based on the code to infinite loop.
Here are one executors logs:
19/04/03
