[
https://issues.apache.org/jira/browse/NIFI-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981135#comment-15981135
]
Matt Burgess commented on NIFI-3728:
------------------------------------
I agree that the emission of DDL statements should be configurable by the user.
It is indeed dangerous, as you point out it may need some changes for the
target database (via ReplaceText for example) or even RouteOnContent to ensure
the statements are only applied to the target if the user desires it. Even
then a routing processor will upset the sequence IDs, rendering the flow
useless for a processor like EnforceOrder, so this filtering needs to be
performed at the source (CaptureChangeMySQL).
> CaptureChangeMySQL to capture truncate table statement
> ------------------------------------------------------
>
> Key: NIFI-3728
> URL: https://issues.apache.org/jira/browse/NIFI-3728
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.2.0
> Reporter: Koji Kawamura
> Fix For: 1.2.0
>
>
> CaptureChangeMySQL has several specific queries to capture, such as 'alter
> table', 'create table' and 'drop table' ... etc. However, it currently does
> not capture 'truncate table' and it should be added.
> Also, this maybe an off topic but I think these [DDL |
> https://en.wikipedia.org/wiki/Data_definition_language] statements can be
> dangerous and some use-cases may require human intervention before executing
> such, instead of fully automating with PutDatabaseRecord. It will be useful
> if CaptureChangeMySQL has a 'Capture DDL statements' property.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
