[jira] [Updated] (NIFI-4785) localization needed

[Ning Sheng (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ning Sheng updated NIFI-4785:
-
Affects Version/s: (was: 1.5.0)
   1.6.0

> localization needed
> ---
>
> Key: NIFI-4785
> URL: https://issues.apache.org/jira/browse/NIFI-4785
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.6.0
>Reporter: Ning Sheng
>Priority: Major
> Fix For: 1.6.0
>
>
> JSP :
> 1.Use the JSTL standard fmt tag for multilingualization
> 1.The resource file is placed under the org.apache.nifi.web.resources package
> 2.Resource file name rules Messages_en.properties English resource file, 
> Messages_cn.properties for Chinese resource file
> Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
> 3.Will be around the jsp Chinese characters in accordance with  key = "canvas.about-dailog.nf-version" /> replace
> 2.In nifi-web-ui in the web.xml configuration in the following content 
> specified properties file location, has been used language
> 
>  javax.servlet.jsp.jstl.fmt.localizationContext 
>  org.apache.nifi.web.resources.Messages 
> 
> 
>  javax.servlet.jsp.jstl.fmt.locale 
>  en 
> 
> 3.Add the * .properties file to the nifi-web-ui pom.xml war plugin
> 
>  org.apache.maven.plugins 
>  maven-war-plugin 
> 
>  $
> {staging.dir}
> /WEB-INF/web.xml 
> 
>  
>  src / main / java / org / apache / nifi / web / resources /  directory>
>  WEB-INF / classes / org / apache / nifi / web / resources /  targetPath>
> 
>  *. Properties 
> 
>  true 
> 
> 4.JSP page of the internationalization of the two general situation
> 1. Directly replace the tag in the text content, for example: replace english 
> content
>  Relationships  Replace with the result
>div>
> 2.Replace the div in the attribute content, for example: replace the test 
> content
>  "Info" title = "Relationships" />
>  "partials.connection-details.configuration-tab.read-only-relationship-names-container.title"
>  var = "Relationships"
>  "Info" title = "$
> {Relationships}
> " /> 
> 3.In the jsp page to increase the fmt reference
> <% @ Taglib uri = "http://java.sun.com/jsp/jstl/fmt; prefix = "fmt"%>
> 4.Properties file rules
> There are two rules
> Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
> If the text information is not unique xpath or id, you can use the original 
> information to name enable-controller-service-dialog.Canceling = Canceling ...
> JS :
> 1.Make nf / globalization / resources.js add translation files
> 2.Global.js initialization, according to the current run of the file name and 
> messsage to determine the resources to find json
> 3.Add the resources.js javascript into the war package in pif.xml for 
> nifi-web-ui
> 
>  org.apache.maven.plugins 
>  maven-war-plugin 
>  2.5 
> 
> 
> Js / nf / globalization / resources.js
> 4.Add a reference to resources.js in jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / bulletin-board.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / canvas.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / cluster.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / counters.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / history.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / login.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / provenance.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / summary.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / templates.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / users.jsp
> 5.Replace the text of js ,like this 
> $('#message-title').text(nf._.msg('nf-canvas.Browser'));



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (NIFI-4785) localization needed

[Ning Sheng (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ning Sheng resolved NIFI-4785.
--
   Resolution: Fixed
Fix Version/s: 1.6.0

[PR|https://github.com/apache/nifi/pull/2408] 

> localization needed
> ---
>
> Key: NIFI-4785
> URL: https://issues.apache.org/jira/browse/NIFI-4785
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.5.0
>Reporter: Ning Sheng
>Priority: Major
> Fix For: 1.6.0
>
>
> JSP :
> 1.Use the JSTL standard fmt tag for multilingualization
> 1.The resource file is placed under the org.apache.nifi.web.resources package
> 2.Resource file name rules Messages_en.properties English resource file, 
> Messages_cn.properties for Chinese resource file
> Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
> 3.Will be around the jsp Chinese characters in accordance with  key = "canvas.about-dailog.nf-version" /> replace
> 2.In nifi-web-ui in the web.xml configuration in the following content 
> specified properties file location, has been used language
> 
>  javax.servlet.jsp.jstl.fmt.localizationContext 
>  org.apache.nifi.web.resources.Messages 
> 
> 
>  javax.servlet.jsp.jstl.fmt.locale 
>  en 
> 
> 3.Add the * .properties file to the nifi-web-ui pom.xml war plugin
> 
>  org.apache.maven.plugins 
>  maven-war-plugin 
> 
>  $
> {staging.dir}
> /WEB-INF/web.xml 
> 
>  
>  src / main / java / org / apache / nifi / web / resources /  directory>
>  WEB-INF / classes / org / apache / nifi / web / resources /  targetPath>
> 
>  *. Properties 
> 
>  true 
> 
> 4.JSP page of the internationalization of the two general situation
> 1. Directly replace the tag in the text content, for example: replace english 
> content
>  Relationships  Replace with the result
>div>
> 2.Replace the div in the attribute content, for example: replace the test 
> content
>  "Info" title = "Relationships" />
>  "partials.connection-details.configuration-tab.read-only-relationship-names-container.title"
>  var = "Relationships"
>  "Info" title = "$
> {Relationships}
> " /> 
> 3.In the jsp page to increase the fmt reference
> <% @ Taglib uri = "http://java.sun.com/jsp/jstl/fmt; prefix = "fmt"%>
> 4.Properties file rules
> There are two rules
> Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
> If the text information is not unique xpath or id, you can use the original 
> information to name enable-controller-service-dialog.Canceling = Canceling ...
> JS :
> 1.Make nf / globalization / resources.js add translation files
> 2.Global.js initialization, according to the current run of the file name and 
> messsage to determine the resources to find json
> 3.Add the resources.js javascript into the war package in pif.xml for 
> nifi-web-ui
> 
>  org.apache.maven.plugins 
>  maven-war-plugin 
>  2.5 
> 
> 
> Js / nf / globalization / resources.js
> 4.Add a reference to resources.js in jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / bulletin-board.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / canvas.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / cluster.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / counters.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / history.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / login.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / provenance.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / summary.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / templates.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / users.jsp
> 5.Replace the text of js ,like this 
> $('#message-title').text(nf._.msg('nf-canvas.Browser'));



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4785) localization needed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4785:
--

GitHub user ns7381 opened a pull request:

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

localization using the JSTL standard fmt tag for multilingualization and 
nf._.msg() function in resource.js

jira issue: https://issues.apache.org/jira/browse/NIFI-4785

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

$ git pull https://github.com/ns7381/nifi NIFI-4785

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

https://github.com/apache/nifi/pull/2408.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 #2408


commit 1bdce66e0e468846953d21b37e8bfa16c48d3d73
Author: ningsheng 
Date:   2018-01-17T06:25:12Z

localization using the JSTL standard fmt tag for multilingualization and 
nf._.msg() function in resource.js




> localization needed
> ---
>
> Key: NIFI-4785
> URL: https://issues.apache.org/jira/browse/NIFI-4785
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core UI
>Affects Versions: 1.5.0
>Reporter: Ning Sheng
>Priority: Major
>
> JSP :
> 1.Use the JSTL standard fmt tag for multilingualization
> 1.The resource file is placed under the org.apache.nifi.web.resources package
> 2.Resource file name rules Messages_en.properties English resource file, 
> Messages_cn.properties for Chinese resource file
> Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
> 3.Will be around the jsp Chinese characters in accordance with  key = "canvas.about-dailog.nf-version" /> replace
> 2.In nifi-web-ui in the web.xml configuration in the following content 
> specified properties file location, has been used language
> 
>  javax.servlet.jsp.jstl.fmt.localizationContext 
>  org.apache.nifi.web.resources.Messages 
> 
> 
>  javax.servlet.jsp.jstl.fmt.locale 
>  en 
> 
> 3.Add the * .properties file to the nifi-web-ui pom.xml war plugin
> 
>  org.apache.maven.plugins 
>  maven-war-plugin 
> 
>  $
> {staging.dir}
> /WEB-INF/web.xml 
> 
>  
>  src / main / java / org / apache / nifi / web / resources /  directory>
>  WEB-INF / classes / org / apache / nifi / web / resources /  targetPath>
> 
>  *. Properties 
> 
>  true 
> 
> 4.JSP page of the internationalization of the two general situation
> 1. Directly replace the tag in the text content, for example: replace english 
> content
>  Relationships  Replace with the result
>div>
> 2.Replace the div in the attribute content, for example: replace the test 
> content
>  "Info" title = "Relationships" />
>  "partials.connection-details.configuration-tab.read-only-relationship-names-container.title"
>  var = "Relationships"
>  "Info" title = "$
> {Relationships}
> " /> 
> 3.In the jsp page to increase the fmt reference
> <% @ Taglib uri = "http://java.sun.com/jsp/jstl/fmt; prefix = "fmt"%>
> 4.Properties file rules
> There are two rules
> Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
> If the text information is not unique xpath or id, you can use the original 
> information to name enable-controller-service-dialog.Canceling = Canceling ...
> JS :
> 1.Make nf / globalization / resources.js add translation files
> 2.Global.js initialization, according to the current run of the file name and 
> messsage to determine the resources to find json
> 3.Add the resources.js javascript into the war package in pif.xml for 
> nifi-web-ui
> 
>  org.apache.maven.plugins 
>  maven-war-plugin 
>  2.5 
> 
> 
> Js / nf / globalization / resources.js
> 4.Add a reference to resources.js in jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / bulletin-board.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / canvas.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / cluster.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / counters.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / history.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / login.jsp
> Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web 
> / nifi-web-ui / src / main / webapp / WEB-INF / pages / provenance.jsp
> Modify: 

[GitHub] nifi pull request #2408: localization using the JSTL standard fmt tag for mu...

[ns7381]

GitHub user ns7381 opened a pull request:

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

localization using the JSTL standard fmt tag for multilingualization and 
nf._.msg() function in resource.js

jira issue: https://issues.apache.org/jira/browse/NIFI-4785

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

$ git pull https://github.com/ns7381/nifi NIFI-4785

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

https://github.com/apache/nifi/pull/2408.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 #2408


commit 1bdce66e0e468846953d21b37e8bfa16c48d3d73
Author: ningsheng 
Date:   2018-01-17T06:25:12Z

localization using the JSTL standard fmt tag for multilingualization and 
nf._.msg() function in resource.js




---

[jira] [Commented] (NIFI-4761) Allow whitelisting expected Host values

[Daniel Chaffelson (JIRA)]

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

Daniel Chaffelson commented on NIFI-4761:
-

If running multiple NiFi instances in local Docker containers, it is typical to 
map the default port (8080) to something else (e.g. 1), this change breaks 
that working out of the box.
Tested and working fine in NiFi 1.2-1.4, 'broken' in 1.5

> Allow whitelisting expected Host values
> ---
>
> Key: NIFI-4761
> URL: https://issues.apache.org/jira/browse/NIFI-4761
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Andy LoPresto
>Priority: Major
>
> NiFi has been updated to only accept requests where the Host header contains 
> an expected value. Currently, the expected values are driven by the .host 
> properties in nifi.properties. When running behind a proxy, the value may be 
> the proxy host if the headers simply pass through. In this scenario, we 
> should offer the ability to whitelist values in case updating the proxy 
> configuration isn't possible.
> Also, the proxy documentation in the admin guide should be updated to include 
> details regarding the Host name whitelisting. Also, should verify the context 
> path whitelisting is documented there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (NIFI-4785) localization needed

[Ning Sheng (JIRA)]

Ning Sheng created NIFI-4785:


 Summary: localization needed
 Key: NIFI-4785
 URL: https://issues.apache.org/jira/browse/NIFI-4785
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Core UI
Affects Versions: 1.5.0
Reporter: Ning Sheng


JSP :
1.Use the JSTL standard fmt tag for multilingualization
1.The resource file is placed under the org.apache.nifi.web.resources package
2.Resource file name rules Messages_en.properties English resource file, 
Messages_cn.properties for Chinese resource file
Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
3.Will be around the jsp Chinese characters in accordance with  replace
2.In nifi-web-ui in the web.xml configuration in the following content 
specified properties file location, has been used language

 javax.servlet.jsp.jstl.fmt.localizationContext 
 org.apache.nifi.web.resources.Messages 


 javax.servlet.jsp.jstl.fmt.locale 
 en 

3.Add the * .properties file to the nifi-web-ui pom.xml war plugin

 org.apache.maven.plugins 
 maven-war-plugin 

 $

{staging.dir}

/WEB-INF/web.xml 

 
 src / main / java / org / apache / nifi / web / resources / 
 WEB-INF / classes / org / apache / nifi / web / resources / 

 *. Properties 

 true 

4.JSP page of the internationalization of the two general situation
1. Directly replace the tag in the text content, for example: replace english 
content
 Relationships  Replace with the result
  
2.Replace the div in the attribute content, for example: replace the test 
content

 
3.In the jsp page to increase the fmt reference
<% @ Taglib uri = "http://java.sun.com/jsp/jstl/fmt; prefix = "fmt"%>
4.Properties file rules
There are two rules
Bulletin-board-content-bullet-bullet-bullet-shell-content-bullet
If the text information is not unique xpath or id, you can use the original 
information to name enable-controller-service-dialog.Canceling = Canceling ...

JS :
1.Make nf / globalization / resources.js add translation files
2.Global.js initialization, according to the current run of the file name and 
messsage to determine the resources to find json
3.Add the resources.js javascript into the war package in pif.xml for 
nifi-web-ui

 org.apache.maven.plugins 
 maven-war-plugin 
 2.5 


Js / nf / globalization / resources.js
4.Add a reference to resources.js in jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / bulletin-board.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / canvas.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / cluster.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / counters.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / history.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / login.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / provenance.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / summary.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / templates.jsp
Modify: nifi-nar-bundles / nifi-framework-bundle / nifi-framework / nifi-web / 
nifi-web-ui / src / main / webapp / WEB-INF / pages / users.jsp
5.Replace the text of js ,like this 
$('#message-title').text(nf._.msg('nf-canvas.Browser'));



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4761) Allow whitelisting expected Host values

[Jeremy Dyer (JIRA)]

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

Jeremy Dyer commented on NIFI-4761:
---

So knowing this does that mean that the .host property MUST be set in 
nifi.properties? I just tried running a fresh NiFi 1.5.0 instance in AWS and I 
could not access the UI without manually specifying the public dns name in the 
.host property. Maybe that is a required configuration now but I was unaware of 
that and just wanted to know what the official stance is on that now?

> Allow whitelisting expected Host values
> ---
>
> Key: NIFI-4761
> URL: https://issues.apache.org/jira/browse/NIFI-4761
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Andy LoPresto
>Priority: Major
>
> NiFi has been updated to only accept requests where the Host header contains 
> an expected value. Currently, the expected values are driven by the .host 
> properties in nifi.properties. When running behind a proxy, the value may be 
> the proxy host if the headers simply pass through. In this scenario, we 
> should offer the ability to whitelist values in case updating the proxy 
> configuration isn't possible.
> Also, the proxy documentation in the admin guide should be updated to include 
> details regarding the Host name whitelisting. Also, should verify the context 
> path whitelisting is documented there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (NIFI-4699) PostHTTP: modify to use FlowFileFilter

[Michael Moser (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Moser reassigned NIFI-4699:
---

Assignee: Michael Moser

> PostHTTP: modify to use FlowFileFilter
> --
>
> Key: NIFI-4699
> URL: https://issues.apache.org/jira/browse/NIFI-4699
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.4.0
>Reporter: Brandon DeVries
>Assignee: Michael Moser
>Priority: Minor
> Attachments: PostHTTP-onTrigger-mod.java
>
>
> PostHTTP does batching of FlowFiles, but only if the "batch" is contiguous on 
> the queue.  Modify to use a FlowFileFilter instead.  See attached for 
> proposed changes to the onTrigger() method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4756) PublishKafkaRecord should consider schema-related attributes when publishing records

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4756:
--

Github user asfgit closed the pull request at:

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


> PublishKafkaRecord should consider schema-related attributes when publishing 
> records
> 
>
> Key: NIFI-4756
> URL: https://issues.apache.org/jira/browse/NIFI-4756
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> Currently, if PublishKafkaRecord (0_10, 0_11, 1_0) is configured to write 
> flowfile attributes as headers, the attributes generated by the Schema Writer 
> are not taken into account. For example, if the Avro Record Writer is used 
> and configured with a Write Strategy of "Write 'schema.name' attribute" and 
> the Attributes to Send as Headers is set to "schema.*" then the schema.name 
> attribute is not sent. This is because the schema.name attribute does not 
> exist on the FlowFile yet but is generated by the Schema Writer



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4784) ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4784:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2407
  
Will review...


> ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes
> --
>
> Key: NIFI-4784
> URL: https://issues.apache.org/jira/browse/NIFI-4784
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
> Environment: All
>Reporter: Sébastien Bouchex Bellomié
>Priority: Minor
>
> Following NIFI-4615  , it appears that the allowableValues annotation for the 
> ProcessorStatusDTO and ProcessorStatusSnapshotDTO classes  are incorrect as 
> the runStatus coming from org.apache.nifi.controller.status.RunStatus enum 
> with the values "Running", "Stopped", "Invalid", "Disabled" are not uppercase.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4756) PublishKafkaRecord should consider schema-related attributes when publishing records

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4756:
---

Commit 7c1ce172232d5fd8ab2a1c1649a9dcbf1a9d08d7 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7c1ce17 ]

NIFI-4756: Updated PublishKafkaRecord processors to include attributes 
generated from schema write strategy into the message headers when appropriate

This closes #2396.

Signed-off-by: Bryan Bende 


> PublishKafkaRecord should consider schema-related attributes when publishing 
> records
> 
>
> Key: NIFI-4756
> URL: https://issues.apache.org/jira/browse/NIFI-4756
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> Currently, if PublishKafkaRecord (0_10, 0_11, 1_0) is configured to write 
> flowfile attributes as headers, the attributes generated by the Schema Writer 
> are not taken into account. For example, if the Avro Record Writer is used 
> and configured with a Write Strategy of "Write 'schema.name' attribute" and 
> the Attributes to Send as Headers is set to "schema.*" then the schema.name 
> attribute is not sent. This is because the schema.name attribute does not 
> exist on the FlowFile yet but is generated by the Schema Writer



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2396: NIFI-4756: Updated PublishKafkaRecord processors to...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] nifi issue #2407: NIFI-4784 ProcessorStatusSnapshotDTO and ProcessorStatusDT...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2407
  
Will review...


---

[jira] [Updated] (NIFI-4756) PublishKafkaRecord should consider schema-related attributes when publishing records

[Bryan Bende (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Bende updated NIFI-4756:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> PublishKafkaRecord should consider schema-related attributes when publishing 
> records
> 
>
> Key: NIFI-4756
> URL: https://issues.apache.org/jira/browse/NIFI-4756
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> Currently, if PublishKafkaRecord (0_10, 0_11, 1_0) is configured to write 
> flowfile attributes as headers, the attributes generated by the Schema Writer 
> are not taken into account. For example, if the Avro Record Writer is used 
> and configured with a Write Strategy of "Write 'schema.name' attribute" and 
> the Attributes to Send as Headers is set to "schema.*" then the schema.name 
> attribute is not sent. This is because the schema.name attribute does not 
> exist on the FlowFile yet but is generated by the Schema Writer



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4784) ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4784:
--

GitHub user sbouchex opened a pull request:

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

NIFI-4784 ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### 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- where  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?
- [ x] 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)? 
- [x ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ x] 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/infovista/nifi NIFI-4784

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

https://github.com/apache/nifi/pull/2407.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 #2407


commit 7286994dccf4091b09eeb8de1bc43e373991e8ae
Author: sbouchex 
Date:   2018-01-16T21:23:51Z

Fixed runStatus allowedValues




> ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes
> --
>
> Key: NIFI-4784
> URL: https://issues.apache.org/jira/browse/NIFI-4784
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
> Environment: All
>Reporter: Sébastien Bouchex Bellomié
>Priority: Minor
>
> Following NIFI-4615  , it appears that the allowableValues annotation for the 
> ProcessorStatusDTO and ProcessorStatusSnapshotDTO classes  are incorrect as 
> the runStatus coming from org.apache.nifi.controller.status.RunStatus enum 
> with the values "Running", "Stopped", "Invalid", "Disabled" are not uppercase.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2407: NIFI-4784 ProcessorStatusSnapshotDTO and ProcessorS...

[sbouchex]

GitHub user sbouchex opened a pull request:

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

NIFI-4784 ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### 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- where  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?
- [ x] 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)? 
- [x ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ x] 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/infovista/nifi NIFI-4784

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

https://github.com/apache/nifi/pull/2407.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 #2407


commit 7286994dccf4091b09eeb8de1bc43e373991e8ae
Author: sbouchex 
Date:   2018-01-16T21:23:51Z

Fixed runStatus allowedValues




---

[jira] [Commented] (NIFI-4756) PublishKafkaRecord should consider schema-related attributes when publishing records

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4756:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2396
  
+1 looks good, verified 0.11 and 1.0 processors send attributes in headers 
correctly, there was a minor check-style error that i am fixing while merging


> PublishKafkaRecord should consider schema-related attributes when publishing 
> records
> 
>
> Key: NIFI-4756
> URL: https://issues.apache.org/jira/browse/NIFI-4756
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> Currently, if PublishKafkaRecord (0_10, 0_11, 1_0) is configured to write 
> flowfile attributes as headers, the attributes generated by the Schema Writer 
> are not taken into account. For example, if the Avro Record Writer is used 
> and configured with a Write Strategy of "Write 'schema.name' attribute" and 
> the Attributes to Send as Headers is set to "schema.*" then the schema.name 
> attribute is not sent. This is because the schema.name attribute does not 
> exist on the FlowFile yet but is generated by the Schema Writer



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2396: NIFI-4756: Updated PublishKafkaRecord processors to includ...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2396
  
+1 looks good, verified 0.11 and 1.0 processors send attributes in headers 
correctly, there was a minor check-style error that i am fixing while merging


---

[jira] [Updated] (NIFI-4784) ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes

[JIRA]

 [ 
https://issues.apache.org/jira/browse/NIFI-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sébastien Bouchex Bellomié updated NIFI-4784:
-
Description: 
Following NIFI-4615  , it appears that the allowableValues annotation for the 
ProcessorStatusDTO and ProcessorStatusSnapshotDTO classes  are incorrect as the 
runStatus coming from org.apache.nifi.controller.status.RunStatus enum with the 
values "Running", "Stopped", "Invalid", "Disabled" are not uppercase.

 

  was:
Following NIFI-4615  , it appears that the allowableValues annotation is 
incorrect as the runStatus coming from 
org.apache.nifi.controller.status.RunStatus enum with the values "Running", 
"Stopped", "Invalid", "Disabled" are not uppercase.

 


> ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes
> --
>
> Key: NIFI-4784
> URL: https://issues.apache.org/jira/browse/NIFI-4784
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
> Environment: All
>Reporter: Sébastien Bouchex Bellomié
>Priority: Minor
>
> Following NIFI-4615  , it appears that the allowableValues annotation for the 
> ProcessorStatusDTO and ProcessorStatusSnapshotDTO classes  are incorrect as 
> the runStatus coming from org.apache.nifi.controller.status.RunStatus enum 
> with the values "Running", "Stopped", "Invalid", "Disabled" are not uppercase.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-4784) ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes

[JIRA]

 [ 
https://issues.apache.org/jira/browse/NIFI-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sébastien Bouchex Bellomié updated NIFI-4784:
-
Summary: ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes 
 (was: ProcessorStatusSnapshotDTO.getRunStatus annotation is incorrect)

> ProcessorStatusSnapshotDTO and ProcessorStatusDTO annotation fixes
> --
>
> Key: NIFI-4784
> URL: https://issues.apache.org/jira/browse/NIFI-4784
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
> Environment: All
>Reporter: Sébastien Bouchex Bellomié
>Priority: Minor
>
> Following NIFI-4615  , it appears that the allowableValues annotation is 
> incorrect as the runStatus coming from 
> org.apache.nifi.controller.status.RunStatus enum with the values "Running", 
> "Stopped", "Invalid", "Disabled" are not uppercase.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (NIFIREG-116) Checkboxes in the New Bucket Policy dialog do not show as checked when clicking directly on the checkboxes.

[Kevin Doran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFIREG-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran resolved NIFIREG-116.
-
Resolution: Fixed

> Checkboxes in the New Bucket Policy dialog do not show as checked when 
> clicking directly on the checkboxes.
> ---
>
> Key: NIFIREG-116
> URL: https://issues.apache.org/jira/browse/NIFIREG-116
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
> Fix For: 0.1.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFIREG-116) Checkboxes in the New Bucket Policy dialog do not show as checked when clicking directly on the checkboxes.

[Kevin Doran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFIREG-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran updated NIFIREG-116:

Fix Version/s: 0.1.1

> Checkboxes in the New Bucket Policy dialog do not show as checked when 
> clicking directly on the checkboxes.
> ---
>
> Key: NIFIREG-116
> URL: https://issues.apache.org/jira/browse/NIFIREG-116
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
> Fix For: 0.1.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFIREG-116) Checkboxes in the New Bucket Policy dialog do not show as checked when clicking directly on the checkboxes.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327810#comment-16327810
 ] 

ASF GitHub Bot commented on NIFIREG-116:


Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/84


> Checkboxes in the New Bucket Policy dialog do not show as checked when 
> clicking directly on the checkboxes.
> ---
>
> Key: NIFIREG-116
> URL: https://issues.apache.org/jira/browse/NIFIREG-116
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-registry pull request #84: [NIFIREG-116] update New Policy dialog check...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/84


---

[jira] [Created] (NIFI-4784) ProcessorStatusSnapshotDTO.getRunStatus annotation is incorrect

[JIRA]

Sébastien Bouchex Bellomié created NIFI-4784:


 Summary: ProcessorStatusSnapshotDTO.getRunStatus annotation is 
incorrect
 Key: NIFI-4784
 URL: https://issues.apache.org/jira/browse/NIFI-4784
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Affects Versions: 1.5.0
 Environment: All
Reporter: Sébastien Bouchex Bellomié


Following NIFI-4615  , it appears that the allowableValues annotation is 
incorrect as the runStatus coming from 
org.apache.nifi.controller.status.RunStatus enum with the values "Running", 
"Stopped", "Invalid", "Disabled" are not uppercase.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFIREG-115) Dialogs should automatically focus their initial inputs to allow users to quickly start typing.

[Kevin Doran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFIREG-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran updated NIFIREG-115:

Fix Version/s: 0.1.1

> Dialogs should automatically focus their initial inputs to allow users to 
> quickly start typing.
> ---
>
> Key: NIFIREG-115
> URL: https://issues.apache.org/jira/browse/NIFIREG-115
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
> Fix For: 0.1.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (NIFIREG-115) Dialogs should automatically focus their initial inputs to allow users to quickly start typing.

[Kevin Doran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFIREG-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran resolved NIFIREG-115.
-
Resolution: Fixed

> Dialogs should automatically focus their initial inputs to allow users to 
> quickly start typing.
> ---
>
> Key: NIFIREG-115
> URL: https://issues.apache.org/jira/browse/NIFIREG-115
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (NIFIREG-115) Dialogs should automatically focus their initial inputs to allow users to quickly start typing.

[Kevin Doran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFIREG-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran reopened NIFIREG-115:
-

> Dialogs should automatically focus their initial inputs to allow users to 
> quickly start typing.
> ---
>
> Key: NIFIREG-115
> URL: https://issues.apache.org/jira/browse/NIFIREG-115
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2396: NIFI-4756: Updated PublishKafkaRecord processors to includ...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2396
  
Reviewing...


---

[jira] [Commented] (NIFI-4756) PublishKafkaRecord should consider schema-related attributes when publishing records

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4756:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2396
  
Reviewing...


> PublishKafkaRecord should consider schema-related attributes when publishing 
> records
> 
>
> Key: NIFI-4756
> URL: https://issues.apache.org/jira/browse/NIFI-4756
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> Currently, if PublishKafkaRecord (0_10, 0_11, 1_0) is configured to write 
> flowfile attributes as headers, the attributes generated by the Schema Writer 
> are not taken into account. For example, if the Avro Record Writer is used 
> and configured with a Write Strategy of "Write 'schema.name' attribute" and 
> the Attributes to Send as Headers is set to "schema.*" then the schema.name 
> attribute is not sent. This is because the schema.name attribute does not 
> exist on the FlowFile yet but is generated by the Schema Writer



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (NIFIREG-115) Dialogs should automatically focus their initial inputs to allow users to quickly start typing.

[Kevin Doran (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFIREG-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran closed NIFIREG-115.
---
Resolution: Fixed

> Dialogs should automatically focus their initial inputs to allow users to 
> quickly start typing.
> ---
>
> Key: NIFIREG-115
> URL: https://issues.apache.org/jira/browse/NIFIREG-115
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFIREG-115) Dialogs should automatically focus their initial inputs to allow users to quickly start typing.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327734#comment-16327734
 ] 

ASF GitHub Bot commented on NIFIREG-115:


Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/83


> Dialogs should automatically focus their initial inputs to allow users to 
> quickly start typing.
> ---
>
> Key: NIFIREG-115
> URL: https://issues.apache.org/jira/browse/NIFIREG-115
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-registry pull request #83: [NIFIREG-115] add focus to inputs in the new...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-registry/pull/83


---

[jira] [Created] (NIFI-4783) Create Google Vision processor

[Jeremy Dyer (JIRA)]

Jeremy Dyer created NIFI-4783:
-

 Summary: Create Google Vision processor
 Key: NIFI-4783
 URL: https://issues.apache.org/jira/browse/NIFI-4783
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Reporter: Jeremy Dyer
Assignee: Jeremy Dyer
 Fix For: 1.6.0


Google provides a suite of API services that provide ML capabilities. Vision is 
one of them. This services allows for an application to send images to the 
Google Cloud ML service and the service will return a response with information 
like what type of object the image is, face detection, does the image content 
mature content, if applicable the geo coordinates of where the image was taken, 
etc. While the service operates over REST the building of the workflow within 
NiFi is quite cumbersome today with lots flags and formatting that must take 
place as well as the parsing. This processor would allow the user to use the 
full capabilities of the REST api and configure the flags in a single place. 
This would also take advantage of the existing work that has already been done 
with the GCP authentication service.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-registry issue #86: NIFIREG-112 - Add a 'diff' endpoint to the API/Clie...

[dannylane]

Github user dannylane commented on the issue:

https://github.com/apache/nifi-registry/pull/86
  
I should add the client change before I submit the PR



---

[jira] [Commented] (NIFIREG-112) Add a 'diff' endpoint to the API/Client for comparing 2 versions of a flow

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327711#comment-16327711
 ] 

ASF GitHub Bot commented on NIFIREG-112:


Github user dannylane commented on the issue:

https://github.com/apache/nifi-registry/pull/86
  
I should add the client change before I submit the PR



> Add a 'diff' endpoint to the API/Client for comparing 2 versions of a flow 
> ---
>
> Key: NIFIREG-112
> URL: https://issues.apache.org/jira/browse/NIFIREG-112
> Project: NiFi Registry
>  Issue Type: Sub-task
>Affects Versions: 0.1.0
>Reporter: Danny Lane
>Assignee: Danny Lane
>Priority: Major
>
> To facilitate the behavior described in the parent ticket we need to add an 
> endpoint to the registry API and client for retrieving a list of differences 
> between two supplied versions of a flow.
> A suggested uri is 
> {{/buckets/\{bucketId\}/flows/\{flowId\}/diff/\{versionA\}/\{versionB\}}}
> The response format should be something similar to the format used by NiFi 
> for its {{local-modifications}} endpoint.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFIREG-112) Add a 'diff' endpoint to the API/Client for comparing 2 versions of a flow

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327709#comment-16327709
 ] 

ASF GitHub Bot commented on NIFIREG-112:


Github user dannylane closed the pull request at:

https://github.com/apache/nifi-registry/pull/86


> Add a 'diff' endpoint to the API/Client for comparing 2 versions of a flow 
> ---
>
> Key: NIFIREG-112
> URL: https://issues.apache.org/jira/browse/NIFIREG-112
> Project: NiFi Registry
>  Issue Type: Sub-task
>Affects Versions: 0.1.0
>Reporter: Danny Lane
>Assignee: Danny Lane
>Priority: Major
>
> To facilitate the behavior described in the parent ticket we need to add an 
> endpoint to the registry API and client for retrieving a list of differences 
> between two supplied versions of a flow.
> A suggested uri is 
> {{/buckets/\{bucketId\}/flows/\{flowId\}/diff/\{versionA\}/\{versionB\}}}
> The response format should be something similar to the format used by NiFi 
> for its {{local-modifications}} endpoint.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-registry pull request #86: NIFIREG-112 - Add a 'diff' endpoint to the A...

[dannylane]

Github user dannylane closed the pull request at:

https://github.com/apache/nifi-registry/pull/86


---

[jira] [Commented] (NIFIREG-112) Add a 'diff' endpoint to the API/Client for comparing 2 versions of a flow

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327705#comment-16327705
 ] 

ASF GitHub Bot commented on NIFIREG-112:


GitHub user dannylane opened a pull request:

https://github.com/apache/nifi-registry/pull/86

NIFIREG-112 - Add a 'diff' endpoint to the API/Client for comparing 2 
versions of a flow.

This PR is for an API endpoint to get a diff between 2 versions of a flow. 

[NIFIREG-77](https://issues.apache.org/jira/projects/NIFIREG/issues/NIFIREG-77) 
is the parent task and 
[NIFIREG-112](https://issues.apache.org/jira/projects/NIFIREG/issues/NIFIREG-112)
 is the sub task.
There is some discussion on the parent task around direction etc. 
Let me know if there's anything I should change. Thanks.

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

$ git pull https://github.com/dannylane/nifi-registry NIFIREG-77

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

https://github.com/apache/nifi-registry/pull/86.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 #86


commit eeed846167dc90d983ea1d37d4149980b3057be2
Author: Danny Lane 
Date:   2018-01-08T23:51:27Z

NIFIREG-77 - Add a 'diff' endpoint to the API/Client for comparing 2 
versions of a flow.




> Add a 'diff' endpoint to the API/Client for comparing 2 versions of a flow 
> ---
>
> Key: NIFIREG-112
> URL: https://issues.apache.org/jira/browse/NIFIREG-112
> Project: NiFi Registry
>  Issue Type: Sub-task
>Affects Versions: 0.1.0
>Reporter: Danny Lane
>Assignee: Danny Lane
>Priority: Major
>
> To facilitate the behavior described in the parent ticket we need to add an 
> endpoint to the registry API and client for retrieving a list of differences 
> between two supplied versions of a flow.
> A suggested uri is 
> {{/buckets/\{bucketId\}/flows/\{flowId\}/diff/\{versionA\}/\{versionB\}}}
> The response format should be something similar to the format used by NiFi 
> for its {{local-modifications}} endpoint.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-registry pull request #86: NIFIREG-112 - Add a 'diff' endpoint to the A...

[dannylane]

GitHub user dannylane opened a pull request:

https://github.com/apache/nifi-registry/pull/86

NIFIREG-112 - Add a 'diff' endpoint to the API/Client for comparing 2 
versions of a flow.

This PR is for an API endpoint to get a diff between 2 versions of a flow. 

[NIFIREG-77](https://issues.apache.org/jira/projects/NIFIREG/issues/NIFIREG-77) 
is the parent task and 
[NIFIREG-112](https://issues.apache.org/jira/projects/NIFIREG/issues/NIFIREG-112)
 is the sub task.
There is some discussion on the parent task around direction etc. 
Let me know if there's anything I should change. Thanks.

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

$ git pull https://github.com/dannylane/nifi-registry NIFIREG-77

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

https://github.com/apache/nifi-registry/pull/86.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 #86


commit eeed846167dc90d983ea1d37d4149980b3057be2
Author: Danny Lane 
Date:   2018-01-08T23:51:27Z

NIFIREG-77 - Add a 'diff' endpoint to the API/Client for comparing 2 
versions of a flow.




---

[jira] [Assigned] (MINIFICPP-365) Refine log levels and messages

[Aldrin Piri (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri reassigned MINIFICPP-365:
-

Assignee: Aldrin Piri

> Refine log levels and messages
> --
>
> Key: MINIFICPP-365
> URL: https://issues.apache.org/jira/browse/MINIFICPP-365
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Aldrin Piri
>Assignee: Aldrin Piri
>Priority: Major
> Fix For: 0.4.0
>
>
> minifi-app.log is verbose and includes a lot of information at an INFO level 
> that is below the typical information a person might care to see.  Some 
> statements are likely extraneous and remnants of development, some should be 
> dropped to a lower priority and others seem duplicative.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFIREG-115) Dialogs should automatically focus their initial inputs to allow users to quickly start typing.

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/NIFIREG-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327682#comment-16327682
 ] 

ASF GitHub Bot commented on NIFIREG-115:


Github user kevdoran commented on the issue:

https://github.com/apache/nifi-registry/pull/83
  
Reviewing...


> Dialogs should automatically focus their initial inputs to allow users to 
> quickly start typing.
> ---
>
> Key: NIFIREG-115
> URL: https://issues.apache.org/jira/browse/NIFIREG-115
> Project: NiFi Registry
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-registry issue #83: [NIFIREG-115] add focus to inputs in the new user, ...

[kevdoran]

Github user kevdoran commented on the issue:

https://github.com/apache/nifi-registry/pull/83
  
Reviewing...


---

[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327659#comment-16327659
 ] 

ASF GitHub Bot commented on MINIFICPP-114:
--

Github user phrocker commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@calebj HTTP Site to Site and C2 don't seem to work. Do you need help in 
testing these? 


> Consolidate JSON API use to RapidJSON
> -
>
> Key: MINIFICPP-114
> URL: https://issues.apache.org/jira/browse/MINIFICPP-114
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: John Reynolds
>Assignee: John Reynolds
>Priority: Major
> Fix For: 0.4.0
>
>
> MiNiFi was updated with new dependencies to jsoncpp: 
> SiteToSiteProvenanceReportingTask
> Performance observations indicate significant improvements with RapidJSON vs. 
> jsoncpp.  Convert all use of jsoncpp to RapidJSON where applicable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #191: MINIFICPP-114 Consolidate JSON API use to RapidJ...

[phrocker]

Github user phrocker commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
@calebj HTTP Site to Site and C2 don't seem to work. Do you need help in 
testing these? 


---

[jira] [Updated] (MINIFICPP-277) Produce system packages in build process

[Andrew Christianson (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Christianson updated MINIFICPP-277:
--
Fix Version/s: (was: 0.4.0)

> Produce system packages in build process
> 
>
> Key: MINIFICPP-277
> URL: https://issues.apache.org/jira/browse/MINIFICPP-277
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Priority: Major
>
> Users have reported issues with portability of built MiNiFi - C++ binaries. 
> While this issue is caused by multiple factors, one factor is the lack of 
> system packages built to be compatible with standard runtime 
> environments/OSes (e.g. CentOS 6). We should add build targets which produce 
> system packages, and ideally have repeatable builds & release artifacts for 
> major target OSes such that the deployment/installation practice is a simple 
> apt-get or yum install.
> Initial yum OS packages:
> * CentOS 6
> * CentOS 7
> Initial deb OS packages:
> * Ubuntu 14.04
> * Ubuntu 16.04



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-277) Produce system packages in build process

[Andrew Christianson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327627#comment-16327627
 ] 

Andrew Christianson commented on MINIFICPP-277:
---

MINIFICPP-277 should be done but should be bumped to a later version. I think 
that would be something to put closer to a 1.0 release.

> Produce system packages in build process
> 
>
> Key: MINIFICPP-277
> URL: https://issues.apache.org/jira/browse/MINIFICPP-277
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Priority: Major
>
> Users have reported issues with portability of built MiNiFi - C++ binaries. 
> While this issue is caused by multiple factors, one factor is the lack of 
> system packages built to be compatible with standard runtime 
> environments/OSes (e.g. CentOS 6). We should add build targets which produce 
> system packages, and ideally have repeatable builds & release artifacts for 
> major target OSes such that the deployment/installation practice is a simple 
> apt-get or yum install.
> Initial yum OS packages:
> * CentOS 6
> * CentOS 7
> Initial deb OS packages:
> * Ubuntu 14.04
> * Ubuntu 16.04



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4782) When reverting a flow, we do not revert required properties to empty values

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4782:
--

Github user asfgit closed the pull request at:

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


> When reverting a flow, we do not revert required properties to empty values
> ---
>
> Key: NIFI-4782
> URL: https://issues.apache.org/jira/browse/NIFI-4782
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> If I create a Processor and place it under version Control, and then I 
> populate a property that is currently unset in the processor (and required), 
> I am given the chance to revert changes. However, doing so does not remove 
> the property from the processor and instead leaves the processor marked as 
> 'locally modified', with the value still set. We should instead remove the 
> value of the property, even if the property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-4782) When reverting a flow, we do not revert required properties to empty values

[Bryan Bende (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Bende updated NIFI-4782:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> When reverting a flow, we do not revert required properties to empty values
> ---
>
> Key: NIFI-4782
> URL: https://issues.apache.org/jira/browse/NIFI-4782
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> If I create a Processor and place it under version Control, and then I 
> populate a property that is currently unset in the processor (and required), 
> I am given the chance to revert changes. However, doing so does not remove 
> the property from the processor and instead leaves the processor marked as 
> 'locally modified', with the value still set. We should instead remove the 
> value of the property, even if the property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4782) When reverting a flow, we do not revert required properties to empty values

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4782:
---

Commit 28e1bcc9d034261c8045c6b2c76ff21839f7eb95 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=28e1bcc ]

NIFI-4782: Allow the value of a Required Property to be moved when changing 
version of a flow or reverting a flow

This closes #2406.

Signed-off-by: Bryan Bende 


> When reverting a flow, we do not revert required properties to empty values
> ---
>
> Key: NIFI-4782
> URL: https://issues.apache.org/jira/browse/NIFI-4782
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> If I create a Processor and place it under version Control, and then I 
> populate a property that is currently unset in the processor (and required), 
> I am given the chance to revert changes. However, doing so does not remove 
> the property from the processor and instead leaves the processor marked as 
> 'locally modified', with the value still set. We should instead remove the 
> value of the property, even if the property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2406: NIFI-4782: Allow the value of a Required Property t...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Resolved] (MINIFICPP-313) GenerateFlowFile 'Unique FlowFiles' property inverted

[marco polo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

marco polo resolved MINIFICPP-313.
--
Resolution: Fixed

> GenerateFlowFile 'Unique FlowFiles' property inverted
> -
>
> Key: MINIFICPP-313
> URL: https://issues.apache.org/jira/browse/MINIFICPP-313
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Dustin Rodrigues
>Priority: Minor
> Fix For: 0.4.0
>
>
> 'Unique FlowFiles' must be set to false in order to get unique flow files, 
> which is backward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MINIFICPP-373) Core minifi needs to be in whole-archive for linux in Cmake

[marco polo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

marco polo updated MINIFICPP-373:
-
Fix Version/s: (was: 0.4.0)

> Core minifi needs to be in whole-archive for linux in Cmake
> ---
>
> Key: MINIFICPP-373
> URL: https://issues.apache.org/jira/browse/MINIFICPP-373
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
>Priority: Critical
>
> Core minifi needs to be in whole-archive for linux in Cmake



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-373) Core minifi needs to be in whole-archive for linux in Cmake

[marco polo (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327610#comment-16327610
 ] 

marco polo commented on MINIFICPP-373:
--

Will be solved with MiNiFiCPP-374

> Core minifi needs to be in whole-archive for linux in Cmake
> ---
>
> Key: MINIFICPP-373
> URL: https://issues.apache.org/jira/browse/MINIFICPP-373
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: marco polo
>Assignee: marco polo
>Priority: Critical
>
> Core minifi needs to be in whole-archive for linux in Cmake



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4782) When reverting a flow, we do not revert required properties to empty values

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4782:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2406
  
+1 looks good and verified that versioned flows can roll back required 
properties to be empty, merging


> When reverting a flow, we do not revert required properties to empty values
> ---
>
> Key: NIFI-4782
> URL: https://issues.apache.org/jira/browse/NIFI-4782
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> If I create a Processor and place it under version Control, and then I 
> populate a property that is currently unset in the processor (and required), 
> I am given the chance to revert changes. However, doing so does not remove 
> the property from the processor and instead leaves the processor marked as 
> 'locally modified', with the value still set. We should instead remove the 
> value of the property, even if the property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2406: NIFI-4782: Allow the value of a Required Property to be mo...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2406
  
+1 looks good and verified that versioned flows can roll back required 
properties to be empty, merging


---

[GitHub] nifi-minifi pull request #102: MINIFI-317 Adding Hipchat information to the ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi/pull/102


---

[GitHub] nifi-minifi pull request #108: MINIFI-415 Adjusting logging when a bundle is...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi/pull/108


---

[GitHub] nifi-minifi pull request #109: MINIFI-421 Updating MiNiFi to make use of NiF...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi/pull/109


---

[jira] [Updated] (NIFI-4428) Implement PutDruid Processor and Controller

[Joseph Witt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Witt updated NIFI-4428:
--
Fix Version/s: 1.6.0

> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
> Fix For: 1.6.0
>
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-4428) Implement PutDruid Processor and Controller

[Joseph Witt (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph Witt updated NIFI-4428:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

+1 merged to master

> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4428:
--

Github user asfgit closed the pull request at:

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


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit 7e29103995e4b4838616c29770b91b762adac375 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7e29103 ]

NIFI-4428: This closes #2310. Updated POM versions to current master branch

Signed-off-by: joewitt 


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit ecb8067883817c97dc4a54951171c37e36af2f03 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ecb8067 ]

NIFI-4428: Replaced JSON input with RecordReader
using per-record flowfiles
NIFI-4428: Added initial L, fixed dependency hierarchy

NIFI-4428: Exposed additional ZK properties

NIFI-4428: More work to reduce dependencies in Druid artifacts

NIFI-4428: Removed inaccessible attribute

NIFI-4428: Fixed typo in property description

NIFI-4428: Updates to Druid NAR L

NIFI-4428: Updated LICENSE to refer to ICU License for icu4j


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2310: NIFI-4428: Add PutDruidRecord processor and DruidTr...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (NIFI-4428) Implement PutDruid Processor and Controller

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4428:
---

Commit 7fa0a34aba23ea390720a8f41aefbe59f26b15c9 in nifi's branch 
refs/heads/master from vvaks
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7fa0a34 ]

NIFI-4428: - Implement PutDruid Processor and Controller

update

added provenance report

added parameters for batch control

WIP


> Implement PutDruid Processor and Controller
> ---
>
> Key: NIFI-4428
> URL: https://issues.apache.org/jira/browse/NIFI-4428
> Project: Apache NiFi
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: Vadim Vaks
>Assignee: Matt Burgess
>Priority: Major
>
> Implement a PutDruid Processor and Controller using Tranquility API. This 
> will enable Nifi to index contents of flow files in Druid. The implementation 
> should also be able to handle late arriving data (event timestamp points to 
> Druid indexing task that has closed, segment granularity and grace window 
> period expired). Late arriving data is typically dropped. Nifi should allow 
> late arriving data to be diverted to FAILED or DROPPED relationship. That 
> would allow late arriving data to be stored on HDFS or S3 until a re-indexing 
> task can merge it into the correct segment in deep storage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (MINIFICPP-331) Implement string replacement functions in Expression Language

[Andrew Christianson (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Christianson resolved MINIFICPP-331.
---
Resolution: Fixed

> Implement string replacement functions in Expression Language
> -
>
> Key: MINIFICPP-331
> URL: https://issues.apache.org/jira/browse/MINIFICPP-331
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> Implement these in EL:
> replace
> replaceFirst
> replaceAll
> replaceNull
> replaceEmpty



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-114) Consolidate JSON API use to RapidJSON

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327510#comment-16327510
 ] 

ASF GitHub Bot commented on MINIFICPP-114:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
Suggest if we are going to merge it, a good time would be the very start of 
0.5.0 so we have plenty of time to test and fix any issues that crop up by the 
time the next release comes around.


> Consolidate JSON API use to RapidJSON
> -
>
> Key: MINIFICPP-114
> URL: https://issues.apache.org/jira/browse/MINIFICPP-114
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: John Reynolds
>Assignee: John Reynolds
>Priority: Major
> Fix For: 0.4.0
>
>
> MiNiFi was updated with new dependencies to jsoncpp: 
> SiteToSiteProvenanceReportingTask
> Performance observations indicate significant improvements with RapidJSON vs. 
> jsoncpp.  Convert all use of jsoncpp to RapidJSON where applicable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #191: MINIFICPP-114 Consolidate JSON API use to RapidJ...

[achristianson]

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/191
  
Suggest if we are going to merge it, a good time would be the very start of 
0.5.0 so we have plenty of time to test and fix any issues that crop up by the 
time the next release comes around.


---

[jira] [Commented] (NIFI-4782) When reverting a flow, we do not revert required properties to empty values

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4782:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2406
  
Reviewing...


> When reverting a flow, we do not revert required properties to empty values
> ---
>
> Key: NIFI-4782
> URL: https://issues.apache.org/jira/browse/NIFI-4782
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> If I create a Processor and place it under version Control, and then I 
> populate a property that is currently unset in the processor (and required), 
> I am given the chance to revert changes. However, doing so does not remove 
> the property from the processor and instead leaves the processor marked as 
> 'locally modified', with the value still set. We should instead remove the 
> value of the property, even if the property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2406: NIFI-4782: Allow the value of a Required Property to be mo...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2406
  
Reviewing...


---

[jira] [Commented] (MINIFICPP-313) GenerateFlowFile 'Unique FlowFiles' property inverted

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327461#comment-16327461
 ] 

ASF GitHub Bot commented on MINIFICPP-313:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/240


> GenerateFlowFile 'Unique FlowFiles' property inverted
> -
>
> Key: MINIFICPP-313
> URL: https://issues.apache.org/jira/browse/MINIFICPP-313
> Project: NiFi MiNiFi C++
>  Issue Type: Bug
>Reporter: Andrew Christianson
>Assignee: Dustin Rodrigues
>Priority: Minor
> Fix For: 0.4.0
>
>
> 'Unique FlowFiles' must be set to false in order to get unique flow files, 
> which is backward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp pull request #240: MINIFICPP-313: correctly implement unique...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/240


---

[jira] [Updated] (NIFI-4763) Versioned Flows show as dirty when component versions change

[Bryan Bende (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Bende updated NIFI-4763:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.6.0
>
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4763) Versioned Flows show as dirty when component versions change

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4763:
--

Github user asfgit closed the pull request at:

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


> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.6.0
>
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2393: NIFI-4763: Ignore differences in components' Bundle...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (NIFI-4763) Versioned Flows show as dirty when component versions change

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on NIFI-4763:
---

Commit d93d53817761772e623d4dd2411fc5474797ec42 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d93d538 ]

NIFI-4763: Ignore differences in components' Bundle Version when comparing a 
local flow to a flow in the registry

This closes #2393.

Signed-off-by: Bryan Bende 


> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.6.0
>
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4763) Versioned Flows show as dirty when component versions change

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4763:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2393
  
+1 looks good and verified behavior, merging


> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.6.0
>
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2393: NIFI-4763: Ignore differences in components' Bundle Versio...

[bbende]

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2393
  
+1 looks good and verified behavior, merging


---

[jira] [Commented] (MINIFICPP-331) Implement string replacement functions in Expression Language

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327449#comment-16327449
 ] 

ASF GitHub Bot commented on MINIFICPP-331:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/226


> Implement string replacement functions in Expression Language
> -
>
> Key: MINIFICPP-331
> URL: https://issues.apache.org/jira/browse/MINIFICPP-331
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> Implement these in EL:
> replace
> replaceFirst
> replaceAll
> replaceNull
> replaceEmpty



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp pull request #226: MINIFICPP-331 Implemented string replacem...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/226


---

[jira] [Updated] (NIFI-4782) When reverting a flow, we do not revert required properties to empty values

[Mark Payne (JIRA)]

 [ 
https://issues.apache.org/jira/browse/NIFI-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne updated NIFI-4782:
-
Fix Version/s: 1.6.0
   Status: Patch Available  (was: Open)

> When reverting a flow, we do not revert required properties to empty values
> ---
>
> Key: NIFI-4782
> URL: https://issues.apache.org/jira/browse/NIFI-4782
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> If I create a Processor and place it under version Control, and then I 
> populate a property that is currently unset in the processor (and required), 
> I am given the chance to revert changes. However, doing so does not remove 
> the property from the processor and instead leaves the processor marked as 
> 'locally modified', with the value still set. We should instead remove the 
> value of the property, even if the property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4782) When reverting a flow, we do not revert required properties to empty values

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4782:
--

GitHub user markap14 opened a pull request:

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

NIFI-4782: Allow the value of a Required Property to be moved when ch…

…anging version of a flow or reverting a flow

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] 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?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] 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/markap14/nifi NIFI-4782

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

https://github.com/apache/nifi/pull/2406.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 #2406


commit 93103eb67daab951861ab563fcfc9ac7f8f8e077
Author: Mark Payne 
Date:   2018-01-16T17:36:52Z

NIFI-4782: Allow the value of a Required Property to be moved when changing 
version of a flow or reverting a flow




> When reverting a flow, we do not revert required properties to empty values
> ---
>
> Key: NIFI-4782
> URL: https://issues.apache.org/jira/browse/NIFI-4782
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 1.6.0
>
>
> If I create a Processor and place it under version Control, and then I 
> populate a property that is currently unset in the processor (and required), 
> I am given the chance to revert changes. However, doing so does not remove 
> the property from the processor and instead leaves the processor marked as 
> 'locally modified', with the value still set. We should instead remove the 
> value of the property, even if the property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2406: NIFI-4782: Allow the value of a Required Property t...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-4782: Allow the value of a Required Property to be moved when ch…

…anging version of a flow or reverting a flow

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] 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?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] 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/markap14/nifi NIFI-4782

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

https://github.com/apache/nifi/pull/2406.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 #2406


commit 93103eb67daab951861ab563fcfc9ac7f8f8e077
Author: Mark Payne 
Date:   2018-01-16T17:36:52Z

NIFI-4782: Allow the value of a Required Property to be moved when changing 
version of a flow or reverting a flow




---

[jira] [Commented] (MINIFICPP-331) Implement string replacement functions in Expression Language

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/MINIFICPP-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327430#comment-16327430
 ] 

ASF GitHub Bot commented on MINIFICPP-331:
--

Github user phrocker commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/226
  
@achristianson Seems good. It looks like the failing build succeeded. Thanks


> Implement string replacement functions in Expression Language
> -
>
> Key: MINIFICPP-331
> URL: https://issues.apache.org/jira/browse/MINIFICPP-331
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> Implement these in EL:
> replace
> replaceFirst
> replaceAll
> replaceNull
> replaceEmpty



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #226: MINIFICPP-331 Implemented string replacement fun...

[phrocker]

Github user phrocker commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/226
  
@achristianson Seems good. It looks like the failing build succeeded. Thanks


---

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4615:
--

Github user sbouchex commented on the issue:

https://github.com/apache/nifi/pull/2276
  
Ok fine for me. I'll do thé ticket + PR soon


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>Priority: Major
> Fix For: 1.5.0
>
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2276: NIFI-4615 processor status is set to the ProcessorStatusDT...

[sbouchex]

Github user sbouchex commented on the issue:

https://github.com/apache/nifi/pull/2276
  
Ok fine for me. I'll do thé ticket + PR soon


---

[GitHub] nifi issue #2405: NIFI-4777 get schema by id even if not latest

[markap14]

Github user markap14 commented on the issue:

https://github.com/apache/nifi/pull/2405
  
@adfel70 thanks for the contribution! I'm a bit concerned about the 
ramifications of this change as-is, though. If I'm understanding the code 
change, it appears to be removing all caching from the controller service. I 
don't think that's what we want to do, as network problems or having the 
Confluent Schema Registry go down would cause the dataflow to stop. I think if 
we want to avoid the caching mechanism, then we would need to expose a property 
to allow the user to choose whether or not they want to do so - or how long 
they want to cache the schema.


---

[GitHub] nifi issue #2276: NIFI-4615 processor status is set to the ProcessorStatusDT...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/2276
  
We only use swagger for documentation generation. Changing the resulting 
value would break the current API that existing clients expect. I believe the 
best path forward would be to fix the documentation by adjusting the annotation 
value. 


---

[jira] [Commented] (NIFI-4763) Versioned Flows show as dirty when component versions change

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4763:
--

Github user bbende commented on the issue:

https://github.com/apache/nifi/pull/2393
  
Reviewing...


> Versioned Flows show as dirty when component versions change
> 
>
> Key: NIFI-4763
> URL: https://issues.apache.org/jira/browse/NIFI-4763
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 1.5.0
>Reporter: Bryan Bende
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.6.0
>
>
> While testing the 1.5.0 RC I happened to have an existing NiFi instance that 
> was running the 1.5.0-SNAPSHOT version of the flow versioning PR, and had a 
> bunch of example versioned flows. I upgraded this instance by replacing the 
> lib directory with everything from the 1.5.0 RC.
> When I went to the UI I noticed all the versioned PGs were showing local 
> changes. Looking at one of them it was because the local flow had upgraded 
> all the component versions to 1.5.0, but the last version of that flow in the 
> registry had the components at 1.5.0-SNAPSHOT.
> At this point you can try to rollback the local changes, but it can't really 
> rollback because there are no more processors for 1.5.0-SNAPSHOT. You can 
> save a new version of the flow with the new component versions and all is 
> good.
> This won't really be an issue until the next release when folks have already 
> been using 1.5.0 + registry for a while and upgrade to 1.6.0 (or whatever the 
> next release is). We may want to ignore component version differences until 
> sometime in the future when we have an extension registry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4615) Processor status is not reported with the API

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-4615:
--

Github user sbouchex commented on the issue:

https://github.com/apache/nifi/pull/2276
  
Well... Changing the API is not good, so I would change the RunStatus class 
instead by changing the constants to uppercase.


> Processor status is not reported with the API
> -
>
> Key: NIFI-4615
> URL: https://issues.apache.org/jira/browse/NIFI-4615
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Configuration Management
>Affects Versions: 1.4.0
>Reporter: Sébastien Bouchex Bellomié
>Priority: Major
> Fix For: 1.5.0
>
>
> * Start a processor
> * Request its status with the Processor/get/{id] API
> Issue : ProcessorEntity.status.runStatus is always null
> Note : DtoFactory.createProcessorStatusDto do not set the processor status



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (MINIFICPP-367) Implement expression language arithmetic operations

[Andrew Christianson (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MINIFICPP-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Christianson reassigned MINIFICPP-367:
-

Assignee: Andrew Christianson

> Implement expression language arithmetic operations
> ---
>
> Key: MINIFICPP-367
> URL: https://issues.apache.org/jira/browse/MINIFICPP-367
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> Mathematical Operations and Numeric Manipulation
> plus
> minus
> multiply
> divide
> mod
> toRadix
> fromRadix
> random
> math



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)