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

ASF GitHub Bot commented on NIFI-3728:
--------------------------------------

GitHub user mattyb149 opened a pull request:

    https://github.com/apache/nifi/pull/1690

    NIFI-3728: Detect 'truncate table' event, allow exclusion of schema change 
events in CaptureChangeMySQL

    Wouldn't be surprised if #1689 or this PR needs to be rebased, depending on 
which is merged first.
    
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
    - [x] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
    - [x] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in 
which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mattyb149/nifi NIFI-3728

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1690.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1690
    
----
commit ad1cc16a16f9b3229167330d81c8d9155eab51ee
Author: Matt Burgess <[email protected]>
Date:   2017-04-24T13:48:39Z

    NIFI-3728: Detect 'truncate table' event, allow exclusion of schema change 
events in 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
>            Assignee: Matt Burgess
>             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)

Reply via email to