[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
Github is taking a long time to replicate but here is a link to the commit 
in apache (I pushed it, I swear, lol):


https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=4a4d60e6af5014342039f751c7b058079d643f7b


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2335) "Starting" a process group doesn't trigger a save

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2335:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolved via PR 698

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

> "Starting" a process group doesn't trigger a save
> -
>
> Key: NIFI-2335
> URL: https://issues.apache.org/jira/browse/NIFI-2335
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> If a process group is started as a whole it will not currently trigger a 
> save. 
> This can cause problems if the group is started and then the instance 
> restarts, the whole group will still be in the stopped state.



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

[jira] [Updated] (NIFI-2080) When selecting multiple components, text is clipped in "Operate" panel

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2080:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolved via PR 698

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

> When selecting multiple components, text is clipped in "Operate" panel
> --
>
> Key: NIFI-2080
> URL: https://issues.apache.org/jira/browse/NIFI-2080
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
>
> When I select multiple components on my canvas, the text in the "Operate" 
> panel shows "Multiple components select..." instead of "Multiple component 
> selected". This is on OSX when the "Show scroll bars" System Preference is 
> set to "Always." If I change that preference to some other value, it properly 
> shows "Multiple components selected"



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

[jira] [Updated] (NIFI-2235) Conditions are inconsistent between Operate palette & context menu

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2235:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolved via PR 698

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

> Conditions are inconsistent between Operate palette & context menu
> --
>
> Key: NIFI-2235
> URL: https://issues.apache.org/jira/browse/NIFI-2235
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Mark Payne
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> Specifically, the ability to Copy was noticed as being different, but there 
> may be others. To replicate, create two processors and change permissions so 
> that you have permissions to view both but only permissions to modify one of 
> them.  I also gave myself NO permissions to modify the group that the 
> components are in. Select both processors in the UI. The palette gives the 
> ability to copy the components but the context menu has nothing in it.



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

[jira] [Updated] (NIFI-2242) UI does not render components properly if moving multiple components with mixed permissions

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2242:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolved via PR 698

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

> UI does not render components properly if moving multiple components with 
> mixed permissions
> ---
>
> Key: NIFI-2242
> URL: https://issues.apache.org/jira/browse/NIFI-2242
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> I selected several processors and connections (a small, disconnected graph) 
> and dragged the components to the right. When I released, I got an error 
> message because I didn't have 'write' permissions to one of the processors. 
> All of the other processors moved, but he one processor did not. As a result, 
> the connections were also not refreshed properly and were not connecting the 
> components visually. Clicking 'refresh' on the graph did cause the 
> connections to be redrawn properly.
> This could be addressed in two different ways. First, we could simply refresh 
> the canvas in this case.
> Secondly, we could use a Flow Snippet to move the components, in which case 
> none of the components would be moved if the user attempted this action 
> because the user does not have sufficient permissions for all components.



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

[jira] [Updated] (NIFI-1800) Scope Controller Services by Process Group

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-1800:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolved via PR 698

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

> Scope Controller Services by Process Group
> --
>
> Key: NIFI-1800
> URL: https://issues.apache.org/jira/browse/NIFI-1800
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework, Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> - Update framework to manage Controller Services by Process Group
> - Update Controller Service persistence to include Process Group



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

[jira] [Updated] (NIFI-2307) Ensure the Connection Configuration and Details Dialog Open

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2307:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Resolved via PR 698

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

> Ensure the Connection Configuration and Details Dialog Open
> ---
>
> Key: NIFI-2307
> URL: https://issues.apache.org/jira/browse/NIFI-2307
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.0.0
>
>
> When appropriate we need to ensure the connection configuration and details 
> dialog open. We were not taking into account the access policies of the 
> source and destination components. Consider using the permissions of the 
> source and destination to drive the permissions of the connection.



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

[jira] [Created] (NIFI-2358) Process Group panel doesn't render details without Write permissions

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2358:
--

 Summary: Process Group panel doesn't render details without Write 
permissions
 Key: NIFI-2358
 URL: https://issues.apache.org/jira/browse/NIFI-2358
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall


Have R/W permissions
open process group config
see ability to see and modify the PG name and details
remove W permission
open process group config
see "Process group name ... Process group comments" but no name or comments.

I believe this is due to it seeing I don't have write permission and then not 
rendering the modifiable box but not rendering anything else

Also this panel should have more details about the PG. UUID would be especially 
useful at the top to reference when viewing CS process groups.



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

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
+1

Visually verified code and comments were addressed. Did a contrib check 
build and on a 3 node secure cluster ran through each ticket and did many 
different iterations of various paths of logic. Thanks Matt @mcgilman, I will 
merge it in.

I will be creating a ticket for the controller service/process group Id 
because there is another problem with that panel (without W permissions the 
process group details don't show up).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2090) Add support for HL7 segment names and components in ExtractHL7Attributes

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2090:
---

[~jfrazee] hello - this checks out w/full clean build + contrib check.  I see 
your comment though and am wondering if that means you don't want this merged 
yet.  I'd say if this gets you a productive step forward let's have this go 
forward and for the other ideas you have spawn off another JIRA to be tackled 
later.

Let me know what you'd like to do.  If you think this is good as-is please go 
ahead and squash the commits and force push and let me know.

Thanks
Joe

> Add support for HL7 segment names and components in ExtractHL7Attributes
> 
>
> Key: NIFI-2090
> URL: https://issues.apache.org/jira/browse/NIFI-2090
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>
> HL7 segments and components (segment fields) have descriptive names, e.g., 
> MSH.12 is Version ID and PID.5 is Patient Name. ExtractHL7Attributes should 
> support using these names in addition to the numeric identifiers.
> Some HL7 segment fields are also "composite" and have sub-elements of their 
> own (separated by ^). For example, PID.5 is the Patient Name, which is 
> sub-divided into family name, given name, etc. It would be nice to have 
> access to the individual components.



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

[jira] [Updated] (NIFI-2090) Add support for HL7 segment names and components in ExtractHL7Attributes

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2090:
--
Status: Patch Available  (was: Open)

> Add support for HL7 segment names and components in ExtractHL7Attributes
> 
>
> Key: NIFI-2090
> URL: https://issues.apache.org/jira/browse/NIFI-2090
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Joey Frazee
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>
> HL7 segments and components (segment fields) have descriptive names, e.g., 
> MSH.12 is Version ID and PID.5 is Patient Name. ExtractHL7Attributes should 
> support using these names in addition to the numeric identifiers.
> Some HL7 segment fields are also "composite" and have sub-elements of their 
> own (separated by ^). For example, PID.5 is the Patient Name, which is 
> sub-divided into family name, given name, etc. It would be nice to have 
> access to the individual components.



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

[jira] [Updated] (NIFI-2298) Add missing futures for ConsumeKafka

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2298:
--
Assignee: Oleg Zhurakousky  (was: Joseph Witt)

> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Updated] (NIFI-2298) Add missing futures for ConsumeKafka

[Joseph Witt (JIRA)]

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

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

> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[ASF subversion and git services (JIRA)]

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

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

Commit 89d7d7721f3901f99dca9d6d964dc0f7a641b458 in nifi's branch refs/heads/0.x 
from [~ozhurakousky]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=89d7d77 ]

NIFI-2298 added Kafka consume attributes to a FlowFile


> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2298:
---

looks good.  merging to master and 0.x then will close.

> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-2298 This closes #687 added Kafka consume attributes to a FlowFile


> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2298:
--

Github user asfgit closed the pull request at:

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


> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Updated] (NIFI-2253) zookeeper server cannot interpret "space" in ZK connection string, in nifi.properties config file

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2253:
--
Status: Patch Available  (was: Open)

> zookeeper server cannot interpret "space" in ZK connection string, in 
> nifi.properties config file
> -
>
> Key: NIFI-2253
> URL: https://issues.apache.org/jira/browse/NIFI-2253
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Haimo Liu
>Assignee: Joseph Witt
>Priority: Minor
> Fix For: 1.0.0
>
>
> ZK server cannot interpret space in the following connection string 
> (nifi.properties config file):
> nifi.zookeeper.connect.string=localhost:2181,localhost:2182,localhost:2183
> in this case, multiple NIFI nodes will run in a standalone mode instead of 
> operating in a clustered mode.



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

[GitHub] nifi pull request #704: NIFI-2253 flexibly cleaning zookeeper connect string

[joewitt]

GitHub user joewitt opened a pull request:

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

NIFI-2253 flexibly cleaning zookeeper connect string



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

$ git pull https://github.com/joewitt/incubator-nifi NIFI-2253

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

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


commit 891d404bf95b7654bf1f1cb5c7c40a1efcb6b7fe
Author: joewitt 
Date:   2016-07-22T02:43:15Z

NIFI-2253 flexibly cleaning zookeeper connect string




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #698: Updating the UI to reflect the access policies being...

[mcgilman]

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

https://github.com/apache/nifi/pull/698#discussion_r71818711
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java
 ---
@@ -2147,9 +2147,15 @@ public ProcessGroupStatus getGroupStatus(final 
ProcessGroup group, final Reposit
 return null;
 }
 
+// if the user is null, this is not a web request so we need to 
treat as authorized - this is the case when
+// gather status for history in a background thread... we then 
will check the access of the user when pulling
+// back history...
+final NiFiUser user = NiFiUserUtils.getNiFiUser();
+final boolean isAuthorized = user == null ? true : 
group.isAuthorized(authorizer, RequestAction.READ, user);
--- End diff --

When handling a web request, the user will always be available. When this 
method is running outside the scope of a web request, there is nothing to 
attempt to authorize (nor should we). This conditional authorization seems 
appropriate to me. However, I think we can clean up the code to make the 
distinction a little more clear and deliberate.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (NIFI-2298) Add missing futures for ConsumeKafka

[Joseph Witt (JIRA)]

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

Joseph Witt reassigned NIFI-2298:
-

Assignee: Joseph Witt  (was: Oleg Zhurakousky)

> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2298:
---

assigned to myself to review

> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Joseph Witt
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[jira] [Commented] (NIFI-2357) Component hot deployment

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2357:
---

certainly a good idea.  Related to the following proposals

https://cwiki.apache.org/confluence/display/NIFI/Extension+Repositories+%28aka+Extension+Registry%29+for+Dynamically-loaded+Extensions

https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in a cluster)
> "Hot deployment of new processors" has immediate benefits. For example it 
> helps in two very common scenarios :
> a) Development of a complex processor that uses a few nifi services (where 
> mock framework only helps partially). (might be simple in a single node!) .
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2298:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/687
  
There are definitely ways to defeat backpressure from working properly when 
implementing processors though so definitely a fair question for something like 
this.


> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[GitHub] nifi issue #687: NIFI-2298 added Kafka consume attributes to a FlowFile

[joewitt]

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/687
  
There are definitely ways to defeat backpressure from working properly when 
implementing processors though so definitely a fair question for something like 
this.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-1977) Property descriptors without explicit validators are not recognized

[Puspendu Banerjee (JIRA)]

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

Puspendu Banerjee commented on NIFI-1977:
-

Let me look through it tonight.

> Property descriptors without explicit validators are not recognized
> ---
>
> Key: NIFI-1977
> URL: https://issues.apache.org/jira/browse/NIFI-1977
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andrew Grande
>
> Looks like a bug in a testing framework.
> I have a simple test case like this one:
> {code:java}
> @Test
> public void customHeader() {
> final TestRunner runner = 
> TestRunners.newTestRunner(ParseCSVRecord.class);
> runner.setProperty(PROP_CUSTOM_HEADER, "Column 1,Column 2");
> runner.enqueue("row1col1,row1col2\nrow2col1, row2col2");
> runner.run();
> {code}
> When a property is declared without an explicit validator, the test runner 
> fails complaining that Custom Header is not a supported property (yes, I've 
> added it to the descriptors list).
> {code:java}
> public static final PropertyDescriptor PROP_CUSTOM_HEADER = new 
> PropertyDescriptor.Builder()
> .name("Custom Header")
> .description("Use this header (delimited according to set rules) instead of 
> auto-discovering it from schema")
> .required(false)  
>   .expressionLanguageSupported(true)
> .build();
> {code}
> The intent here is to not have a validator declared, but rather implement 
> more complex logic in the customValidate() callback, but the test never gets 
> to that point.



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

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2298:
--

Github user xmlking commented on the issue:

https://github.com/apache/nifi/pull/687
  
Yes. Thanks 

Sent from my iPhone

> On Jul 21, 2016, at 5:09 PM, Oleg Zhurakousky  
wrote:
> 
> @xmlking Back Pressure is the function of all processors so there is 
nothing specific required in ConsumeKafka to handle it. Does that answer your 
question?
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 



> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[GitHub] nifi issue #687: NIFI-2298 added Kafka consume attributes to a FlowFile

[xmlking]

Github user xmlking commented on the issue:

https://github.com/apache/nifi/pull/687
  
Yes. Thanks 

Sent from my iPhone

> On Jul 21, 2016, at 5:09 PM, Oleg Zhurakousky  
wrote:
> 
> @xmlking Back Pressure is the function of all processors so there is 
nothing specific required in ConsumeKafka to handle it. Does that answer your 
question?
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
> 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2298) Add missing futures for ConsumeKafka

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2298:
--

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/687
  
@xmlking Back Pressure is the function of all processors so there is 
nothing specific required in ConsumeKafka to handle it. Does that answer your 
question?


> Add missing futures for ConsumeKafka
> 
>
> Key: NIFI-2298
> URL: https://issues.apache.org/jira/browse/NIFI-2298
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 0.7.0
>Reporter: sumanth chinthagunta
>Assignee: Oleg Zhurakousky
>  Labels: kafka
> Fix For: 1.0.0, 0.8.0
>
>
> The new ConsumeKafka processor  is missing some capabilities that were 
> present in old getKafka processor. 
> 1. New ConsumeKafka is not writing critical Kafka attributes  i.e., 
> kafka.key, kafka.offset, kafka.partition etc into flowFile attributes. 
> Old getKafka processor: 
> {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:17:00 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19709945781167274'
> Key: 'kafka.key'
>Value: '\{"database":"test","table":"sc_job","pk.systemid":1\}'
> Key: 'kafka.offset'
>Value: '1184010261'
> Key: 'kafka.partition'
>Value: '0'
> Key: 'kafka.topic'
>Value: ‘data'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '244059bb-9ad9-4d74-b1fb-312eee72124a'
>  {quote}
>  
> New ConsumeKafka processor : 
>  {quote}
> Standard FlowFile Attributes
> Key: 'entryDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'lineageStartDate'
>Value: 'Sun Jul 17 15:18:41 CDT 2016'
> Key: 'fileSize'
>Value: '183'
> FlowFile Attribute Map Content
> Key: 'filename'
>Value: '19710046870478139'
> Key: 'path'
>Value: './'
> Key: 'uuid'
>Value: '349fbeb3-e342-4533-be4c-424793fa5c59’
> {quote}
> 2. getKafka/petKafka are compatible with Kafka 0.8.x and 0.9.x . 
> Please make new PublishKafka/ConsumeKafka processors based on Kafka 0.10 
> version. 
> 3. Support subscribing to multiple topics i.e., topic:  topic1,topic2 
> 4. Support configurable Serializer/DeSerializer for String, JSON , Avro etc. 



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

[GitHub] nifi issue #687: NIFI-2298 added Kafka consume attributes to a FlowFile

[olegz]

Github user olegz commented on the issue:

https://github.com/apache/nifi/pull/687
  
@xmlking Back Pressure is the function of all processors so there is 
nothing specific required in ConsumeKafka to handle it. Does that answer your 
question?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2357) Component hot deployment

[n h (JIRA)]

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

n h updated NIFI-2357:
--
Description: 
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deployment of new processors" has immediate benefits. For example it helps 
in two very common scenarios :

a) Development of a complex processor that uses a few nifi services (where mock 
framework only helps partially). It is very helpful even if it is only 
supported for "single node" .
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".


  was:
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deployment of new processors" has immediate benefits. For example it helps 
in two very common scenarios :

a) Development of a complex processor that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in a cluster)
> "Hot deployment of new processors" has immediate benefits. For example it 
> helps in two very common scenarios :
> a) Development of a complex processor that uses a few nifi services (where 
> mock framework only helps partially). It is very helpful even if it is only 
> supported for "single node" .
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Updated] (NIFI-2357) Component hot deployment

[n h (JIRA)]

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

n h updated NIFI-2357:
--
Description: 
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deployment of new processors" has immediate benefits. For example it helps 
in two very common scenarios :

a) Development of complex processors that use a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".


  was:
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deployment of new processors" has immediate benefits. For example it helps 
in two very common scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in a cluster)
> "Hot deployment of new processors" has immediate benefits. For example it 
> helps in two very common scenarios :
> a) Development of complex processors that use a few nifi services (where mock 
> framework only helps partially). It is also very helpful in development 
> environment (single node).
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Updated] (NIFI-2357) Component hot deployment

[n h (JIRA)]

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

n h updated NIFI-2357:
--
Description: 
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deployment of new processors" has immediate benefits. For example it helps 
in two very common scenarios :

a) Development of a complex processor that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".


  was:
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deployment of new processors" has immediate benefits. For example it helps 
in two very common scenarios :

a) Development of complex processors that use a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in a cluster)
> "Hot deployment of new processors" has immediate benefits. For example it 
> helps in two very common scenarios :
> a) Development of a complex processor that uses a few nifi services (where 
> mock framework only helps partially). It is also very helpful in development 
> environment (single node).
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Updated] (NIFI-2357) Component hot deployment

[n h (JIRA)]

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

n h updated NIFI-2357:
--
Description: 
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deployment of new processors" has immediate benefits. For example it helps 
in two very common scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".


  was:
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in a cluster)
> "Hot deployment of new processors" has immediate benefits. For example it 
> helps in two very common scenarios :
> a) Development of complex processors that uses a few nifi services (where 
> mock framework only helps partially). It is also very helpful in development 
> environment (single node).
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Updated] (NIFI-2357) Component hot deployment

[n h (JIRA)]

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

n h updated NIFI-2357:
--
Description: 
Hot deployment of new/upgraded components is a critical requirement in may 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in clustered deployments)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".


  was:
Hot deployment of new/"upgraded components is a critical requirement in may 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in clustered deployments)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in may 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in clustered deployments)
> "Hot deploy of new processors" helps in two very usefule scenarios :
> a) Development of complex processors that uses a few nifi services (where 
> mock framework only helps partially). It is also very helpful in development 
> environment (single node).
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Updated] (NIFI-2357) Component hot deployment

[n h (JIRA)]

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

n h updated NIFI-2357:
--
Description: 
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in clustered deployments)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".


  was:
Hot deployment of new/upgraded components is a critical requirement in may 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in clustered deployments)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in clustered deployments)
> "Hot deploy of new processors" helps in two very usefule scenarios :
> a) Development of complex processors that uses a few nifi services (where 
> mock framework only helps partially). It is also very helpful in development 
> environment (single node).
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Updated] (NIFI-2357) Component hot deployment

[n h (JIRA)]

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

n h updated NIFI-2357:
--
Description: 
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in a cluster)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".


  was:
Hot deployment of new/upgraded components is a critical requirement in many 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in clustered deployments)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".



> Component hot deployment
> 
>
> Key: NIFI-2357
> URL: https://issues.apache.org/jira/browse/NIFI-2357
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Core Framework
>Reporter: n h
>  Labels: Deployment, Hot
>
> Hot deployment of new/upgraded components is a critical requirement in many 
> scenarios. A few suggestions are :
> 1. Hot deployment of new processors/components 
> 2. Hot deployment of processors/components that are not used in current flow 
> context
> 3. Rolling upgrades (in a cluster)
> "Hot deploy of new processors" helps in two very usefule scenarios :
> a) Development of complex processors that uses a few nifi services (where 
> mock framework only helps partially). It is also very helpful in development 
> environment (single node).
> b) Complex system that can't be restarted (Or has very short maintenance time 
> : a few hours each month/year). In this situation we could build "upgraded 
> processor" and use them as "new processor".



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

[jira] [Created] (NIFI-2357) Component hot deployment

[n h (JIRA)]

n h created NIFI-2357:
-

 Summary: Component hot deployment
 Key: NIFI-2357
 URL: https://issues.apache.org/jira/browse/NIFI-2357
 Project: Apache NiFi
  Issue Type: New Feature
  Components: Core Framework
Reporter: n h


Hot deployment of new/"upgraded components is a critical requirement in may 
scenarios. A few suggestions are :

1. Hot deployment of new processors/components 
2. Hot deployment of processors/components that are not used in current flow 
context
3. Rolling upgrades (in clustered deployments)

"Hot deploy of new processors" helps in two very usefule scenarios :

a) Development of complex processors that uses a few nifi services (where mock 
framework only helps partially). It is also very helpful in development 
environment (single node).
b) Complex system that can't be restarted (Or has very short maintenance time : 
a few hours each month/year). In this situation we could build "upgraded 
processor" and use them as "new processor".




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

[jira] [Updated] (NIFI-2050) Advanced button blends with cancel button

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-2050:
--
Status: Patch Available  (was: In Progress)

> Advanced button blends with cancel button
> -
>
> Key: NIFI-2050
> URL: https://issues.apache.org/jira/browse/NIFI-2050
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
> Attachments: nifi-2050_advanced-button.png
>
>
> UpdateAttribute Processor > Configure Processor: advanced button blends in 
> with cancel button. Need UX...maybe make it a link...
> Also need to style the custom ui for the advanced dialog.



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

[jira] [Updated] (NIFI-2134) Provenance Event dialog – Details tab

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-2134:
--
Status: Patch Available  (was: In Progress)

> Provenance Event dialog – Details tab
> -
>
> Key: NIFI-2134
> URL: https://issues.apache.org/jira/browse/NIFI-2134
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
>
> For the right column listing parent/child flowfiles:
> * Remove excess top/bottom margin around the headers (i.e., Parent FlowFiles 
> & Child FlowFiles headings)
> * Parent FlowFiles heading should top align with the 'Time' label in the left 
> column
> * Space below the each header should be 10px
> * For any FlowFile UUIDs that are listed, use the same stacked label/value 
> style used in the left column



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

[jira] [Updated] (NIFI-2139) Provenance Event dialog – ​Content tab

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-2139:
--
Status: Patch Available  (was: In Progress)

> Provenance Event dialog – ​Content tab
> --
>
> Key: NIFI-2139
> URL: https://issues.apache.org/jira/browse/NIFI-2139
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Rob Moran
>Assignee: Scott Aslan
>
> For Download, View, and (replay) Submit button​s, style the same (in 
> appearance only) as the Advanced button described in NIFI-2050.
> * Apply 10px between the Download and View buttons
> * Change the name for the Submit button to 'REPLAY'
> * For replay-content-message (when replay content is not available), 
> font-size should be 13px
> Please use these icons for each button:
> * fa-download for Download
> * fa-eye for View
> * fa-repeat for Replay



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

[jira] [Updated] (NIFI-2076) New Inline Controller Service Dialog

[Scott Aslan (JIRA)]

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

Scott Aslan updated NIFI-2076:
--
Status: Patch Available  (was: In Progress)

> New Inline Controller Service Dialog
> 
>
> Key: NIFI-2076
> URL: https://issues.apache.org/jira/browse/NIFI-2076
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
>
> - is too wide



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

[jira] [Commented] (NIFI-2050) Advanced button blends with cancel button

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2050:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-2050] [NIFI-2076] [NIFI-2136] [NIFI-2139] [NIFI-2134]

-update dialog advanced buttons
-fix Add inline controller service dialog description width
-update provenance details dialog

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

$ git pull https://github.com/scottyaslan/nifi devBranch

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

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


commit 57a6bd2acd333b249cbfa93ac67bc6a178cef335
Author: Scott Aslan 
Date:   2016-07-21T22:39:59Z

[NIFI-2050] update dialog advanced buttons

commit 8eb525779b1199bde720f148b1c8f1772e3a9b7e
Author: Scott Aslan 
Date:   2016-07-21T22:40:15Z

[NIFI-2076] fix Add inline controller service dialog description width

commit b1ae45c0c7cee5da8c3d3863e7cd2e9c24b7f176
Author: Scott Aslan 
Date:   2016-07-21T22:41:32Z

[NIFI-2136] [NIFI-2139] [NIFI-2134] update provenance details dialog




> Advanced button blends with cancel button
> -
>
> Key: NIFI-2050
> URL: https://issues.apache.org/jira/browse/NIFI-2050
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
> Attachments: nifi-2050_advanced-button.png
>
>
> UpdateAttribute Processor > Configure Processor: advanced button blends in 
> with cancel button. Need UX...maybe make it a link...
> Also need to style the custom ui for the advanced dialog.



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

[GitHub] nifi pull request #703: [NIFI-2050] [NIFI-2076] [NIFI-2136] [NIFI-2139] [NIF...

[scottyaslan]

GitHub user scottyaslan opened a pull request:

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

[NIFI-2050] [NIFI-2076] [NIFI-2136] [NIFI-2139] [NIFI-2134]

-update dialog advanced buttons
-fix Add inline controller service dialog description width
-update provenance details dialog

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

$ git pull https://github.com/scottyaslan/nifi devBranch

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

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


commit 57a6bd2acd333b249cbfa93ac67bc6a178cef335
Author: Scott Aslan 
Date:   2016-07-21T22:39:59Z

[NIFI-2050] update dialog advanced buttons

commit 8eb525779b1199bde720f148b1c8f1772e3a9b7e
Author: Scott Aslan 
Date:   2016-07-21T22:40:15Z

[NIFI-2076] fix Add inline controller service dialog description width

commit b1ae45c0c7cee5da8c3d3863e7cd2e9c24b7f176
Author: Scott Aslan 
Date:   2016-07-21T22:41:32Z

[NIFI-2136] [NIFI-2139] [NIFI-2134] update provenance details dialog




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-1995) Support keystores with multiple certificates by exposing alias selection in configuration

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-1995:

Fix Version/s: (was: 1.0.0)

> Support keystores with multiple certificates by exposing alias selection in 
> configuration
> -
>
> Key: NIFI-1995
> URL: https://issues.apache.org/jira/browse/NIFI-1995
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: certificate, keystore, security
>
> Some users and organizations would like to provide different certificates for 
> identification of the same NiFi instance when acting in different roles (for 
> example, one certificate to identify the server for the API / UI interaction, 
> and another to identify the server in cluster communications and/or 
> site-to-site communications). A preliminary list of roles is:
> * API / UI host
> * remote authorization / authentication repositories (communicating with 
> Ranger, LDAP, KDC, etc.)
> * cluster (node/NCM/Zookeeper)
> * site-to-site
> * client when connecting to remote services during data flow ({{InvokeHTTP}}, 
> {{PutSQL}}, etc.)
> This should be implemented in a manner that does not break the default 
> operation (i.e. a keystore with a single certificate value) but allows easy 
> overriding for one or more of the roles listed above. 



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

[jira] [Updated] (NIFI-1990) Implement consistent security controls for cluster, site-to-site, and API communications

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-1990:

Priority: Major  (was: Critical)

> Implement consistent security controls for cluster, site-to-site, and API 
> communications
> 
>
> Key: NIFI-1990
> URL: https://issues.apache.org/jira/browse/NIFI-1990
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>  Labels: client-auth, clustering, security, site-to-site, tls
>
> As discovered in [NIFI-1981], edge cases in configuration of cluster 
> communications over TLS without client authentication caused errors in the 
> application. We should provide a consistent experience, from documentation to 
> configuration to execution:
> * Machine to machine communication should have two settings -- plaintext or 
> TLS with mutual authentication. 
> ** Cluster
> ** Site to Site
> * The API / UI should allow more granular control -- plaintext, TLS with 
> server authentication only, or TLS with mutual authentication. Some clients 
> (API consumers, users in an enterprise environment) may have client 
> certificates, but the majority will not, and TLS authentication of the 
> server, and data integrity and confidentiality assurances should still be 
> available. 
> ** Site to site over the API (see [NIFI-1857]) will respect this setting for 
> the TLS handshake negotiation, but will manually enforce the presence of a 
> client certificate in an HTTP header on any request arriving over HTTPS. 
> The {{nifi.security.needClientAuth}} setting should be removed from 
> nifi.properties. A new setting {{nifi.security.api.needClientAuth}} will be 
> added, and documented to explicitly apply only to the API (and, by extension, 
> Web UI). 



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

[jira] [Updated] (NIFI-1990) Implement consistent security controls for cluster, site-to-site, and API communications

[Andy LoPresto (JIRA)]

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

Andy LoPresto updated NIFI-1990:

Fix Version/s: (was: 1.0.0)

> Implement consistent security controls for cluster, site-to-site, and API 
> communications
> 
>
> Key: NIFI-1990
> URL: https://issues.apache.org/jira/browse/NIFI-1990
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andy LoPresto
>Assignee: Andy LoPresto
>Priority: Critical
>  Labels: client-auth, clustering, security, site-to-site, tls
>
> As discovered in [NIFI-1981], edge cases in configuration of cluster 
> communications over TLS without client authentication caused errors in the 
> application. We should provide a consistent experience, from documentation to 
> configuration to execution:
> * Machine to machine communication should have two settings -- plaintext or 
> TLS with mutual authentication. 
> ** Cluster
> ** Site to Site
> * The API / UI should allow more granular control -- plaintext, TLS with 
> server authentication only, or TLS with mutual authentication. Some clients 
> (API consumers, users in an enterprise environment) may have client 
> certificates, but the majority will not, and TLS authentication of the 
> server, and data integrity and confidentiality assurances should still be 
> available. 
> ** Site to site over the API (see [NIFI-1857]) will respect this setting for 
> the TLS handshake negotiation, but will manually enforce the presence of a 
> client certificate in an HTTP header on any request arriving over HTTPS. 
> The {{nifi.security.needClientAuth}} setting should be removed from 
> nifi.properties. A new setting {{nifi.security.api.needClientAuth}} will be 
> added, and documented to explicitly apply only to the API (and, by extension, 
> Web UI). 



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

[GitHub] nifi pull request #698: Updating the UI to reflect the access policies being...

[JPercivall]

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

https://github.com/apache/nifi/pull/698#discussion_r71795919
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/authorization/ConnectionAuthorizable.java
 ---
@@ -0,0 +1,54 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.authorization;
+
+import org.apache.nifi.authorization.resource.Authorizable;
+import org.apache.nifi.connectable.Connectable;
+import org.apache.nifi.groups.ProcessGroup;
+
+/**
+ * Authorizable for policies of an Authorizable.
--- End diff --

I think this should be "Authorizable for policies of a Connection."


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #698: Updating the UI to reflect the access policies being...

[JPercivall]

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

https://github.com/apache/nifi/pull/698#discussion_r7179
  
--- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/FlowController.java
 ---
@@ -2147,9 +2147,15 @@ public ProcessGroupStatus getGroupStatus(final 
ProcessGroup group, final Reposit
 return null;
 }
 
+// if the user is null, this is not a web request so we need to 
treat as authorized - this is the case when
+// gather status for history in a background thread... we then 
will check the access of the user when pulling
+// back history...
+final NiFiUser user = NiFiUserUtils.getNiFiUser();
+final boolean isAuthorized = user == null ? true : 
group.isAuthorized(authorizer, RequestAction.READ, user);
--- End diff --

This seems like a very insecure way to do things (if null then authorized).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-1800) Scope Controller Services by Process Group

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1800:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
As part of NIFI-1800, when viewing the config for a process group it should 
have the UUID at the top. This way at the very least I can tell which 
controller services belong to this ProcessGroup without trying to remember the 
exact UUID (no tab in that panel shows that information).

Also it may be best to have the name in that column instead of UUID. 


> Scope Controller Services by Process Group
> --
>
> Key: NIFI-1800
> URL: https://issues.apache.org/jira/browse/NIFI-1800
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework, Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> - Update framework to manage Controller Services by Process Group
> - Update Controller Service persistence to include Process Group



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

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
As part of NIFI-1800, when viewing the config for a process group it should 
have the UUID at the top. This way at the very least I can tell which 
controller services belong to this ProcessGroup without trying to remember the 
exact UUID (no tab in that panel shows that information).

Also it may be best to have the name in that column instead of UUID. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
Similar logic is possible when going from the sub group to root group.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
NIFI-2235 offending logic path:
copy processor in root PG
go into PG I do not have modify access
Context menu does not have paste, palette menu allows it to be clicked
after i click paste (and get no access) it correctly refreshes to show no 
ability to paste


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2356) ConvertJSONToSQL Assumes IS_AUTOINCREMENT

[Peter Wicks (JIRA)]

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

Peter Wicks updated NIFI-2356:
--
Description: 
ConvertJSONToSQL Processor, it assumes that the column "IS_AUTOINCREMENT" will 
always be available.

When using Teradata JDBC driver this column is not available.  Available 
columns are:

TABLE_CAT
TABLE_SCHEM
TABLE_NAME
COLUMN_NAME
DATA_TYPE
TYPE_NAME
COLUMN_SIZE
BUFFER_LENGTH
DECIMAL_DIGITS
NUM_PREC_RADIX
NULLABLE
REMARKS
COLUMN_DEF
SQL_DATA_TYPE
SQL_DATETIME_SUB
CHAR_OCTET_LENGTH
ORDINAL_POSITION
IS_NULLABLE
SCOPE_CATLOG
SCOPE_SCHEMA
SCOPE_TABLE
SOURCE_DATA_TYPE

  was:
ConvertJSONToSQL.java assumes that the column "IS_AUTOINCREMENT" will always be 
available.

When using Teradata JDBC driver this column is not available.  Available 
columns are:

TABLE_CAT
TABLE_SCHEM
TABLE_NAME
COLUMN_NAME
DATA_TYPE
TYPE_NAME
COLUMN_SIZE
BUFFER_LENGTH
DECIMAL_DIGITS
NUM_PREC_RADIX
NULLABLE
REMARKS
COLUMN_DEF
SQL_DATA_TYPE
SQL_DATETIME_SUB
CHAR_OCTET_LENGTH
ORDINAL_POSITION
IS_NULLABLE
SCOPE_CATLOG
SCOPE_SCHEMA
SCOPE_TABLE
SOURCE_DATA_TYPE


> ConvertJSONToSQL Assumes IS_AUTOINCREMENT
> -
>
> Key: NIFI-2356
> URL: https://issues.apache.org/jira/browse/NIFI-2356
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: 0.7.0
> Environment: Teradata JDBC
>Reporter: Peter Wicks
>
> ConvertJSONToSQL Processor, it assumes that the column "IS_AUTOINCREMENT" 
> will always be available.
> When using Teradata JDBC driver this column is not available.  Available 
> columns are:
> TABLE_CAT
> TABLE_SCHEM
> TABLE_NAME
> COLUMN_NAME
> DATA_TYPE
> TYPE_NAME
> COLUMN_SIZE
> BUFFER_LENGTH
> DECIMAL_DIGITS
> NUM_PREC_RADIX
> NULLABLE
> REMARKS
> COLUMN_DEF
> SQL_DATA_TYPE
> SQL_DATETIME_SUB
> CHAR_OCTET_LENGTH
> ORDINAL_POSITION
> IS_NULLABLE
> SCOPE_CATLOG
> SCOPE_SCHEMA
> SCOPE_TABLE
> SOURCE_DATA_TYPE



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

[jira] [Created] (NIFI-2356) ConvertJSONToSQL Assumes IS_AUTOINCREMENT

[Peter Wicks (JIRA)]

Peter Wicks created NIFI-2356:
-

 Summary: ConvertJSONToSQL Assumes IS_AUTOINCREMENT
 Key: NIFI-2356
 URL: https://issues.apache.org/jira/browse/NIFI-2356
 Project: Apache NiFi
  Issue Type: Bug
  Components: Extensions
Affects Versions: 0.7.0
 Environment: Teradata JDBC
Reporter: Peter Wicks


ConvertJSONToSQL.java assumes that the column "IS_AUTOINCREMENT" will always be 
available.

When using Teradata JDBC driver this column is not available.  Available 
columns are:

TABLE_CAT
TABLE_SCHEM
TABLE_NAME
COLUMN_NAME
DATA_TYPE
TYPE_NAME
COLUMN_SIZE
BUFFER_LENGTH
DECIMAL_DIGITS
NUM_PREC_RADIX
NULLABLE
REMARKS
COLUMN_DEF
SQL_DATA_TYPE
SQL_DATETIME_SUB
CHAR_OCTET_LENGTH
ORDINAL_POSITION
IS_NULLABLE
SCOPE_CATLOG
SCOPE_SCHEMA
SCOPE_TABLE
SOURCE_DATA_TYPE



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

[jira] [Commented] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2320:
---

ah i see.  i should have read the subject !  Thanks

> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[jira] [Resolved] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[Joseph Witt (JIRA)]

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

Joseph Witt resolved NIFI-2320.
---
Resolution: Fixed

> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[jira] [Updated] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2320:
--
Assignee: Andrew Lim  (was: Joseph Witt)

> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
> Fix For: 1.0.0
>
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
I don't think NIFI-2235 was addressed. I am still able to reproduce


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-2355) Unable to order by any column when viewing Controller Services

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2355:
--

 Summary: Unable to order by any column when viewing Controller 
Services
 Key: NIFI-2355
 URL: https://issues.apache.org/jira/browse/NIFI-2355
 Project: Apache NiFi
  Issue Type: Sub-task
Reporter: Joseph Percivall


Have multiple controller services in a process group
attempt to order by a column by clicking it
nothing happens (see arrow flip)



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

[jira] [Updated] (NIFI-2354) In process group config, Controller Service icons can become unordered

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2354:
---
Summary: In process group config, Controller Service icons can become 
unordered  (was: In processo group config Controller Service icons can become 
unordered)

> In process group config, Controller Service icons can become unordered
> --
>
> Key: NIFI-2354
> URL: https://issues.apache.org/jira/browse/NIFI-2354
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Joseph Percivall
>Priority: Trivial
> Attachments: Screen Shot 2016-07-21 at 3.48.17 PM.png
>
>
> See attached image



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

[jira] [Created] (NIFI-2354) In processo group config Controller Service icons can become unordered

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2354:
--

 Summary: In processo group config Controller Service icons can 
become unordered
 Key: NIFI-2354
 URL: https://issues.apache.org/jira/browse/NIFI-2354
 Project: Apache NiFi
  Issue Type: Sub-task
Reporter: Joseph Percivall
Priority: Trivial
 Attachments: Screen Shot 2016-07-21 at 3.48.17 PM.png

See attached image



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

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/698
  
Good catch. Will update PR shortly. Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-1733) Create Authorizer implementation that uses Apache Ranger

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1733:
--

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/574
  
@bbende happy to take this on for review


> Create Authorizer implementation that uses Apache Ranger
> 
>
> Key: NIFI-1733
> URL: https://issues.apache.org/jira/browse/NIFI-1733
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.0.0
>
>
> In NIFI-1552 we defined a new Authorizer API for 1.0.0. 
> In addition to the standard file-based Authorizer, we should provide an 
> Authorizer implementation that uses Apache Ranger.



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

[jira] [Created] (NIFI-2353) When not clustered, nifi logs warning about not being able to find cluster coordinator

[Mark Payne (JIRA)]

Mark Payne created NIFI-2353:


 Summary: When not clustered, nifi logs warning about not being 
able to find cluster coordinator
 Key: NIFI-2353
 URL: https://issues.apache.org/jira/browse/NIFI-2353
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core Framework
Reporter: Mark Payne
Assignee: Mark Payne
 Fix For: 1.0.0


I saw the following in the logs:


2016-07-21 15:52:07,835 WARN [main] o.a.nifi.controller.StandardFlowService 
Failed to connect to cluster due to: 
org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket due 
to: java.io.IOException: Unable to determine Cluster Coordinator from ZooKeeper
org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket due 
to: java.io.IOException: Unable to determine Cluster Coordinator from ZooKeeper
at 
org.apache.nifi.cluster.protocol.AbstractNodeProtocolSender.createSocket(AbstractNodeProtocolSender.java:112)
 ~[nifi-framework-cluster-protocol-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.cluster.protocol.AbstractNodeProtocolSender.requestConnection(AbstractNodeProtocolSender.java:47)
 ~[nifi-framework-cluster-protocol-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.cluster.protocol.impl.NodeProtocolSenderListener.requestConnection(NodeProtocolSenderListener.java:84)
 ~[nifi-framework-cluster-protocol-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.connect(StandardFlowService.java:773)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:448)
 [nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:746) 
[nifi-jetty-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.apache.nifi.NiFi.(NiFi.java:137) 
[nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at org.apache.nifi.NiFi.main(NiFi.java:227) 
[nifi-runtime-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
Caused by: java.io.IOException: Unable to determine Cluster Coordinator from 
ZooKeeper
at 
org.apache.nifi.cluster.coordination.node.CuratorNodeProtocolSender.getServiceAddress(CuratorNodeProtocolSender.java:110)
 ~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at 
org.apache.nifi.cluster.protocol.AbstractNodeProtocolSender.createSocket(AbstractNodeProtocolSender.java:108)
 ~[nifi-framework-cluster-protocol-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
... 7 common frames omitted
Caused by: org.apache.nifi.cluster.protocol.ProtocolException: Attempted to 
determine Cluster Coordinator address. Zookeeper indicates that address is 
10.200.30.55, but this is not in the expected format of :
at 
org.apache.nifi.cluster.coordination.node.CuratorNodeProtocolSender.getServiceAddress(CuratorNodeProtocolSender.java:86)
 ~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
... 8 common frames omitted



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

[jira] [Created] (NIFI-2352) Adjust location of home link in the error page

[Matt Gilman (JIRA)]

Matt Gilman created NIFI-2352:
-

 Summary: Adjust location of home link in the error page
 Key: NIFI-2352
 URL: https://issues.apache.org/jira/browse/NIFI-2352
 Project: Apache NiFi
  Issue Type: Bug
  Components: Core UI
Reporter: Matt Gilman
 Fix For: 1.0.0


If the message is long, the text will sit on top of the home link.



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

[GitHub] nifi issue #574: NIFI-1733 Adding a Ranger implementation of NiFi's Authoriz...

[YolandaMDavis]

Github user YolandaMDavis commented on the issue:

https://github.com/apache/nifi/pull/574
  
@bbende happy to take this on for review


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-2351) Able to scroll Component name in Policies panel

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2351:
--

 Summary: Able to scroll Component name in Policies panel
 Key: NIFI-2351
 URL: https://issues.apache.org/jira/browse/NIFI-2351
 Project: Apache NiFi
  Issue Type: Sub-task
Reporter: Joseph Percivall


On mac with scroll bars always enabled
view a processor's policy page
able to see a small scroll bar on the processor name and scroll it slightly 



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

[jira] [Commented] (NIFI-2265) Authorization: Able to see hidden processor information in Status History

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2265:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
Relating to NIFI-2265. I have a process group that I do not have view 
permissions on. I have processors in that group that inherit the policy from 
the group. When I view the flow on the canvas or by clicking "stats" I properly 
don't the name but when I view "summary" (from the top menu) I see the names. 

Tracking it down in the developer tools, it looks like it comes from the 
ProcessGroupStatusSnapshots (I don't have view access to that group either).


> Authorization: Able to see hidden processor information in Status History
> -
>
> Key: NIFI-2265
> URL: https://issues.apache.org/jira/browse/NIFI-2265
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Matt Gilman
>Priority: Blocker
>  Labels: UI
> Fix For: 1.0.0
>
> Attachments: NIFI-2265_Summary.png, NIFI-2265_statusHistory.png
>
>
> When a user is not privileged to see a processor, on the canvas the Name and 
> Type of the Processor is properly hidden.  But if you right-click on the 
> processor and select "Stats", this information is displayed in the Status 
> History.
> Screenshot attached.



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

[jira] [Updated] (NIFI-2348) When processor is selected, cannot copy id from palette

[Joseph Percivall (JIRA)]

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

Joseph Percivall updated NIFI-2348:
---
Summary: When processor is selected, cannot copy id from palette  (was: 
When processor is selected, cannot copy id from pallete)

> When processor is selected, cannot copy id from palette
> ---
>
> Key: NIFI-2348
> URL: https://issues.apache.org/jira/browse/NIFI-2348
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Priority: Minor
>
> Processor selected
> Processor details show up in palette
> highlight uuid in palette (processor remains "selected" on graph)
> copy then copies the processor instead of the uuid
> As a user, I would like to copy the uuid when I have the text highlighted 



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

[jira] [Created] (NIFI-2348) When processor is selected, cannot copy id from pallete

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2348:
--

 Summary: When processor is selected, cannot copy id from pallete
 Key: NIFI-2348
 URL: https://issues.apache.org/jira/browse/NIFI-2348
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
Priority: Minor


Processor selected
Processor details show up in palette
highlight uuid in palette (processor remains "selected" on graph)
copy then copies the processor instead of the uuid

As a user, I would like to copy the uuid when I have the text highlighted 



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

[GitHub] nifi-minifi-cpp issue #4: MINIFI-6: Basic C++ implementation for MiNiFi

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/4
  
Hey @benqiu2016.  I have rebased and merged this effort and pushed it to 
nifi-minifi-cpp/MINIFI-6 as part of 9e42ec5f3fdb0804b5977fb1abd8128f612fc71f.  
As it is not yet in master, the PR wasn't automatically closed out.  Would you 
be able to close this out when you have the opportunity?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-1950) Convert 0.x site-to-site access policies when possible

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1950:
--

GitHub user bbende opened a pull request:

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

NIFI-1950 Updating FileAuthorizer to convert access controls from inp…

…ut and output ports during legacy conversion

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

$ git pull https://github.com/bbende/nifi NIFI-1950

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

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


commit ded2830ccca8d9377bf8f5f52ce5c9a4a6040b96
Author: Bryan Bende 
Date:   2016-07-21T16:18:09Z

NIFI-1950 Updating FileAuthorizer to convert access controls from input and 
output ports during legacy conversion




> Convert 0.x site-to-site access policies when possible
> --
>
> Key: NIFI-1950
> URL: https://issues.apache.org/jira/browse/NIFI-1950
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Bryan Bende
>Priority: Blocker
> Fix For: 1.0.0
>
>
> In the 0.x baseline access a Remote Port is configurable. These 
> authorizations are stored in the flow.xml. In the 1.0.0 baseline these 
> decisions will be made by a configurable authorizer. When possible, these 
> access policies need to be converted to the authorizer upon starting with a 
> legacy flow.
> Note: This won't be possible when the authorizer is externally managed. When 
> this is the case, we'll need to document that the access policies will need 
> to be manually restored using the external tool the authorizer supports.



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

[jira] [Updated] (NIFI-2292) Nodes in cluster sometimes become out-of-sync with actual 'connection state' of node

[Mark Payne (JIRA)]

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

Mark Payne updated NIFI-2292:
-
Status: Patch Available  (was: Open)

> Nodes in cluster sometimes become out-of-sync with actual 'connection state' 
> of node
> 
>
> Key: NIFI-2292
> URL: https://issues.apache.org/jira/browse/NIFI-2292
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally I'll see a node that has a different view of the cluster than 
> other nodes. Right now I'm actually seeing "node 1" think it's in 
> 'CONNECTING' state while nodes 2-5 think we have 5/5 nodes connected.
> This also can result in a node that is elected cluster coordinator and then 
> has that role revoked can continually monitor for heartbeats, even though it 
> won't receive them since it's not the coordinator anymore. This results in 
> continually logging a message like "Failed to retrieve any new heartbeat 
> information for nodes. Will not make any decisions based on heartbeats."



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

[GitHub] nifi pull request #701: NIFI-2292: Funnel all cluster node status changes th...

[markap14]

GitHub user markap14 opened a pull request:

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

NIFI-2292: Funnel all cluster node status changes through the cluster 
coordinator…

… instead of having each node broadcast changes to the whole cluster. 
This gives us the ability to increment the updateId consistently without race 
conditions.

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

$ git pull https://github.com/markap14/nifi NIFI-2292

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

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


commit 03942d0091e6adc213dc42e3c81725ab5ca257fa
Author: Mark Payne 
Date:   2016-07-21T18:30:08Z

NIFI-2292: Funnel all cluster node status changes through the cluster 
coordinator instead of having each node broadcast changes to the whole cluster. 
This gives us the ability to increment the updateId consistently without race 
conditions.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2292) Nodes in cluster sometimes become out-of-sync with actual 'connection state' of node

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2292:
--

GitHub user markap14 opened a pull request:

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

NIFI-2292: Funnel all cluster node status changes through the cluster 
coordinator…

… instead of having each node broadcast changes to the whole cluster. This 
gives us the ability to increment the updateId consistently without race 
conditions.

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

$ git pull https://github.com/markap14/nifi NIFI-2292

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

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


commit 03942d0091e6adc213dc42e3c81725ab5ca257fa
Author: Mark Payne 
Date:   2016-07-21T18:30:08Z

NIFI-2292: Funnel all cluster node status changes through the cluster 
coordinator instead of having each node broadcast changes to the whole cluster. 
This gives us the ability to increment the updateId consistently without race 
conditions.




> Nodes in cluster sometimes become out-of-sync with actual 'connection state' 
> of node
> 
>
> Key: NIFI-2292
> URL: https://issues.apache.org/jira/browse/NIFI-2292
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Mark Payne
>Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally I'll see a node that has a different view of the cluster than 
> other nodes. Right now I'm actually seeing "node 1" think it's in 
> 'CONNECTING' state while nodes 2-5 think we have 5/5 nodes connected.
> This also can result in a node that is elected cluster coordinator and then 
> has that role revoked can continually monitor for heartbeats, even though it 
> won't receive them since it's not the coordinator anymore. This results in 
> continually logging a message like "Failed to retrieve any new heartbeat 
> information for nodes. Will not make any decisions based on heartbeats."



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

[GitHub] nifi pull request #702: NIFI-1950 Updating FileAuthorizer to convert access ...

[bbende]

GitHub user bbende opened a pull request:

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

NIFI-1950 Updating FileAuthorizer to convert access controls from inp…

…ut and output ports during legacy conversion

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

$ git pull https://github.com/bbende/nifi NIFI-1950

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

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


commit ded2830ccca8d9377bf8f5f52ce5c9a4a6040b96
Author: Bryan Bende 
Date:   2016-07-21T16:18:09Z

NIFI-1950 Updating FileAuthorizer to convert access controls from input and 
output ports during legacy conversion




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2347) Pasted Components should inherit policies from the original, not the group it's pasted into

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2347:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
Created a new ticket for an issue I saw:
https://issues.apache.org/jira/browse/NIFI-2347


> Pasted Components should inherit policies from the original, not the group 
> it's pasted into
> ---
>
> Key: NIFI-2347
> URL: https://issues.apache.org/jira/browse/NIFI-2347
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Joseph Percivall
>Priority: Blocker
>
> Copy a processor that you have view permissions but not write
> Paste it into a group that you have full permissions
> Pasted processor inherits from the group and gives you full permissions.
> Instead it should copy/inherit the policies from the copied component.



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

[jira] [Commented] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-2320:
--

[~joewitt], I think this can be closed.  I believe all screenshots with the 
older UI in the Getting Started guide have been updated as part of this Jira.

> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[jira] [Created] (NIFI-2347) Pasted Components should inherit policies from the original, not the group it's pasted into

[Joseph Percivall (JIRA)]

Joseph Percivall created NIFI-2347:
--

 Summary: Pasted Components should inherit policies from the 
original, not the group it's pasted into
 Key: NIFI-2347
 URL: https://issues.apache.org/jira/browse/NIFI-2347
 Project: Apache NiFi
  Issue Type: Bug
Reporter: Joseph Percivall
Priority: Blocker


Copy a processor that you have view permissions but not write
Paste it into a group that you have full permissions
Pasted processor inherits from the group and gives you full permissions.

Instead it should copy/inherit the policies from the copied component.



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

[jira] [Commented] (NIFI-1977) Property descriptors without explicit validators are not recognized

[Gregory Hart (JIRA)]

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

Gregory Hart commented on NIFI-1977:


It does appear that all properties are required to have a validator and this is 
enforced in the NiFi UI too. I think the error message is a little misleading.

> Property descriptors without explicit validators are not recognized
> ---
>
> Key: NIFI-1977
> URL: https://issues.apache.org/jira/browse/NIFI-1977
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 0.6.1
>Reporter: Andrew Grande
>
> Looks like a bug in a testing framework.
> I have a simple test case like this one:
> {code:java}
> @Test
> public void customHeader() {
> final TestRunner runner = 
> TestRunners.newTestRunner(ParseCSVRecord.class);
> runner.setProperty(PROP_CUSTOM_HEADER, "Column 1,Column 2");
> runner.enqueue("row1col1,row1col2\nrow2col1, row2col2");
> runner.run();
> {code}
> When a property is declared without an explicit validator, the test runner 
> fails complaining that Custom Header is not a supported property (yes, I've 
> added it to the descriptors list).
> {code:java}
> public static final PropertyDescriptor PROP_CUSTOM_HEADER = new 
> PropertyDescriptor.Builder()
> .name("Custom Header")
> .description("Use this header (delimited according to set rules) instead of 
> auto-discovering it from schema")
> .required(false)  
>   .expressionLanguageSupported(true)
> .build();
> {code}
> The intent here is to not have a validator declared, but rather implement 
> more complex logic in the customValidate() callback, but the test never gets 
> to that point.



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

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
One thing I did notice is when I have selected just GenerateFF I can move 
it (UI properly moves relationship too) but if I have GenerateFF and connection 
selected it fails (message "Must be authorized to modify every component 
selected."). I believe this is because it is checking if I have permission to 
move the connection which in turn checks if I have permission to modify the 
destination (which I don't).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/698
  
Yeah, I'm unable to replicate. The first message you mentioned sounds like 
the request was attempted like it was prior to the fix. Maybe your browser had 
some old JS cached. The "Must be authorized..." message is a client side check 
that I added to address NIFI-2242. Let me know if you still seeing any 
weirdness.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
Actually I think that was another bug relating to inconsistent cluster 
state. I just retried and got a pop-up saying "Must be authorized to modify 
every component selected."


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/698
  
NIFI-2242 was when there are multiple components selected with mixed 
permissions so I think this may be a slightly different case but I'd be happy 
to address as part of this PR.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2242) UI does not render components properly if moving multiple components with mixed permissions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2242:
--

Github user JPercivall commented on the issue:

https://github.com/apache/nifi/pull/698
  
Doesn't seem to address NIFI-2242. I have write permission to GenerateFF 
but not LogAttribute. This UI mess up fixed itself after refresh.

https://cloud.githubusercontent.com/assets/11302527/17031083/768b0cb6-4f40-11e6-951b-d4a368533593.png;>



> UI does not render components properly if moving multiple components with 
> mixed permissions
> ---
>
> Key: NIFI-2242
> URL: https://issues.apache.org/jira/browse/NIFI-2242
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Mark Payne
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> I selected several processors and connections (a small, disconnected graph) 
> and dragged the components to the right. When I released, I got an error 
> message because I didn't have 'write' permissions to one of the processors. 
> All of the other processors moved, but he one processor did not. As a result, 
> the connections were also not refreshed properly and were not connecting the 
> components visually. Clicking 'refresh' on the graph did cause the 
> connections to be redrawn properly.
> This could be addressed in two different ways. First, we could simply refresh 
> the canvas in this case.
> Secondly, we could use a Flow Snippet to move the components, in which case 
> none of the components would be moved if the user attempted this action 
> because the user does not have sufficient permissions for all components.



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

[jira] [Commented] (NIFI-2344) non-required Controller services disabled on restart

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2344:
---

[~ozhurakousky] So are you working this?  Are you able to work it as a blocker?

> non-required Controller services disabled on restart
> 
>
> Key: NIFI-2344
> URL: https://issues.apache.org/jira/browse/NIFI-2344
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Brandon DeVries
>Assignee: Oleg Zhurakousky
>Priority: Blocker
>
> So... the problem from NIFI-2160 isn't quite dead yet.  The fix for that 
> ticket recursively enumerates controller services that a controller service 
> references, but only if they are *required*\[1\].  However, there are many 
> cases in which referenced controller services may not be required properties:
> [DistributedMapCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html]
>  - SSL Context Service
> [DistributedMapCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html]
>  - SSL Context Service
> [DistributedSetCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html]
>  - SSL Context Service
> [DistributedSetCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html]
>  - SSL Context Service
> [JMSConnectionFactoryProvider|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html]
>  - SSL Context Service
> This causes the above services to become disabled on restart if they were 
> previously enabled.  I'd propose changing the line:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && 
> descriptor.isRequired()) {
> {code}
> to:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && pEntry.getValue() 
> != null) {
> {code}
> \[1\] 
> https://github.com/apache/nifi/blob/rel/nifi-0.7.0/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceNode.java#L121



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

[jira] [Commented] (NIFI-2344) non-required Controller services disabled on restart

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2344:
---

I think in the case of a blocker it does make sense but in the case of a 
blocker like this let's go ahead and make a 0.7.1 tag and assign this to it.  
You'd not want to wait for the eventual 0.8 or 1.0 for example right?

So should we be talking 0.7.1 release and getting that going?

> non-required Controller services disabled on restart
> 
>
> Key: NIFI-2344
> URL: https://issues.apache.org/jira/browse/NIFI-2344
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Brandon DeVries
>Assignee: Oleg Zhurakousky
>Priority: Blocker
>
> So... the problem from NIFI-2160 isn't quite dead yet.  The fix for that 
> ticket recursively enumerates controller services that a controller service 
> references, but only if they are *required*\[1\].  However, there are many 
> cases in which referenced controller services may not be required properties:
> [DistributedMapCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html]
>  - SSL Context Service
> [DistributedMapCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html]
>  - SSL Context Service
> [DistributedSetCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html]
>  - SSL Context Service
> [DistributedSetCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html]
>  - SSL Context Service
> [JMSConnectionFactoryProvider|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html]
>  - SSL Context Service
> This causes the above services to become disabled on restart if they were 
> previously enabled.  I'd propose changing the line:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && 
> descriptor.isRequired()) {
> {code}
> to:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && pEntry.getValue() 
> != null) {
> {code}
> \[1\] 
> https://github.com/apache/nifi/blob/rel/nifi-0.7.0/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceNode.java#L121



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

[jira] [Updated] (NIFI-2344) non-required Controller services disabled on restart

[Brandon DeVries (JIRA)]

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

Brandon DeVries updated NIFI-2344:
--
Priority: Blocker  (was: Major)

> non-required Controller services disabled on restart
> 
>
> Key: NIFI-2344
> URL: https://issues.apache.org/jira/browse/NIFI-2344
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Brandon DeVries
>Assignee: Oleg Zhurakousky
>Priority: Blocker
>
> So... the problem from NIFI-2160 isn't quite dead yet.  The fix for that 
> ticket recursively enumerates controller services that a controller service 
> references, but only if they are *required*\[1\].  However, there are many 
> cases in which referenced controller services may not be required properties:
> [DistributedMapCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html]
>  - SSL Context Service
> [DistributedMapCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html]
>  - SSL Context Service
> [DistributedSetCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html]
>  - SSL Context Service
> [DistributedSetCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html]
>  - SSL Context Service
> [JMSConnectionFactoryProvider|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html]
>  - SSL Context Service
> This causes the above services to become disabled on restart if they were 
> previously enabled.  I'd propose changing the line:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && 
> descriptor.isRequired()) {
> {code}
> to:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && pEntry.getValue() 
> != null) {
> {code}
> \[1\] 
> https://github.com/apache/nifi/blob/rel/nifi-0.7.0/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceNode.java#L121



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

[jira] [Assigned] (NIFI-2050) Advanced button blends with cancel button

[Scott Aslan (JIRA)]

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

Scott Aslan reassigned NIFI-2050:
-

Assignee: Scott Aslan

> Advanced button blends with cancel button
> -
>
> Key: NIFI-2050
> URL: https://issues.apache.org/jira/browse/NIFI-2050
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.0.0
>
> Attachments: nifi-2050_advanced-button.png
>
>
> UpdateAttribute Processor > Configure Processor: advanced button blends in 
> with cancel button. Need UX...maybe make it a link...
> Also need to style the custom ui for the advanced dialog.



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

[jira] [Updated] (NIFI-2340) Incremental database processors should support incoming flow files and Expression Language

[Matt Burgess (JIRA)]

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

Matt Burgess updated NIFI-2340:
---
Summary: Incremental database processors should support incoming flow files 
and Expression Language  (was: Incremental database processors should support 
incoming flow files)

> Incremental database processors should support incoming flow files and 
> Expression Language
> --
>
> Key: NIFI-2340
> URL: https://issues.apache.org/jira/browse/NIFI-2340
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0, 0.7.0
>Reporter: Matt Burgess
>
> QueryDatabaseTable and GenerateTableFetch do not support incoming 
> connections, which makes them less flexible for accepting table names, such 
> as using Expression Language (EL) for names located in flow file attributes, 
> e.g.) The use of EL (to include custom properties and the Variable Registry) 
> will enable these processors to fetch arbitrary tables based on the provided 
> values.



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

[jira] [Commented] (NIFI-2344) non-required Controller services disabled on restart

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2344:
---

Removed Fix versions.  We need to assign those once we have work underway, and 
a patch coming or provided.  We're having issues on getting releases going 
because we're just tagging preferred fix versions but we need those to be 
powered by progress.  Please by all means do assign the fix version once this 
has been addressed or is in-progress and planned for a given release.

> non-required Controller services disabled on restart
> 
>
> Key: NIFI-2344
> URL: https://issues.apache.org/jira/browse/NIFI-2344
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Brandon DeVries
>Assignee: Oleg Zhurakousky
>
> So... the problem from NIFI-2160 isn't quite dead yet.  The fix for that 
> ticket recursively enumerates controller services that a controller service 
> references, but only if they are *required*\[1\].  However, there are many 
> cases in which referenced controller services may not be required properties:
> [DistributedMapCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html]
>  - SSL Context Service
> [DistributedMapCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html]
>  - SSL Context Service
> [DistributedSetCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html]
>  - SSL Context Service
> [DistributedSetCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html]
>  - SSL Context Service
> [JMSConnectionFactoryProvider|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html]
>  - SSL Context Service
> This causes the above services to become disabled on restart if they were 
> previously enabled.  I'd propose changing the line:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && 
> descriptor.isRequired()) {
> {code}
> to:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && pEntry.getValue() 
> != null) {
> {code}
> \[1\] 
> https://github.com/apache/nifi/blob/rel/nifi-0.7.0/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceNode.java#L121



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

[jira] [Updated] (NIFI-2344) non-required Controller services disabled on restart

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2344:
--
Fix Version/s: (was: 0.8.0)
   (was: 1.0.0)

> non-required Controller services disabled on restart
> 
>
> Key: NIFI-2344
> URL: https://issues.apache.org/jira/browse/NIFI-2344
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 0.7.0
>Reporter: Brandon DeVries
>Assignee: Oleg Zhurakousky
>
> So... the problem from NIFI-2160 isn't quite dead yet.  The fix for that 
> ticket recursively enumerates controller services that a controller service 
> references, but only if they are *required*\[1\].  However, there are many 
> cases in which referenced controller services may not be required properties:
> [DistributedMapCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedMapCacheClientService/index.html]
>  - SSL Context Service
> [DistributedMapCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html]
>  - SSL Context Service
> [DistributedSetCacheClientService|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.client.DistributedSetCacheClientService/index.html]
>  - SSL Context Service
> [DistributedSetCacheServer|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.distributed.cache.server.DistributedSetCacheServer/index.html]
>  - SSL Context Service
> [JMSConnectionFactoryProvider|http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.jms.cf.JMSConnectionFactoryProvider/index.html]
>  - SSL Context Service
> This causes the above services to become disabled on restart if they were 
> previously enabled.  I'd propose changing the line:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && 
> descriptor.isRequired()) {
> {code}
> to:
> {code}
> if (descriptor.getControllerServiceDefinition() != null && pEntry.getValue() 
> != null) {
> {code}
> \[1\] 
> https://github.com/apache/nifi/blob/rel/nifi-0.7.0/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/service/StandardControllerServiceNode.java#L121



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

[jira] [Commented] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[Joseph Witt (JIRA)]

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

Joseph Witt commented on NIFI-2320:
---

+1 Merged to master.  Left open though as it looks like more images will be 
coming.  Can you please confirm [~andrewmlim]?

> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[jira] [Commented] (NIFI-2211) Update NiFi architecture graphics for overview doc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2211:
--

Github user asfgit closed the pull request at:

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


> Update NiFi architecture graphics for overview doc
> --
>
> Key: NIFI-2211
> URL: https://issues.apache.org/jira/browse/NIFI-2211
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
> Attachments: zero-master-cluster.png, zero-master-node.png
>
>




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

[jira] [Updated] (NIFI-2320) Update screenshot images in Getting Started guide for 1.0

[Joseph Witt (JIRA)]

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

Joseph Witt updated NIFI-2320:
--
Status: Open  (was: Patch Available)

> Update screenshot images in Getting Started guide for 1.0
> -
>
> Key: NIFI-2320
> URL: https://issues.apache.org/jira/browse/NIFI-2320
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation & Website
>Affects Versions: 1.0.0
>Reporter: Andrew Lim
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
>
> The screenshots in the documentation need to be updated for the new UI.
> This ticket is for the images used or added to the Getting Started guide.



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

[GitHub] nifi pull request #691: NIFI-2320 Update existing Getting Starting images wi...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request #700: NIFI-2211 Updating NiFi architecture graphics for ov...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-2211) Update NiFi architecture graphics for overview doc

[Joseph Witt (JIRA)]

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

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

+1.  Merged to master.  Thanks!

> Update NiFi architecture graphics for overview doc
> --
>
> Key: NIFI-2211
> URL: https://issues.apache.org/jira/browse/NIFI-2211
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Documentation & Website
>Reporter: Rob Moran
>Assignee: Joseph Witt
> Fix For: 1.0.0
>
> Attachments: zero-master-cluster.png, zero-master-node.png
>
>




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

[GitHub] nifi issue #698: Updating the UI to reflect the access policies being enforc...

[JPercivall]

Github user JPercivall commented on the issue:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---