[jira] [Updated] (NIFI-3301) Nifi 1.1.1 – Data provenence visible but not click-able as expected

[James Wing (JIRA)]

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

James Wing updated NIFI-3301:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Nifi 1.1.1 – Data provenence visible but not click-able as expected
> ---
>
> Key: NIFI-3301
> URL: https://issues.apache.org/jira/browse/NIFI-3301
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.1.1
> Environment: Ubuntu 15.04
> openjdk version "1.8.0_45-internal"
> OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
>Reporter: Frank Thiele
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: lineage.svg, TransTemplate_2.xml
>
>
> I have downloaded the bin package and deployed a test flow in my Ubuntu
> system with Java 8. Given a file that has flown through the system, when
> opening the data provenence view of the last node (PutFTP), I cannot
> click on the nodes displayed and there is no hovering of data possible.
> But this was possible in version 0.6. I also tried Chromium instead of
> my Firefox but this doesn't help.
> What am I doing wrong?



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

[jira] [Commented] (NIFI-3301) Nifi 1.1.1 – Data provenence visible but not click-able as expected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3301:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1430
  
Thanks, @mcgilman , the update looks good.  I squashed and merged.


> Nifi 1.1.1 – Data provenence visible but not click-able as expected
> ---
>
> Key: NIFI-3301
> URL: https://issues.apache.org/jira/browse/NIFI-3301
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.1.1
> Environment: Ubuntu 15.04
> openjdk version "1.8.0_45-internal"
> OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
>Reporter: Frank Thiele
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: lineage.svg, TransTemplate_2.xml
>
>
> I have downloaded the bin package and deployed a test flow in my Ubuntu
> system with Java 8. Given a file that has flown through the system, when
> opening the data provenence view of the last node (PutFTP), I cannot
> click on the nodes displayed and there is no hovering of data possible.
> But this was possible in version 0.6. I also tried Chromium instead of
> my Firefox but this doesn't help.
> What am I doing wrong?



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

[GitHub] nifi issue #1430: NIFI-3301: Fix cursor style over event type text in lineag...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1430
  
Thanks, @mcgilman , the update looks good.  I squashed and merged.


---
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-3301) Nifi 1.1.1 – Data provenence visible but not click-able as expected

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3301: Provenance UI Cursor Styling
- Addressing inconsistent cursor styling and drag behavior in lineage graph.

This closes #1430.

Signed-off-by: James Wing 


> Nifi 1.1.1 – Data provenence visible but not click-able as expected
> ---
>
> Key: NIFI-3301
> URL: https://issues.apache.org/jira/browse/NIFI-3301
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.1.1
> Environment: Ubuntu 15.04
> openjdk version "1.8.0_45-internal"
> OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
>Reporter: Frank Thiele
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: lineage.svg, TransTemplate_2.xml
>
>
> I have downloaded the bin package and deployed a test flow in my Ubuntu
> system with Java 8. Given a file that has flown through the system, when
> opening the data provenence view of the last node (PutFTP), I cannot
> click on the nodes displayed and there is no hovering of data possible.
> But this was possible in version 0.6. I also tried Chromium instead of
> my Firefox but this doesn't help.
> What am I doing wrong?



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

[GitHub] nifi pull request #1430: NIFI-3301: Fix cursor style over event type text in...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-3301) Nifi 1.1.1 – Data provenence visible but not click-able as expected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3301:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1430
  
Good call. I had my setup to ignore whitespace following my rebase and I 
overlooked it. I'm pretty sure it's correct now but it still looks like some 
things are shifted because I moved a lot of the logic into a showContextMenu 
function instead of handling everything within the anonymous callback.


> Nifi 1.1.1 – Data provenence visible but not click-able as expected
> ---
>
> Key: NIFI-3301
> URL: https://issues.apache.org/jira/browse/NIFI-3301
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.1.1
> Environment: Ubuntu 15.04
> openjdk version "1.8.0_45-internal"
> OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
>Reporter: Frank Thiele
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: lineage.svg, TransTemplate_2.xml
>
>
> I have downloaded the bin package and deployed a test flow in my Ubuntu
> system with Java 8. Given a file that has flown through the system, when
> opening the data provenence view of the last node (PutFTP), I cannot
> click on the nodes displayed and there is no hovering of data possible.
> But this was possible in version 0.6. I also tried Chromium instead of
> my Firefox but this doesn't help.
> What am I doing wrong?



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

[GitHub] nifi issue #1430: NIFI-3301: Fix cursor style over event type text in lineag...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1430
  
Good call. I had my setup to ignore whitespace following my rebase and I 
overlooked it. I'm pretty sure it's correct now but it still looks like some 
things are shifted because I moved a lot of the logic into a showContextMenu 
function instead of handling everything within the anonymous callback.


---
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-3301) Nifi 1.1.1 – Data provenence visible but not click-able as expected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3301:
--

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1430
  
@mcgilman - Thank you for making this more elaborate fix, I like the way it 
both looks and works.  I have a question about the code diffs, though, it looks 
like there is a lot of whitespace-only indentation change between lines ~546 
and ~1034 of `nf-provenance-lineage.js`.  Is that intentional and desired?


> Nifi 1.1.1 – Data provenence visible but not click-able as expected
> ---
>
> Key: NIFI-3301
> URL: https://issues.apache.org/jira/browse/NIFI-3301
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.1.1
> Environment: Ubuntu 15.04
> openjdk version "1.8.0_45-internal"
> OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
>Reporter: Frank Thiele
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: lineage.svg, TransTemplate_2.xml
>
>
> I have downloaded the bin package and deployed a test flow in my Ubuntu
> system with Java 8. Given a file that has flown through the system, when
> opening the data provenence view of the last node (PutFTP), I cannot
> click on the nodes displayed and there is no hovering of data possible.
> But this was possible in version 0.6. I also tried Chromium instead of
> my Firefox but this doesn't help.
> What am I doing wrong?



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

[GitHub] nifi issue #1430: NIFI-3301: Fix cursor style over event type text in lineag...

[jvwing]

Github user jvwing commented on the issue:

https://github.com/apache/nifi/pull/1430
  
@mcgilman - Thank you for making this more elaborate fix, I like the way it 
both looks and works.  I have a question about the code diffs, though, it looks 
like there is a lot of whitespace-only indentation change between lines ~546 
and ~1034 of `nf-provenance-lineage.js`.  Is that intentional and desired?


---
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-2961) Create EncryptAttribute processor

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-2961:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1294
  
I am currently making some commits to this PR (on a local branch which I 
will post later) to resolve some of the issues recently encountered:

* Improper access scope of property fields
* Unit tests incorrectly modified to reference raw `name` instead of 
`displayName` in validation error messages
* `Public Keyring` property pointed at `Private Keyring`
* Incorrectly reverted default KDF from `Bcrypt` to `Legacy KDF` 
(deprecated)

As this touches sensitive code within the application (not only does it add 
a new processor which users will trust to encrypt sensitive attributes, but it 
also rewrites `EncryptContent` which is already widely-used in production 
systems), we need to be very careful that regression tests are passing, the 
cryptographic code is correct and safe, and we follow the principle of least 
surprise for users. 


> Create EncryptAttribute processor
> -
>
> Key: NIFI-2961
> URL: https://issues.apache.org/jira/browse/NIFI-2961
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Affects Versions: 1.0.0
>Reporter: Andy LoPresto
>  Labels: attributes, encryption, security
>
> Similar to {{EncryptContent}}, the {{EncryptAttribute}} processor would allow 
> individual (and multiple) flowfile attributes to be encrypted (either 
> in-place or to a new attribute key) with various encryption algorithms (AES, 
> RSA, PBE, and PGP). 
> Specific compatibility with the {{OpenSSL EVP_BytesToKey}}, {{PBKDF2}}, 
> {{scrypt}}, and {{bcrypt}} key derivation functions should be included. 
> The processor should provide the boolean option to encrypt or decrypt (only 
> one operation per instance of the processor). The processor should also allow 
> Base64 encoding (aka ASCII armor) for the encrypted attributes to prevent 
> byte escaping/data loss. 
> If [dangerous processor 
> annotations|https://cwiki.apache.org/confluence/display/NIFI/Security+Feature+Roadmap]
>  are introduced, this processor should be marked as such and the 
> corresponding attribute protection (i.e. provenance before/after, etc.) 
> should be applied. 
> Originally requested in this [Stack Overflow 
> question|https://stackoverflow.com/questions/40294945/nifi-encrypt-json].  



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

[GitHub] nifi issue #1294: NIFI-2961 Create EncryptAttribute processor

[alopresto]

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1294
  
I am currently making some commits to this PR (on a local branch which I 
will post later) to resolve some of the issues recently encountered:

* Improper access scope of property fields
* Unit tests incorrectly modified to reference raw `name` instead of 
`displayName` in validation error messages
* `Public Keyring` property pointed at `Private Keyring`
* Incorrectly reverted default KDF from `Bcrypt` to `Legacy KDF` 
(deprecated)

As this touches sensitive code within the application (not only does it add 
a new processor which users will trust to encrypt sensitive attributes, but it 
also rewrites `EncryptContent` which is already widely-used in production 
systems), we need to be very careful that regression tests are passing, the 
cryptographic code is correct and safe, and we follow the principle of least 
surprise for users. 


---
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-3381) Update NAR Maven Plugin to include version information

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-3381:
--
Status: Patch Available  (was: Open)

> Update NAR Maven Plugin to include version information
> --
>
> Key: NIFI-3381
> URL: https://issues.apache.org/jira/browse/NIFI-3381
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: NIFI-3381.patch
>
>
> In support of running multiple versions of the same component, NiFi needs to 
> know the version of a NAR that the component came from. This ticket is to 
> update the NAR Maven Plugin to add additional information to the MANIFEST 
> file to support this effort.
> Further information is described here:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension



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

[jira] [Updated] (NIFI-3381) Update NAR Maven Plugin to include version information

[Bryan Bende (JIRA)]

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

Bryan Bende updated NIFI-3381:
--
Attachment: NIFI-3381.patch

> Update NAR Maven Plugin to include version information
> --
>
> Key: NIFI-3381
> URL: https://issues.apache.org/jira/browse/NIFI-3381
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: NIFI-3381.patch
>
>
> In support of running multiple versions of the same component, NiFi needs to 
> know the version of a NAR that the component came from. This ticket is to 
> update the NAR Maven Plugin to add additional information to the MANIFEST 
> file to support this effort.
> Further information is described here:
> https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension



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

[jira] [Comment Edited] (NIFI-3350) Reduce NiFi startup time by streamlining documentation extraction

[James Wing (JIRA)]

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

James Wing edited comment on NIFI-3350 at 1/20/17 10:03 PM:


[~mosermw], how would you describe your test methodology for that speed 
improvement?  I have not experienced the same improvement yet.  I tried this 
out two ways:

1. Local Machine - where I clear out all of the repository and working 
directories prior to running NiFi before each trial.
2. Docker - with a Docker container that boots up a fresh OS with the NiFi 
source for each run, so no directories are preserved.

How does that compare with what you are doing?

!nifi-3350-doc-optimization-results-1.png!


was (Author: jameswing):
[~mosermw], how would you describe your test methodology for that speed 
improvement?  I have not experienced the same improvement yet.  I tried this 
out two ways:

1. Local Machine - where I clear out all of the repository and working 
directories prior to running NiFi before each trial.
1. Docker - with a Docker container that boots up a fresh OS with the NiFi 
source for each run, so no directories are preserved.

How does that compare with what you are doing?

!nifi-3350-doc-optimization-results-1.png!

> Reduce NiFi startup time by streamlining documentation extraction
> -
>
> Key: NIFI-3350
> URL: https://issues.apache.org/jira/browse/NIFI-3350
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.1, 1.1.1
>Reporter: Michael Moser
>Assignee: Michael Moser
> Attachments: nifi-3350-doc-optimization-results-1.png
>
>
> On NiFi startup, after seeing the new log message added in NIFI-3164, I 
> noticed that generating documentation of all components takes a long time.  
> After reading the NarUnpacker code, it appears to scan every file in every 
> jar for NiFi component documentation.  I think there are some optimizations 
> we can do here  which should reduce NiFi startup time.



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

[jira] [Commented] (NIFI-3350) Reduce NiFi startup time by streamlining documentation extraction

[James Wing (JIRA)]

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

James Wing commented on NIFI-3350:
--

[~mosermw], how would you describe your test methodology for that speed 
improvement?  I have not experienced the same improvement yet.  I tried this 
out two ways:

1. Local Machine - where I clear out all of the repository and working 
directories prior to running NiFi before each trial.
1. Docker - with a Docker container that boots up a fresh OS with the NiFi 
source for each run, so no directories are preserved.

How does that compare with what you are doing?

!nifi-3350-doc-optimization-results-1.png!

> Reduce NiFi startup time by streamlining documentation extraction
> -
>
> Key: NIFI-3350
> URL: https://issues.apache.org/jira/browse/NIFI-3350
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.1, 1.1.1
>Reporter: Michael Moser
>Assignee: Michael Moser
> Attachments: nifi-3350-doc-optimization-results-1.png
>
>
> On NiFi startup, after seeing the new log message added in NIFI-3164, I 
> noticed that generating documentation of all components takes a long time.  
> After reading the NarUnpacker code, it appears to scan every file in every 
> jar for NiFi component documentation.  I think there are some optimizations 
> we can do here  which should reduce NiFi startup time.



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

[jira] [Updated] (NIFI-3350) Reduce NiFi startup time by streamlining documentation extraction

[James Wing (JIRA)]

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

James Wing updated NIFI-3350:
-
Attachment: nifi-3350-doc-optimization-results-1.png

> Reduce NiFi startup time by streamlining documentation extraction
> -
>
> Key: NIFI-3350
> URL: https://issues.apache.org/jira/browse/NIFI-3350
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.1, 1.1.1
>Reporter: Michael Moser
>Assignee: Michael Moser
> Attachments: nifi-3350-doc-optimization-results-1.png
>
>
> On NiFi startup, after seeing the new log message added in NIFI-3164, I 
> noticed that generating documentation of all components takes a long time.  
> After reading the NarUnpacker code, it appears to scan every file in every 
> jar for NiFi component documentation.  I think there are some optimizations 
> we can do here  which should reduce NiFi startup time.



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

[jira] [Commented] (NIFI-3301) Nifi 1.1.1 – Data provenence visible but not click-able as expected

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3301:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1430
  
I just pushed an update making the suggested changes. Thanks again!


> Nifi 1.1.1 – Data provenence visible but not click-able as expected
> ---
>
> Key: NIFI-3301
> URL: https://issues.apache.org/jira/browse/NIFI-3301
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Affects Versions: 1.1.1
> Environment: Ubuntu 15.04
> openjdk version "1.8.0_45-internal"
> OpenJDK Runtime Environment (build 1.8.0_45-internal-b14)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
>Reporter: Frank Thiele
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.2.0
>
> Attachments: lineage.svg, TransTemplate_2.xml
>
>
> I have downloaded the bin package and deployed a test flow in my Ubuntu
> system with Java 8. Given a file that has flown through the system, when
> opening the data provenence view of the last node (PutFTP), I cannot
> click on the nodes displayed and there is no hovering of data possible.
> But this was possible in version 0.6. I also tried Chromium instead of
> my Firefox but this doesn't help.
> What am I doing wrong?



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

[GitHub] nifi issue #1430: NIFI-3301: Fix cursor style over event type text in lineag...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1430
  
I just pushed an update making the suggested changes. Thanks again!


---
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] [Resolved] (NIFI-3359) Modularize all of nifi-web-ui except canvas directory

[Matt Gilman (JIRA)]

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

Matt Gilman resolved NIFI-3359.
---
   Resolution: Fixed
Fix Version/s: 1.2.0

> Modularize all of nifi-web-ui except canvas directory
> -
>
> Key: NIFI-3359
> URL: https://issues.apache.org/jira/browse/NIFI-3359
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
>
> Need to modularize (re-package) UI components to promote maintainability and 
> eventual reusability for UI extensions. Components are already conceptually 
> modular however circular references exists which should not be allowed. Need 
> to re-package functions to eliminate circular
> references.



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

[GitHub] nifi issue #1428: [NIFI-3359] Modularize all of nifi-web-ui except canvas di...

[mcgilman]

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1428
  
Thanks @scottyaslan! This has been merged to master.


---
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-3359) Modularize all of nifi-web-ui except canvas directory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3359:
--

Github user asfgit closed the pull request at:

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


> Modularize all of nifi-web-ui except canvas directory
> -
>
> Key: NIFI-3359
> URL: https://issues.apache.org/jira/browse/NIFI-3359
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
>
> Need to modularize (re-package) UI components to promote maintainability and 
> eventual reusability for UI extensions. Components are already conceptually 
> modular however circular references exists which should not be allowed. Need 
> to re-package functions to eliminate circular
> references.



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

[jira] [Commented] (NIFI-3359) Modularize all of nifi-web-ui except canvas directory

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3359:
--

Github user mcgilman commented on the issue:

https://github.com/apache/nifi/pull/1428
  
Thanks @scottyaslan! This has been merged to master.


> Modularize all of nifi-web-ui except canvas directory
> -
>
> Key: NIFI-3359
> URL: https://issues.apache.org/jira/browse/NIFI-3359
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
>
> Need to modularize (re-package) UI components to promote maintainability and 
> eventual reusability for UI extensions. Components are already conceptually 
> modular however circular references exists which should not be allowed. Need 
> to re-package functions to eliminate circular
> references.



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

[jira] [Commented] (NIFI-3359) Modularize all of nifi-web-ui except canvas directory

[ASF subversion and git services (JIRA)]

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

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

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

[NIFI-3359] Modularize all of nifi-web-ui except canvas directory
- Removing shell.jsp from summary.jsp.
- This closes #1428


> Modularize all of nifi-web-ui except canvas directory
> -
>
> Key: NIFI-3359
> URL: https://issues.apache.org/jira/browse/NIFI-3359
> Project: Apache NiFi
>  Issue Type: Sub-task
>  Components: Core UI
>Reporter: Scott Aslan
>Assignee: Scott Aslan
> Fix For: 1.2.0
>
>
> Need to modularize (re-package) UI components to promote maintainability and 
> eventual reusability for UI extensions. Components are already conceptually 
> modular however circular references exists which should not be allowed. Need 
> to re-package functions to eliminate circular
> references.



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

[jira] [Created] (NIFI-3381) Update NAR Maven Plugin to include version information

[Bryan Bende (JIRA)]

Bryan Bende created NIFI-3381:
-

 Summary: Update NAR Maven Plugin to include version information
 Key: NIFI-3381
 URL: https://issues.apache.org/jira/browse/NIFI-3381
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Bryan Bende
Assignee: Bryan Bende
Priority: Minor
 Fix For: 1.2.0


In support of running multiple versions of the same component, NiFi needs to 
know the version of a NAR that the component came from. This ticket is to 
update the NAR Maven Plugin to add additional information to the MANIFEST file 
to support this effort.

Further information is described here:
https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension



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

[jira] [Created] (NIFI-3380) Multiple Versions of the Same Component

[Bryan Bende (JIRA)]

Bryan Bende created NIFI-3380:
-

 Summary: Multiple Versions of the Same Component
 Key: NIFI-3380
 URL: https://issues.apache.org/jira/browse/NIFI-3380
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Core Framework
Reporter: Bryan Bende
Assignee: Bryan Bende
 Fix For: 1.2.0


This ticket is to track the work for supporting multiple versions of the same 
component within NiFi. The overall design for this feature is described in 
detail at the following wiki page:

https://cwiki.apache.org/confluence/display/NIFI/Multiple+Versions+of+the+Same+Extension

This ticket will track only the core NiFi work, and a separate ticket will be 
created to track enhancements for the NAR Maven Plugin.



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

[jira] [Commented] (NIFI-1796) Create the 'Hello World' example of custom processor development

[Andrew Lim (JIRA)]

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

Andrew Lim commented on NIFI-1796:
--

This doesn't help solve the core issue of this ticket, but related to the 
documentation comments, I filed 
https://issues.apache.org/jira/browse/NIFI-3345.  Basically, since the 
processor list is so long now, we could make the left nav sections of the doc 
collapsible so areas like the Developer Guide are no longer obscured.

> Create the 'Hello World' example of custom processor development
> 
>
> Key: NIFI-1796
> URL: https://issues.apache.org/jira/browse/NIFI-1796
> Project: Apache NiFi
>  Issue Type: Task
>  Components: Documentation & Website
>Reporter: Joseph Witt
>Assignee: Oleg Zhurakousky
>
> We really need to create a simple guide for how to build custom processor in 
> nifi.  The sort of 'hello world' example.
> This was created due to finding it hard to give a nice simple short pointer 
> for a question on the mailing list.
> We do have a solid developer guide here [1] that goes into the key concepts 
> and processor development a bit.  The next best thing is to use the supplied 
> maven archetype to lay down the fundamental pieces.  You can read a bit more 
> about that here [2].  Finally something that is also quite helpful is looking 
> at the standard processors to see if anything follows the pattern/problem you 
> had in mind and which can serve as a good basis [3]
> [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html
> [2] 
> https://richardstechnotes.wordpress.com/2015/12/06/setting-up-for-custom-nifi-processor-development/
> [3] 
> https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard



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

[jira] [Commented] (NIFI-3350) Reduce NiFi startup time by streamlining documentation extraction

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3350:
--

Github user jvwing commented on the issue:

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


> Reduce NiFi startup time by streamlining documentation extraction
> -
>
> Key: NIFI-3350
> URL: https://issues.apache.org/jira/browse/NIFI-3350
> Project: Apache NiFi
>  Issue Type: Improvement
>Affects Versions: 0.7.1, 1.1.1
>Reporter: Michael Moser
>Assignee: Michael Moser
>
> On NiFi startup, after seeing the new log message added in NIFI-3164, I 
> noticed that generating documentation of all components takes a long time.  
> After reading the NarUnpacker code, it appears to scan every file in every 
> jar for NiFi component documentation.  I think there are some optimizations 
> we can do here  which should reduce NiFi startup time.



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

[GitHub] nifi issue #1416: NIFI-3350 optimized documentation extraction to reduce sta...

[jvwing]

Github user jvwing commented on the issue:

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

[GitHub] nifi issue #379: NIFI-1022 Added Tachyon/Alluxio processors

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/379
  
no rush!  was just trying to revisit items in the queue


---
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-1022) Create GetTachyon and PutTachyon Processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1022:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/379
  
no rush!  was just trying to revisit items in the queue


> Create GetTachyon and PutTachyon Processors
> ---
>
> Key: NIFI-1022
> URL: https://issues.apache.org/jira/browse/NIFI-1022
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Jeremy Dyer
>Assignee: Pierre Villard
>Priority: Minor
> Attachments: Alluxio.xml
>
>
> Provide support for Apache Tachyon by implementing a GetTachyon and 
> PutTachyon processor. Having the ability to both read and write to Tachyon 
> would assist in sharing data with external applications such as Spark.



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

[jira] [Commented] (NIFI-1022) Create GetTachyon and PutTachyon Processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1022:
--

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/379
  
Hey @apiri, yes Alluxio guys informed me about this, I'll try to update the 
PR asap. Will let you know when it's done.


> Create GetTachyon and PutTachyon Processors
> ---
>
> Key: NIFI-1022
> URL: https://issues.apache.org/jira/browse/NIFI-1022
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Jeremy Dyer
>Assignee: Pierre Villard
>Priority: Minor
> Attachments: Alluxio.xml
>
>
> Provide support for Apache Tachyon by implementing a GetTachyon and 
> PutTachyon processor. Having the ability to both read and write to Tachyon 
> would assist in sharing data with external applications such as Spark.



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

[GitHub] nifi issue #379: NIFI-1022 Added Tachyon/Alluxio processors

[pvillard31]

Github user pvillard31 commented on the issue:

https://github.com/apache/nifi/pull/379
  
Hey @apiri, yes Alluxio guys informed me about this, I'll try to update the 
PR asap. Will let you know when it's done.


---
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-1022) Create GetTachyon and PutTachyon Processors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-1022:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/379
  
@pvillard31 I saw that the referenced ticket seems to now be resolved.  Not 
sure if this was still of interest, but if so would be happy to revisit upon 
updating.


> Create GetTachyon and PutTachyon Processors
> ---
>
> Key: NIFI-1022
> URL: https://issues.apache.org/jira/browse/NIFI-1022
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Jeremy Dyer
>Assignee: Pierre Villard
>Priority: Minor
> Attachments: Alluxio.xml
>
>
> Provide support for Apache Tachyon by implementing a GetTachyon and 
> PutTachyon processor. Having the ability to both read and write to Tachyon 
> would assist in sharing data with external applications such as Spark.



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

[GitHub] nifi issue #379: NIFI-1022 Added Tachyon/Alluxio processors

[apiri]

Github user apiri commented on the issue:

https://github.com/apache/nifi/pull/379
  
@pvillard31 I saw that the referenced ticket seems to now be resolved.  Not 
sure if this was still of interest, but if so would be happy to revisit upon 
updating.


---
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] [Resolved] (NIFI-3158) ZooKeeper Migrator should be better about cleaning up resources and throw more specific exceptions

[Bryan Rosander (JIRA)]

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

Bryan Rosander resolved NIFI-3158.
--
Resolution: Fixed

> ZooKeeper Migrator should be better about cleaning up resources and throw 
> more specific exceptions
> --
>
> Key: NIFI-3158
> URL: https://issues.apache.org/jira/browse/NIFI-3158
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Minor
>
> ZooKeeper Migrator should close input/output streams and the ZK client when 
> it's finished using them.  Also, IOExceptions should be used in most places 
> that currently throw RuntimeException.



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

[jira] [Commented] (NIFI-3158) ZooKeeper Migrator should be better about cleaning up resources and throw more specific exceptions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3158:
--

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/1427
  
+1 Merged


> ZooKeeper Migrator should be better about cleaning up resources and throw 
> more specific exceptions
> --
>
> Key: NIFI-3158
> URL: https://issues.apache.org/jira/browse/NIFI-3158
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Minor
>
> ZooKeeper Migrator should close input/output streams and the ZK client when 
> it's finished using them.  Also, IOExceptions should be used in most places 
> that currently throw RuntimeException.



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

[jira] [Commented] (NIFI-3158) ZooKeeper Migrator should be better about cleaning up resources and throw more specific exceptions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3158:
--

Github user asfgit closed the pull request at:

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


> ZooKeeper Migrator should be better about cleaning up resources and throw 
> more specific exceptions
> --
>
> Key: NIFI-3158
> URL: https://issues.apache.org/jira/browse/NIFI-3158
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Minor
>
> ZooKeeper Migrator should close input/output streams and the ZK client when 
> it's finished using them.  Also, IOExceptions should be used in most places 
> that currently throw RuntimeException.



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

[GitHub] nifi pull request #1427: NIFI-3158 Added cleanup of resources and refactored...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #1427: NIFI-3158 Added cleanup of resources and refactored except...

[brosander]

Github user brosander commented on the issue:

https://github.com/apache/nifi/pull/1427
  
+1 Merged


---
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-3158) ZooKeeper Migrator should be better about cleaning up resources and throw more specific exceptions

[ASF subversion and git services (JIRA)]

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

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

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

NIFI-3158 Added cleanup of resources and refactored exception handling

This closes #1427.

Signed-off-by: Bryan Rosander 


> ZooKeeper Migrator should be better about cleaning up resources and throw 
> more specific exceptions
> --
>
> Key: NIFI-3158
> URL: https://issues.apache.org/jira/browse/NIFI-3158
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Affects Versions: 1.1.0
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Minor
>
> ZooKeeper Migrator should close input/output streams and the ZK client when 
> it's finished using them.  Also, IOExceptions should be used in most places 
> that currently throw RuntimeException.



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

[jira] [Commented] (NIFI-3260) Official Docker Image

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3260:
--

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

https://github.com/apache/nifi/pull/1372#discussion_r97082483
  
--- Diff: nifi-docker/1.1.1/DockerRun.sh ---
@@ -0,0 +1,3 @@
+#!/bin/bash
+DOCKER_IMAGE="$(cat DockerImage.txt)"
+docker run -it -d -p 8080:8080 -p 8181:8181 $DOCKER_IMAGE
--- End diff --

The port mapping should also be present when a given container is started 
again


> Official Docker Image
> -
>
> Key: NIFI-3260
> URL: https://issues.apache.org/jira/browse/NIFI-3260
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
>  Labels: docker
> Fix For: 1.2.0
>
>
> This JIRA is for setting up a Docker folder structure within the NiFi source 
> code as discussed in the dev mailing list at
> https://lists.apache.org/thread.html/e905a559cb01b30f1a7032cec5c9605685f27a65bdf7fee41b735089@%3Cdev.nifi.apache.org%3E



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

[GitHub] nifi pull request #1372: NIFI-3260 Official Docker Image

[apiri]

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

https://github.com/apache/nifi/pull/1372#discussion_r97082483
  
--- Diff: nifi-docker/1.1.1/DockerRun.sh ---
@@ -0,0 +1,3 @@
+#!/bin/bash
+DOCKER_IMAGE="$(cat DockerImage.txt)"
+docker run -it -d -p 8080:8080 -p 8181:8181 $DOCKER_IMAGE
--- End diff --

The port mapping should also be present when a given container is started 
again


---
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-3260) Official Docker Image

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on NIFI-3260:
--

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

https://github.com/apache/nifi/pull/1372#discussion_r96966952
  
--- Diff: nifi-docker/1.1.1/DockerRun.sh ---
@@ -0,0 +1,3 @@
+#!/bin/bash
+DOCKER_IMAGE="$(cat DockerImage.txt)"
+docker run -it -d -p 8080:8080 -p 8181:8181 $DOCKER_IMAGE
--- End diff --

Do we have to execute following command every time we want to start nifi 
docker instance?
 docker run -it -d -p 8080:8080 -p 8181:8181 $DOCKER_IMAGE 

or once docker container is created, we can do docker stop and docker start.
i am trying that with my docker container. It works well with docker run. 
but it does work well with docker stop and docker start.

Can you try that?


> Official Docker Image
> -
>
> Key: NIFI-3260
> URL: https://issues.apache.org/jira/browse/NIFI-3260
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Tools and Build
>Reporter: Jeremy Dyer
>Assignee: Jeremy Dyer
>  Labels: docker
> Fix For: 1.2.0
>
>
> This JIRA is for setting up a Docker folder structure within the NiFi source 
> code as discussed in the dev mailing list at
> https://lists.apache.org/thread.html/e905a559cb01b30f1a7032cec5c9605685f27a65bdf7fee41b735089@%3Cdev.nifi.apache.org%3E



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

[GitHub] nifi pull request #1372: NIFI-3260 Official Docker Image

[gauravgoyal86]

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

https://github.com/apache/nifi/pull/1372#discussion_r96966952
  
--- Diff: nifi-docker/1.1.1/DockerRun.sh ---
@@ -0,0 +1,3 @@
+#!/bin/bash
+DOCKER_IMAGE="$(cat DockerImage.txt)"
+docker run -it -d -p 8080:8080 -p 8181:8181 $DOCKER_IMAGE
--- End diff --

Do we have to execute following command every time we want to start nifi 
docker instance?
 docker run -it -d -p 8080:8080 -p 8181:8181 $DOCKER_IMAGE 

or once docker container is created, we can do docker stop and docker start.
i am trying that with my docker container. It works well with docker run. 
but it does work well with docker stop and docker start.

Can you try that?


---
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] [Resolved] (NIFI-3379) ListHDFS has no File Filter Regex

[Pierre Villard (JIRA)]

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

Pierre Villard resolved NIFI-3379.
--
Resolution: Duplicate
  Assignee: Pierre Villard

The pull request for NIFI-2859 implements a file regex in ListHDFS processor. 
Once the PR will be reviewed and merged, the feature will be available in NiFi.

> ListHDFS has no File Filter Regex
> -
>
> Key: NIFI-3379
> URL: https://issues.apache.org/jira/browse/NIFI-3379
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Jan Verbeeck
>Assignee: Pierre Villard
>Priority: Minor
>
> ListHDFS is missing 'File Filter Regex'. Look at listSFTP for the correct 
> behaviour.



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

[jira] [Created] (NIFI-3379) ListHDFS has no File Filter Regex

[Jan Verbeeck (JIRA)]

Jan Verbeeck created NIFI-3379:
--

 Summary: ListHDFS has no File Filter Regex
 Key: NIFI-3379
 URL: https://issues.apache.org/jira/browse/NIFI-3379
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Jan Verbeeck
Priority: Minor


ListHDFS is missing 'File Filter Regex'. Look at listSFTP for the correct 
behaviour.



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