[jira] [Commented] (NIFI-3425) Cache prepared statements in PutCassandraQL

["Matt Burgess (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598768#comment-16598768 ] 

Matt Burgess commented on NIFI-3425:
------------------------------------

Sorry I lost track of this. The patch does not go in cleanly as it changes some files that are not associated with the actual fix. I will start with Michael's patch and make some modifications, he will be listed as co-author of the commit in the Pull Request that I issue. 

> Cache prepared statements in PutCassandraQL
> -------------------------------------------
>
>                 Key: NIFI-3425
>                 URL: https://issues.apache.org/jira/browse/NIFI-3425
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Minor
>         Attachments: NIFI-3425.patch
>
>
> Currently PutCassandraQL supports prepared statements (using ? parameters much like JDBC SQL statements) via flow file attributes specifying the type and value of the parameters.
> However, the prepared statement is created (and thus possibly re-created) for each flow file, which neuters its effectiveness over literal CQL statements. The driver warns of this:
> 2017-01-31 14:30:54,287 WARN [cluster1-worker-1] com.datastax.driver.core.Cluster Re-preparing already prepared query insert into test_table (id, timestamp, id1, timestamp1, id
> 2, timestamp2, id3, timestamp3, id4, timestamp4, id5, timestamp5, id6, timestamp6) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?);. Please note that preparing the same query
>  more than once is generally an anti-pattern and will likely affect performance. Consider preparing the statement only once.
> Prepared statements should be cached and reused where possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)