[
https://issues.apache.org/jira/browse/NIFI-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614994#comment-16614994
]
ASF subversion and git services commented on NIFI-3425:
-------------------------------------------------------
Commit 4a25402c1af7e51b1a7bf61f185dc58b5c40e90b in nifi's branch
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4a25402 ]
NIFI-3425: Provide ability to cache CQL statements
This closes #2986.
Co-authored-by: Michael A Giroux <[email protected]>
Signed-off-by: Mark Payne <[email protected]>
> 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)
