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

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

Github user mcgilman commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/424#discussion_r63452681
  
    --- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiServiceFacade.java
 ---
    @@ -1670,6 +1670,49 @@ public ProcessorDTO getConfiguration() {
         }
     
         @Override
    +    public ConfigurationSnapshot<ProcessorDTO> 
setProcessorProperties(final Revision revision, final String processorId, final 
Map<String,String> properties) {
    --- End diff --
    
    I think it may make sense to just use updateProcessor(...) instead 
introducing setProcessorProperties(...). We should probably even get rid of 
setProcessorAnnotationData(...) in favor of updateProcessor(...). In earlier 
version of NiFi, these values were setting differently which is why there was 
two different method. However, now I think we can consolidate these.


> JSON-to-JSON Schema Converter Editor
> ------------------------------------
>
>                 Key: NIFI-1850
>                 URL: https://issues.apache.org/jira/browse/NIFI-1850
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core UI
>            Reporter: Yolanda M. Davis
>            Priority: Minor
>             Fix For: 1.0.0, 0.7.0
>
>
> With NIFI-361 implemented, users can embed a JOLT spec into the TransformJSON 
> processor. However, building the spec is not intuitive enough without the 
> ability to obtain real time feedback on spec syntax and preview output data. 
> Would like to have a specification editor and transform  preview view added 
> to the processor configuration screen to  allow users to immediately see the 
> impact on the output JSON data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to