You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Quan Green (JIRA)" <ji...@apache.org> on 2018/01/03 10:27:01 UTC
[jira] [Commented] (NIFI-4493) PutCassandraQL Option to Disable
Prepared Statements
[ https://issues.apache.org/jira/browse/NIFI-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309433#comment-16309433 ]
Quan Green commented on NIFI-4493:
----------------------------------
I have also come across a similar issue where the number of ?'s is impractical and would like to disable prepared statements as it spams out logs and uses extra resources.
> PutCassandraQL Option to Disable Prepared Statements
> ----------------------------------------------------
>
> Key: NIFI-4493
> URL: https://issues.apache.org/jira/browse/NIFI-4493
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.4.0
> Reporter: Ben Thorner
> Priority: Minor
> Labels: cassandra, putcassandraql
>
> Cassandra complains when using this processor to perform large numbers of changing queries. In our scenario, we are using batch statements to insert incoming data.
> INFO [ScheduledTasks:1] 2017-10-17 16:13:35,213 QueryProcessor.java:134 - 3849 prepared statements discarded in the last minute because cache limit reached (66453504 bytes)
> In this scenario, I don't think it's feasible to use prepared statements, as the number of ? parameters is impractical. Could we instead have an option to disable prepared statements?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)