[
https://issues.apache.org/jira/browse/NIFI-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433058#comment-17433058
]
Matt Burgess commented on NIFI-4358:
------------------------------------
[[email protected]] Did you try on a live instance? The way the code is
written it looks like compression would never work, as the enum object is being
compared to a String, which would never be equal. Also the compression property
was not added to PutCassandraRecord (that one doesn't use the common properties
from AbstractCassandraProcessor for some reason). Having said that, I made
those changes and tried against a CosmosDB instance, and it didn't matter what
the compression was on the table (defaults to LZ4 but I tried one with Snappy)
and what the Compression property was set to. All writing and reading happened
without any compression mismatch errors or anything like that.
> Capability to activate compression on Cassandra connection
> ----------------------------------------------------------
>
> Key: NIFI-4358
> URL: https://issues.apache.org/jira/browse/NIFI-4358
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: Jean-Louis
> Assignee: Sandish Kumar HN
> Priority: Minor
> Labels: cassandra
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It's interesting to activate compression in some use cases. Can we add a
> processor property to set a compression. If we consider Cassandra Java
> Driver, this can be done using this
> (withCompression(ProtocolOptions.Compression.LZ4))
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
