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

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

Github user jvwing commented on the issue:

    https://github.com/apache/nifi/pull/2030
  
    Overall, this looks good - tests pass, integration tests pass, refactoring 
of integration test credentials is nice, code looks good.  In my basic testing, 
it deleted objects from RethinkDB just fine.  I have a few questions about the 
**Return old Changes from the delete** option, and how it is processed.  I am 
not very familiar with RethinkDB, so I had to check the [delete 
docs](https://rethinkdb.com/api/java/delete/) on how it works.  I have no 
practical experience using this option.
    
    * Instead of a true/false dropdown list, you made this a free text field 
supporting expression language.  May I ask why?  I think it would be easier to 
edit if we did, and easier to understand if we made the options more 
explanatory ("Capture changes as FlowFile content", "Do not capture changes", 
or something like that).
    * If the option is true, the processor writes the changes to the attribute 
`rethinkdb.delete.changes`, the changes are also contained in the entire raw 
`attribute rethinkdb.delete.result` attribute, and finally the changes are 
written to the flowfile content.  Do we need all of those?
    * In the event that the deleted document is large, the attributes will be 
large, and potentially unusable due to truncation at 64KB.
    * The modify provenance event is reported regardless of this setting.  
Shouldn't we only do that if a change is made?



> Create RethinkDB Delete Processor
> ---------------------------------
>
>                 Key: NIFI-4212
>                 URL: https://issues.apache.org/jira/browse/NIFI-4212
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>    Affects Versions: 1.3.0
>            Reporter: Mans Singh
>            Assignee: Mans Singh
>            Priority: Minor
>              Labels: delete, rethinkdb
>             Fix For: 1.4.0
>
>
> Create processor to delete RethinkDB documents by id.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to