[jira] [Commented] (NIFI-3260) Official Docker Image
[ https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945217#comment-15945217 ] Aldrin Piri commented on NIFI-3260: --- [~joewitt] If this is the last thing holding up our release, we certainly can, otherwise, I would heavily prefer not to. Given the nature of all the infrastructure outside of our control and the ASF release processes, we have limited attempts to get the image built through official Apache channels. I have a ticket into INFRA (linked). While it would give us a lot more flexibility, I don't particularly wish to have a separate repo, vote, and release process for just Dockerfiles. Let me know your thoughts. > 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: Aldrin Piri > 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.15#6346)
[jira] [Commented] (NIFI-3440) Test failure on Win10 for FileSystemRepository/content repo
[ https://issues.apache.org/jira/browse/NIFI-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945549#comment-15945549 ] Aldrin Piri commented on NIFI-3440: --- I believe Appveyor has been fairly consistently showing this behavior as well. May be worthwhile rolling your patch into a PR to make use of that process as another data point. > Test failure on Win10 for FileSystemRepository/content repo > --- > > Key: NIFI-3440 > URL: https://issues.apache.org/jira/browse/NIFI-3440 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.2.0 > Environment: Windows10 >Reporter: Joseph Witt > Fix For: 1.2.0 > > Attachments: > 0001-NIFI-3440-Added-retry-logic-when-trying-to-delete-ne.patch, > 0001-NIFI-3440-Use-File-I-O-API-instead-of-NIO-API-for-de.patch > > > Running org.apache.nifi.controller.repository.io.TestLimitedInputStream > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in > org.apache.nifi.controller.repository.io.Test > LimitedInputStream > Running org.apache.nifi.controller.repository.TestFileSystemRepository > Tests run: 31, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 28.698 sec > <<< FAILURE! - in org.apache.nifi.controller > .repository.TestFileSystemRepository > testReadWithContentArchived(org.apache.nifi.controller.repository.TestFileSystemRepository) > Time elapsed: 0.596 sec << > < ERROR! > java.nio.file.FileSystemException: > C:\Users\nifi\nifi.git\nifi-nar-bundles\nifi-framework-bundle\nifi-framework\nifi-fra > mework-core\target\content_repository\1\1486264479123-1: The process cannot > access the file because it is being used by > another process. > at > sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86) > at > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) > at > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) > at > sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269) > at > sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) > at java.nio.file.Files.deleteIfExists(Files.java:1165) > at > org.apache.nifi.controller.repository.TestFileSystemRepository.testReadWithContentArchived(TestFileSystemRepo > sitory.java:408) > testReadWithNoContentArchived(org.apache.nifi.controller.repository.TestFileSystemRepository) > Time elapsed: 0.621 sec > <<< ERROR! > java.lang.Exception: Unexpected exception, > expected but > was > at > sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86) > at > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) > at > sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) > at > sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:269) > at > sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) > at java.nio.file.Files.deleteIfExists(Files.java:1165) > at > org.apache.nifi.controller.repository.TestFileSystemRepository.testReadWithNoContentArchived(TestFileSystemRe > pository.java:429) > Running org.apache.nifi.controller.repository.TestRingBufferEventRepository > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec - > in org.apache.nifi.controller.repository.Tes > tRingBufferEventRepository > Running org.apache.nifi.controller.repository.TestStandardProcessSession > [~markap14] isnt this something you've addressed before perhaps in another > test? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3440) Test failure on Win10 for FileSystemRepository/content repo
[
https://issues.apache.org/jira/browse/NIFI-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945641#comment-15945641
]
Aldrin Piri commented on NIFI-3440:
---
[~markap14] Applied your patches and pushed off to a branch in my personal
fork. Looks like similar results in that scenario as well:
{code}
---
T E S T S
---
Running org.apache.nifi.cluster.HeartbeatPayloadTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.266 sec - in
org.apache.nifi.cluster.HeartbeatPayloadTest
Running org.apache.nifi.cluster.ZooKeeperClientConfigTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.172 sec - in
org.apache.nifi.cluster.ZooKeeperClientConfigTest
Running org.apache.nifi.controller.PositionScalerSpec
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.5 sec - in
org.apache.nifi.controller.PositionScalerSpec
Running org.apache.nifi.controller.repository.claim.TestContentClaimWriteCache
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.234 sec - in
org.apache.nifi.controller.repository.claim.TestContentClaimWriteCache
Running
org.apache.nifi.controller.repository.claim.TestStandardResourceClaimManager
Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 sec - in
org.apache.nifi.controller.repository.claim.TestStandardResourceClaimManager
Running org.apache.nifi.controller.repository.io.TestLimitedInputStream
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec - in
org.apache.nifi.controller.repository.io.TestLimitedInputStream
Running org.apache.nifi.controller.repository.SchemaRepositoryRecordSerdeTest
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.312 sec - in
org.apache.nifi.controller.repository.SchemaRepositoryRecordSerdeTest
Running org.apache.nifi.controller.repository.TestFileSystemRepository
Tests run: 32, Failures: 1, Errors: 1, Skipped: 1, Time elapsed: 18.195 sec <<<
FAILURE! - in org.apache.nifi.controller.repository.TestFileSystemRepository
testReadWithContentArchived(org.apache.nifi.controller.repository.TestFileSystemRepository)
Time elapsed: 0.797 sec <<< FAILURE!
java.lang.AssertionError: Failed to delete
C:\projects\incubator-nifi\nifi-nar-bundles\nifi-framework-bundle\nifi-framework\nifi-framework-core\target\content_repository\1\1490724127784-1
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
org.apache.nifi.controller.repository.TestFileSystemRepository.testReadWithContentArchived(TestFileSystemRepository.java:449)
testReadWithNoContentArchived(org.apache.nifi.controller.repository.TestFileSystemRepository)
Time elapsed: 0.831 sec <<< ERROR!
java.lang.Exception: Unexpected exception,
expected but
was
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
org.apache.nifi.controller.repository.TestFileSystemRepository.testReadWithNoContentArchived(TestFileSystemRepository.java:478)
{code}
You can scope out the log @
https://ci.appveyor.com/project/apiri/incubator-nifi/build/1.0.0-SNAPSHOT-2
This is for Windows Server 2k12 as per
https://github.com/apiri/incubator-nifi/blob/3440/appveyor.yml
> Test failure on Win10 for FileSystemRepository/content repo
> ---
>
> Key: NIFI-3440
> URL: https://issues.apache.org/jira/browse/NIFI-3440
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.2.0
> Environment: Windows10
>Reporter: Joseph Witt
> Fix For: 1.2.0
>
> Attachments:
> 0001-NIFI-3440-Added-retry-logic-when-trying-to-delete-ne.patch,
> 0001-NIFI-3440-Use-File-I-O-API-instead-of-NIO-API-for-de.patch
>
>
> Running org.apache.nifi.controller.repository.io.TestLimitedInputStream
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in
> org.apache.nifi.controller.repository.io.Test
> LimitedInputStream
> Running org.apache.nifi.controller.repository.TestFileSystemRepository
> Tests run: 31, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 28.698 sec
> <<< FAILURE! - in org.apache.nifi.controller
> .repository.TestFileSystemRepository
> testReadWithContentArchived(org.apache.nifi.controller.repository.TestFileSystemRepository)
> Time elapsed: 0.596 sec <<
> < ERROR!
> java.nio.file.FileSystemException:
> C:\Users\nifi\nifi.git\nifi-nar-bundles\nifi-framework-bundle\nifi-framework\nifi-fra
> mework-core\target\content_repository\1\1486264479123-1: The process cannot
> access the file because it is being used by
> another process.
> at
> sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:86)
> at
> sun.nio.fs.WindowsExce
[jira] [Updated] (NIFI-3650) Ensure travis-ci won't cache nifi artifacts
[ https://issues.apache.org/jira/browse/NIFI-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3650: -- Fix Version/s: 1.2.0 > Ensure travis-ci won't cache nifi artifacts > --- > > Key: NIFI-3650 > URL: https://issues.apache.org/jira/browse/NIFI-3650 > Project: Apache NiFi > Issue Type: Bug >Reporter: Andre F de Miranda >Assignee: Andre F de Miranda > Fix For: 1.2.0 > > > while caching dependencies is a fair way of improving travis-ci build times, > the existence of cached NiFi artifacts within maven's ~/.m2 directory may > hide issues caused by incomplete code refactoring that would otherwise be > triggered had travis-ci been running a truly clean build. > We should find a way of balancing caching and possible build false negatives. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (NIFI-3650) Ensure travis-ci won't cache nifi artifacts
[ https://issues.apache.org/jira/browse/NIFI-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-3650. --- Resolution: Fixed > Ensure travis-ci won't cache nifi artifacts > --- > > Key: NIFI-3650 > URL: https://issues.apache.org/jira/browse/NIFI-3650 > Project: Apache NiFi > Issue Type: Bug >Reporter: Andre F de Miranda >Assignee: Andre F de Miranda > Fix For: 1.2.0 > > > while caching dependencies is a fair way of improving travis-ci build times, > the existence of cached NiFi artifacts within maven's ~/.m2 directory may > hide issues caused by incomplete code refactoring that would otherwise be > triggered had travis-ci been running a truly clean build. > We should find a way of balancing caching and possible build false negatives. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFIREG-2) Design logo for Registry
[ https://issues.apache.org/jira/browse/NIFIREG-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949228#comment-15949228 ] Aldrin Piri commented on NIFIREG-2: --- awesome, I like the design and work you've done! > Design logo for Registry > > > Key: NIFIREG-2 > URL: https://issues.apache.org/jira/browse/NIFIREG-2 > Project: NiFi Registry > Issue Type: Task >Reporter: Rob Moran >Assignee: Rob Moran >Priority: Minor > Attachments: registry-logo-concept_2017-03-27.png, > registry-logo-concept_2017-03-30.png > > > The attached image contains the proposed logo design for Registry. The points > below describe some of the thinking behind it: > * Relationship to NiFi and MiNiFi through the use of the same color palette, > typeface, and block elements representing bits of data > * For Registry these blocks also represent the storage/organization aspect > through their even distribution and arrangement > * The 3 gradated blocks across the top – forming the terminal part of a > lowercase *r* – represent movement (e.g., a versioned flow being saved to > NiFi or imported to NiFi from the registry) > * Relating back to the original water/flow concept of NiFi, the curved line > integrated into the gradated blocks represent the continuous motion of > flowing water > * The light gray block helps with idea of storage as previously mentioned, > but also alludes to unused storage/free space > * The gray block also helps establish the strong diagonal slicing through it > and the lowest green block. Again this helps with the idea of movement, but > more so speaks to how Registry operates in the background, tucked away, > largely unseen by NiFi operators as it facilitates deployment tasks -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3665) Documentation doesn't cover handling of local state directory in upgrade scenarios
Aldrin Piri created NIFI-3665:
-
Summary: Documentation doesn't cover handling of local state
directory in upgrade scenarios
Key: NIFI-3665
URL: https://issues.apache.org/jira/browse/NIFI-3665
Project: Apache NiFi
Issue Type: Improvement
Components: Documentation & Website
Reporter: Aldrin Piri
Priority: Minor
We had a user that was running a standalone instance of NiFi and was unsure of
what to do with the state directory.
{quote}
I just wanted to confirm something, but I couldn't find anything online.
A lot of docs that talk about setting NiFi up from a System Admin's
point-of-view, mention changing config to move several folders out of the NiFi
root dir. These typically include all 4 repositories, as well as files like the
flow.xml.gz.
I see most guide leave the 'work' dir in place, so I assume when a new version
comes out, nothing is lost if 'work' is deleted.
However, I'm not sure about the 'state' dir. Should this exist outside of the
root dir, if the idea is to replace NiFi's root dir with a new version, or does
it also get re-built like 'work'? Does it make a difference when running single
node vs (master-less) cluster?
Thanks for any advice in advance,
--Wes
{quote}
We don't seem to capture the idea of externalizing this to make upgrades easier
in our Administrator's guide
(https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#state_providers)
nor in the Upgrade guide in our Wiki
(https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (NIFI-2940) Unable to view deleted components in unsecured instance Flow Configuration HIstory
[ https://issues.apache.org/jira/browse/NIFI-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951054#comment-15951054 ] Aldrin Piri commented on NIFI-2940: --- Seems to make sense. I am a bit confused why an unsecured instance has this issue though. Seems more of a bug than a matter of permissions. > Unable to view deleted components in unsecured instance Flow Configuration > HIstory > -- > > Key: NIFI-2940 > URL: https://issues.apache.org/jira/browse/NIFI-2940 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Aldrin Piri >Priority: Minor > > I have an unsecured instance of NiFi running a fairly standard flow. > Upon deleting a connection I had wanted to see what relationships were > attached to it, and viewed the Flow Configuration History. In that listing, > while I could see that there was an event that took place, all of the details > were listed as unauthorized. > I additionally tested with other components (processors, funnels, etc) and > noted similar results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-2940) Unable to view deleted components in unsecured instance Flow Configuration HIstory
[ https://issues.apache.org/jira/browse/NIFI-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951305#comment-15951305 ] Aldrin Piri commented on NIFI-2940: --- Gotcha. Thanks for clarifying! > Unable to view deleted components in unsecured instance Flow Configuration > HIstory > -- > > Key: NIFI-2940 > URL: https://issues.apache.org/jira/browse/NIFI-2940 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Aldrin Piri >Priority: Minor > > I have an unsecured instance of NiFi running a fairly standard flow. > Upon deleting a connection I had wanted to see what relationships were > attached to it, and viewed the Flow Configuration History. In that listing, > while I could see that there was an event that took place, all of the details > were listed as unauthorized. > I additionally tested with other components (processors, funnels, etc) and > noted similar results. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-2747) Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH)
[ https://issues.apache.org/jira/browse/NIFI-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951330#comment-15951330 ] Aldrin Piri commented on NIFI-2747: --- Both algos currently load the entirety of the contents into memory. > Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH) > - > > Key: NIFI-2747 > URL: https://issues.apache.org/jira/browse/NIFI-2747 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Andre F de Miranda >Assignee: Andre F de Miranda > > It would be great if we had a processor to support fuzzy hashing algorithms > such as SpamSum/SSDeep -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3691) Provide utility to verify configured security settings and certificates
Aldrin Piri created NIFI-3691: - Summary: Provide utility to verify configured security settings and certificates Key: NIFI-3691 URL: https://issues.apache.org/jira/browse/NIFI-3691 Project: Apache NiFi Issue Type: Sub-task Components: Configuration Reporter: Aldrin Piri It would be helpful to provide a utility that could analyze keystores/truststores to verify compatibility and expected behavior with configured security settings such as two way SSL (right hostname, alias, etc). The idea is that as a diagnostic tool, we could provide users with some help to verify and troubleshoot any issues that may exist with certificates outside of more expensive change/restart loops with NiFi. As a follow-on, it would be helpful to get a listing of key properties about the configured keystore/truststore or files provided. An extension of this might additionally setup a client/server test with the utility between instances, again, to verify correct operation without doing so in NiFi itself as suggested by the parent ticket. It would be nice to provide this as part of the NiFi release and accessible via nifi.sh. By extension, the functionality could also appear in the TLS toolkit. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-2747) Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH)
[ https://issues.apache.org/jira/browse/NIFI-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-2747: -- Resolution: Fixed Fix Version/s: 1.2.0 Status: Resolved (was: Patch Available) > Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH) > - > > Key: NIFI-2747 > URL: https://issues.apache.org/jira/browse/NIFI-2747 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Andre F de Miranda >Assignee: Andre F de Miranda > Fix For: 1.2.0 > > > It would be great if we had a processor to support fuzzy hashing algorithms > such as SpamSum/SSDeep -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3716) Utility to calculate MAX storage required for BackPressure on a Node
[ https://issues.apache.org/jira/browse/NIFI-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976663#comment-15976663 ] Aldrin Piri commented on NIFI-3716: --- Hey [~Eulicny], I've added you to the list of contributors in JIRA for the NIFI project and will get this ticket assigned to you. Thanks for getting involved! > Utility to calculate MAX storage required for BackPressure on a Node > > > Key: NIFI-3716 > URL: https://issues.apache.org/jira/browse/NIFI-3716 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joseph Niemiec >Priority: Trivial > > Today there is no way to understand the max amount of data which can be > stored in backpressure for a given flow. Personally have had users configure > queues with impossible backpressure amounts that would definitely fill the > disk, having an operational tool to understand if anyone has done something > so dramatic would be helpful. > I see this produce a report by analyzing the FlowFile.xml.gz. > * Total Storage for all queues Backpressure > * Average Storage of all queues Backpressure > * Min and Max of all queues Backpressure over the entire flow. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-3716) Utility to calculate MAX storage required for BackPressure on a Node
[ https://issues.apache.org/jira/browse/NIFI-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned NIFI-3716: - Assignee: Eric Ulicny > Utility to calculate MAX storage required for BackPressure on a Node > > > Key: NIFI-3716 > URL: https://issues.apache.org/jira/browse/NIFI-3716 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joseph Niemiec >Assignee: Eric Ulicny >Priority: Trivial > > Today there is no way to understand the max amount of data which can be > stored in backpressure for a given flow. Personally have had users configure > queues with impossible backpressure amounts that would definitely fill the > disk, having an operational tool to understand if anyone has done something > so dramatic would be helpful. > I see this produce a report by analyzing the FlowFile.xml.gz. > * Total Storage for all queues Backpressure > * Average Storage of all queues Backpressure > * Min and Max of all queues Backpressure over the entire flow. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3260) Official Docker Image
[ https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992625#comment-15992625 ] Aldrin Piri commented on NIFI-3260: --- [~joewitt] If this is the last thing left, we can bump it from the release. Or perhaps more appropriately, I will close this ticket and then create a new one. To give ourselves a bit more wiggle room, I may look to request a new repository (maybe nifi-docker or similar) and migrate all of our Docker work to that from the respective projects. It allows us more flexibility and decouples the Docker work from each project. Unfortunately, it would introduce another round of voting separate from each release process. We could batch these up as a couple of the projects are related in terms of release timelines. Let me know your thoughts. If it seems reasonable, I can kick out an email to the community to get some more input. > 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: Aldrin Piri > 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.15#6346)
[jira] [Commented] (NIFI-3260) Official Docker Image
[ https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992902#comment-15992902 ] Aldrin Piri commented on NIFI-3260: --- Have been chatting with INFRA a bit in their HipChat room. Seems like the procedure/process for this getting enabled is still a bit up in the air. Waiting to hear from another part of the team about next steps. Will try to follow up once I learn a bit more. > 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: Aldrin Piri > 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.15#6346)
[jira] [Resolved] (NIFI-3260) Official Docker Image
[ https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-3260. --- Resolution: Done > 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: Aldrin Piri > 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.15#6346)
[jira] [Commented] (NIFI-3260) Official Docker Image
[ https://issues.apache.org/jira/browse/NIFI-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15993420#comment-15993420 ] Aldrin Piri commented on NIFI-3260: --- Haven't made any progress with INFRA. At this point in time we can mark this issue as resolved and open a new ticket to get integrated with Docker Hub at some point once those processes are better established. > 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: Aldrin Piri > 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.15#6346)
[jira] [Created] (NIFI-3772) Integrate Docker Image into Docker Hub
Aldrin Piri created NIFI-3772: - Summary: Integrate Docker Image into Docker Hub Key: NIFI-3772 URL: https://issues.apache.org/jira/browse/NIFI-3772 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Reporter: Jeremy Dyer Assignee: Aldrin Piri 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.15#6346)
[jira] [Updated] (NIFI-3772) Integrate Docker Image into Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3772: -- Description: This JIRA is for setting up the created Docker image in Docker Hub once we can determine how to do so under the apache account. (was: 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) > Integrate Docker Image into Docker Hub > -- > > Key: NIFI-3772 > URL: https://issues.apache.org/jira/browse/NIFI-3772 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Jeremy Dyer >Assignee: Aldrin Piri > Labels: docker > Fix For: 1.2.0 > > > This JIRA is for setting up the created Docker image in Docker Hub once we > can determine how to do so under the apache account. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3772) Integrate Docker Image into Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3772: -- Fix Version/s: (was: 1.2.0) > Integrate Docker Image into Docker Hub > -- > > Key: NIFI-3772 > URL: https://issues.apache.org/jira/browse/NIFI-3772 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Jeremy Dyer >Assignee: Aldrin Piri > Labels: docker > > This JIRA is for setting up the created Docker image in Docker Hub once we > can determine how to do so under the apache account. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3772) Integrate Docker Image into Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3772: -- Fix Version/s: 1.2.0 > Integrate Docker Image into Docker Hub > -- > > Key: NIFI-3772 > URL: https://issues.apache.org/jira/browse/NIFI-3772 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Jeremy Dyer >Assignee: Aldrin Piri > Labels: docker > Fix For: 1.2.0 > > > This JIRA is for setting up the created Docker image in Docker Hub once we > can determine how to do so under the apache account. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (NIFI-3772) Integrate Docker Image into Docker Hub
[ https://issues.apache.org/jira/browse/NIFI-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-3772. --- Resolution: Fixed Yay, Infra! > Integrate Docker Image into Docker Hub > -- > > Key: NIFI-3772 > URL: https://issues.apache.org/jira/browse/NIFI-3772 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Jeremy Dyer >Assignee: Aldrin Piri > Labels: docker > Fix For: 1.2.0 > > > This JIRA is for setting up the created Docker image in Docker Hub once we > can determine how to do so under the apache account. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3802) Update site/evangelize how to access ASF NiFi Hipchat room
Aldrin Piri created NIFI-3802: - Summary: Update site/evangelize how to access ASF NiFi Hipchat room Key: NIFI-3802 URL: https://issues.apache.org/jira/browse/NIFI-3802 Project: Apache NiFi Issue Type: Task Components: Documentation & Website Reporter: Aldrin Piri Assignee: Aldrin Piri As part of https://issues.apache.org/jira/browse/INFRA-14090 a HipChat room was created on the ASF instance with a publicly accessible link. This would be a helpful resource for allowing communication more immediately among community members in a location other than GitHub PRs and the like. Once documentation is established, should also send out messages to dev and users as another resource available. Accessible here: https://www.hipchat.com/gzh2m5YML -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3829) Processor has visual defect and shows canvas
Aldrin Piri created NIFI-3829: - Summary: Processor has visual defect and shows canvas Key: NIFI-3829 URL: https://issues.apache.org/jira/browse/NIFI-3829 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.2.0 Environment: Debian Stretch Firefox 41.4 Reporter: Aldrin Piri Priority: Trivial In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and Windows), a processor after being placed on the canvas and then subsequently moved, causes the background behind the processor name, version, NAR disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3829: -- Attachment: transparent processor info.png > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Firefox 41.4 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
Aldrin Piri created NIFI-3830: - Summary: Clicking on any component on Linux causes %3F to continuously be added to beginning of query string Key: NIFI-3830 URL: https://issues.apache.org/jira/browse/NIFI-3830 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.2.0 Environment: Linux Firefox & Chromium Reporter: Aldrin Piri Priority: Minor In Debian across both Firefox and Chromium, selecting a component causes another %3F (encoded ?) to be prepended to the query string after the original ?. The URL remains the same until moving up the hierarchy (exiting a process group). The UI and URL is still functional but imagine it might cause problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
[ https://issues.apache.org/jira/browse/NIFI-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3830: -- Attachment: malformed query string.png > Clicking on any component on Linux causes %3F to continuously be added to > beginning of query string > --- > > Key: NIFI-3830 > URL: https://issues.apache.org/jira/browse/NIFI-3830 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Linux > Firefox & Chromium >Reporter: Aldrin Piri >Priority: Minor > Attachments: malformed query string.png > > > In Debian across both Firefox and Chromium, selecting a component causes > another %3F (encoded ?) to be prepended to the query string after the > original ?. > The URL remains the same until moving up the hierarchy (exiting a process > group). The UI and URL is still functional but imagine it might cause > problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3829: -- Environment: Debian Stretch Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 was: Debian Stretch Firefox 41.4 Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 > (64-bit) > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3829: -- Environment: Debian Stretch Firefox 41.4 Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 was: Debian Stretch Firefox 41.4 > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Firefox 41.4 > Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 > (64-bit) > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1651#comment-1651 ] Aldrin Piri commented on NIFI-3829: --- Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Firefox 41.4 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
[ https://issues.apache.org/jira/browse/NIFI-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1653#comment-1653 ] Aldrin Piri commented on NIFI-3830: --- Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 > Clicking on any component on Linux causes %3F to continuously be added to > beginning of query string > --- > > Key: NIFI-3830 > URL: https://issues.apache.org/jira/browse/NIFI-3830 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Linux > Firefox & Chromium > Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 > (64-bit) > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Minor > Attachments: malformed query string.png > > > In Debian across both Firefox and Chromium, selecting a component causes > another %3F (encoded ?) to be prepended to the query string after the > original ?. > The URL remains the same until moving up the hierarchy (exiting a process > group). The UI and URL is still functional but imagine it might cause > problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
[ https://issues.apache.org/jira/browse/NIFI-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3830: -- Environment: Linux Firefox & Chromium Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 was: Linux Firefox & Chromium > Clicking on any component on Linux causes %3F to continuously be added to > beginning of query string > --- > > Key: NIFI-3830 > URL: https://issues.apache.org/jira/browse/NIFI-3830 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Linux > Firefox & Chromium > Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 > (64-bit) > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Minor > Attachments: malformed query string.png > > > In Debian across both Firefox and Chromium, selecting a component causes > another %3F (encoded ?) to be prepended to the query string after the > original ?. > The URL remains the same until moving up the hierarchy (exiting a process > group). The UI and URL is still functional but imagine it might cause > problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3829: -- Environment: Debian Stretch Firefox 45.1.1 was: Debian Stretch Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1651#comment-1651 ] Aldrin Piri edited comment on NIFI-3829 at 5/7/17 8:27 PM: --- Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 was (Author: aldrin): Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 (64-bit) Firefox 45.1.1 > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3829) Processor has visual defect and shows canvas
[ https://issues.apache.org/jira/browse/NIFI-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000779#comment-16000779 ] Aldrin Piri commented on NIFI-3829: --- Gotcha, wasn't able to dig out the supported versions. Feel free to close this issue. That is the current release for a stock distribution of Debian 9 and treated as an ESR (extended support). Not likely to introduce other sources on that system to upgrade. > Processor has visual defect and shows canvas > > > Key: NIFI-3829 > URL: https://issues.apache.org/jira/browse/NIFI-3829 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Debian Stretch > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Trivial > Attachments: transparent processor info.png > > > In Debian on Firefox (Chrome/Chromium seems unaffected as well as on OS X and > Windows), a processor after being placed on the canvas and then subsequently > moved, causes the background behind the processor name, version, NAR > disappears and allows the canvas to show through. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
[ https://issues.apache.org/jira/browse/NIFI-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000798#comment-16000798 ] Aldrin Piri commented on NIFI-3830: --- Is the listed version of Chrome unsupported too? > Clicking on any component on Linux causes %3F to continuously be added to > beginning of query string > --- > > Key: NIFI-3830 > URL: https://issues.apache.org/jira/browse/NIFI-3830 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Linux > Firefox & Chromium > Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 > (64-bit) > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Minor > Attachments: malformed query string.png > > > In Debian across both Firefox and Chromium, selecting a component causes > another %3F (encoded ?) to be prepended to the query string after the > original ?. > The URL remains the same until moving up the hierarchy (exiting a process > group). The UI and URL is still functional but imagine it might cause > problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3830) Clicking on any component on Linux causes %3F to continuously be added to beginning of query string
[ https://issues.apache.org/jira/browse/NIFI-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000804#comment-16000804 ] Aldrin Piri commented on NIFI-3830: --- Apparently looked everywhere else but user guide. For Future Aldrin, browser support is: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#browser-support > Clicking on any component on Linux causes %3F to continuously be added to > beginning of query string > --- > > Key: NIFI-3830 > URL: https://issues.apache.org/jira/browse/NIFI-3830 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.2.0 > Environment: Linux > Firefox & Chromium > Version 50.0.2661.94 built on Debian stretch/sid, running on Debian 9.0 > (64-bit) > Firefox 45.1.1 >Reporter: Aldrin Piri >Priority: Minor > Attachments: malformed query string.png > > > In Debian across both Firefox and Chromium, selecting a component causes > another %3F (encoded ?) to be prepended to the query string after the > original ?. > The URL remains the same until moving up the hierarchy (exiting a process > group). The UI and URL is still functional but imagine it might cause > problems should this cause the URL to exceed max length. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3835) Provide signal handling for docker image
Aldrin Piri created NIFI-3835: - Summary: Provide signal handling for docker image Key: NIFI-3835 URL: https://issues.apache.org/jira/browse/NIFI-3835 Project: Apache NiFi Issue Type: Improvement Components: Docker Affects Versions: 1.2.0 Reporter: Aldrin Piri It would be helpful to include traps of system signals. Additionally, ways of invoking functionality at shutdown time could give the container more resilience. This was initially prompted by a mailing list question and comment on the original Docker PR by Gaurav: https://github.com/apache/nifi/pull/1372#issuecomment-299902495 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3835) Provide signal handling for docker image
[ https://issues.apache.org/jira/browse/NIFI-3835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000965#comment-16000965 ] Aldrin Piri commented on NIFI-3835: --- One such example of a pre-existing solution after a quick search for this work is https://github.com/Yelp/dumb-init. MIT licensed > Provide signal handling for docker image > > > Key: NIFI-3835 > URL: https://issues.apache.org/jira/browse/NIFI-3835 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker >Affects Versions: 1.2.0 >Reporter: Aldrin Piri > > It would be helpful to include traps of system signals. Additionally, ways > of invoking functionality at shutdown time could give the container more > resilience. > This was initially prompted by a mailing list question and comment on the > original Docker PR by Gaurav: > https://github.com/apache/nifi/pull/1372#issuecomment-299902495 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3802) Update site/evangelize how to access ASF NiFi Hipchat room
[ https://issues.apache.org/jira/browse/NIFI-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3802: -- Status: Patch Available (was: In Progress) > Update site/evangelize how to access ASF NiFi Hipchat room > -- > > Key: NIFI-3802 > URL: https://issues.apache.org/jira/browse/NIFI-3802 > Project: Apache NiFi > Issue Type: Task > Components: Documentation & Website >Reporter: Aldrin Piri >Assignee: Aldrin Piri > > As part of https://issues.apache.org/jira/browse/INFRA-14090 a HipChat room > was created on the ASF instance with a publicly accessible link. This would > be a helpful resource for allowing communication more immediately among > community members in a location other than GitHub PRs and the like. > Once documentation is established, should also send out messages to dev and > users as another resource available. > Accessible here: https://www.hipchat.com/gzh2m5YML -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-3802) Update site/evangelize how to access ASF NiFi Hipchat room
[ https://issues.apache.org/jira/browse/NIFI-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001101#comment-16001101 ] Aldrin Piri commented on NIFI-3802: --- After merging of associated PRs, need to send an email out to users/dev to announce and point at listed resources. > Update site/evangelize how to access ASF NiFi Hipchat room > -- > > Key: NIFI-3802 > URL: https://issues.apache.org/jira/browse/NIFI-3802 > Project: Apache NiFi > Issue Type: Task > Components: Documentation & Website >Reporter: Aldrin Piri >Assignee: Aldrin Piri > > As part of https://issues.apache.org/jira/browse/INFRA-14090 a HipChat room > was created on the ASF instance with a publicly accessible link. This would > be a helpful resource for allowing communication more immediately among > community members in a location other than GitHub PRs and the like. > Once documentation is established, should also send out messages to dev and > users as another resource available. > Accessible here: https://www.hipchat.com/gzh2m5YML -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3864) Update RM guide to handle Docker build preconditions
Aldrin Piri created NIFI-3864: - Summary: Update RM guide to handle Docker build preconditions Key: NIFI-3864 URL: https://issues.apache.org/jira/browse/NIFI-3864 Project: Apache NiFi Issue Type: Task Components: Docker, Documentation & Website Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 1.3.0 The Dockerbuild currently works off of archive.apache.org. Artifacts are moved from dist to archive in an automated fashion. We need to update verbiage such that we are sure the needed artifacts are present before pushing the rel/ tag. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (NIFI-3112) When running "nifi.sh start" errors that occur in the bootstrap are routed to dev/null
[ https://issues.apache.org/jira/browse/NIFI-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reopened NIFI-3112: --- Assignee: (was: Andre F de Miranda) SSH hangs as originally reported in 2199 > When running "nifi.sh start" errors that occur in the bootstrap are routed > to dev/null > --- > > Key: NIFI-3112 > URL: https://issues.apache.org/jira/browse/NIFI-3112 > Project: Apache NiFi > Issue Type: Bug >Reporter: Joseph Percivall >Priority: Critical > Fix For: 1.2.0 > > > The commit added in this PR[1] makes it so any errors that occur in the > bootstrap during a "start" command will get routed to dev/null and it will > silently fail. Nothing is logged to the bootstrap log either. If you do the > "run" command it will work as expected and show the error. > [1] https://github.com/apache/nifi/pull/1092 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (NIFI-2199) NiFi cannot be restarted through SSH (nifi.sh hangs)
[
https://issues.apache.org/jira/browse/NIFI-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reopened NIFI-2199:
---
SSH hangs due to routing of bootstrap errors in NIFI-3112
> NiFi cannot be restarted through SSH (nifi.sh hangs)
>
>
> Key: NIFI-2199
> URL: https://issues.apache.org/jira/browse/NIFI-2199
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.0.0, 0.5.1, 0.7.0, 0.6.1
>Reporter: Michal Klempa
>Priority: Minor
> Labels: initscript
> Fix For: 1.1.0
>
>
> When NiFi is to restarted using SSH from remote host, nifi.sh causes SSH to
> hang on open io streams.
> Steps to reproduce:
> 1. HostA - NiFi instalation
> 2. HostB - client machine
> 3. log to HostB
> 4. issue a command
> {code}
> ssh root@HostA /etc/init.d/nifi restart
> {code}
> Expected behavior: NiFi is restarted, SSH command exits with 0
> Actual behavior: NiFi is restarted, SSH command hang on
> This seems to be somehow related to SSH handling IO streams of process. Seems
> like detached NiFi java process does not close stdin/out/err (i do not know
> precisely) leading to sshd waiting for some input/output to come to client.
> I was able to do a quick&dirty fix in nifi.sh as follows:
> 1. on existing nifi installation, in file /etc/init.d/nifi find the line
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ &)
> {code}
> its line number 214 (true branch of if [ "$1"] = "start"] condition).
> 2. replace it by line:
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ > /dev/null 2>&1 < /dev/null &)
> {code}
> This simply redirects stdin from /dev/null to NiFi java process and redirects
> stdout/err to /dev/null letting SSH to close the session.
> After applying this fix, I am able to restart NiFi remotely using SSH.
> Use case for this scenario: When Flow Manager develop flow.xml.gz on
> localhost/testing environments, usually deployment to production environment
> is handled by jenkins/bamboo CI tools. These tools need to log in, upload new
> flow.xml.gz and restart NiFi. All remotely using SSH.
> If somebody can advice me where in the source code is this line of code
> located, I can prepare a pull request for this quick&dirty fix.
> But. Maybe we may want to go further and investigate what to do with IO
> streams inside Java...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (NIFI-2199) NiFi cannot be restarted through SSH (nifi.sh hangs)
[
https://issues.apache.org/jira/browse/NIFI-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated NIFI-2199:
--
Affects Version/s: 1.2.0
> NiFi cannot be restarted through SSH (nifi.sh hangs)
>
>
> Key: NIFI-2199
> URL: https://issues.apache.org/jira/browse/NIFI-2199
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.0.0, 0.5.1, 0.7.0, 0.6.1, 1.2.0
>Reporter: Michal Klempa
>Priority: Minor
> Labels: initscript
> Fix For: 1.1.0
>
>
> When NiFi is to restarted using SSH from remote host, nifi.sh causes SSH to
> hang on open io streams.
> Steps to reproduce:
> 1. HostA - NiFi instalation
> 2. HostB - client machine
> 3. log to HostB
> 4. issue a command
> {code}
> ssh root@HostA /etc/init.d/nifi restart
> {code}
> Expected behavior: NiFi is restarted, SSH command exits with 0
> Actual behavior: NiFi is restarted, SSH command hang on
> This seems to be somehow related to SSH handling IO streams of process. Seems
> like detached NiFi java process does not close stdin/out/err (i do not know
> precisely) leading to sshd waiting for some input/output to come to client.
> I was able to do a quick&dirty fix in nifi.sh as follows:
> 1. on existing nifi installation, in file /etc/init.d/nifi find the line
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ &)
> {code}
> its line number 214 (true branch of if [ "$1"] = "start"] condition).
> 2. replace it by line:
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ > /dev/null 2>&1 < /dev/null &)
> {code}
> This simply redirects stdin from /dev/null to NiFi java process and redirects
> stdout/err to /dev/null letting SSH to close the session.
> After applying this fix, I am able to restart NiFi remotely using SSH.
> Use case for this scenario: When Flow Manager develop flow.xml.gz on
> localhost/testing environments, usually deployment to production environment
> is handled by jenkins/bamboo CI tools. These tools need to log in, upload new
> flow.xml.gz and restart NiFi. All remotely using SSH.
> If somebody can advice me where in the source code is this line of code
> located, I can prepare a pull request for this quick&dirty fix.
> But. Maybe we may want to go further and investigate what to do with IO
> streams inside Java...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (NIFI-2199) NiFi cannot be restarted through SSH (nifi.sh hangs)
[
https://issues.apache.org/jira/browse/NIFI-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri reassigned NIFI-2199:
-
Assignee: Aldrin Piri
> NiFi cannot be restarted through SSH (nifi.sh hangs)
>
>
> Key: NIFI-2199
> URL: https://issues.apache.org/jira/browse/NIFI-2199
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.0.0, 0.5.1, 0.7.0, 0.6.1, 1.2.0
>Reporter: Michal Klempa
>Assignee: Aldrin Piri
>Priority: Minor
> Labels: initscript
> Fix For: 1.1.0
>
>
> When NiFi is to restarted using SSH from remote host, nifi.sh causes SSH to
> hang on open io streams.
> Steps to reproduce:
> 1. HostA - NiFi instalation
> 2. HostB - client machine
> 3. log to HostB
> 4. issue a command
> {code}
> ssh root@HostA /etc/init.d/nifi restart
> {code}
> Expected behavior: NiFi is restarted, SSH command exits with 0
> Actual behavior: NiFi is restarted, SSH command hang on
> This seems to be somehow related to SSH handling IO streams of process. Seems
> like detached NiFi java process does not close stdin/out/err (i do not know
> precisely) leading to sshd waiting for some input/output to come to client.
> I was able to do a quick&dirty fix in nifi.sh as follows:
> 1. on existing nifi installation, in file /etc/init.d/nifi find the line
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ &)
> {code}
> its line number 214 (true branch of if [ "$1"] = "start"] condition).
> 2. replace it by line:
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ > /dev/null 2>&1 < /dev/null &)
> {code}
> This simply redirects stdin from /dev/null to NiFi java process and redirects
> stdout/err to /dev/null letting SSH to close the session.
> After applying this fix, I am able to restart NiFi remotely using SSH.
> Use case for this scenario: When Flow Manager develop flow.xml.gz on
> localhost/testing environments, usually deployment to production environment
> is handled by jenkins/bamboo CI tools. These tools need to log in, upload new
> flow.xml.gz and restart NiFi. All remotely using SSH.
> If somebody can advice me where in the source code is this line of code
> located, I can prepare a pull request for this quick&dirty fix.
> But. Maybe we may want to go further and investigate what to do with IO
> streams inside Java...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (NIFI-3112) When running "nifi.sh start" errors that occur in the bootstrap are routed to dev/null
[ https://issues.apache.org/jira/browse/NIFI-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned NIFI-3112: - Assignee: Aldrin Piri > When running "nifi.sh start" errors that occur in the bootstrap are routed > to dev/null > --- > > Key: NIFI-3112 > URL: https://issues.apache.org/jira/browse/NIFI-3112 > Project: Apache NiFi > Issue Type: Bug >Reporter: Joseph Percivall >Assignee: Aldrin Piri >Priority: Critical > Fix For: 1.2.0 > > > The commit added in this PR[1] makes it so any errors that occur in the > bootstrap during a "start" command will get routed to dev/null and it will > silently fail. Nothing is logged to the bootstrap log either. If you do the > "run" command it will work as expected and show the error. > [1] https://github.com/apache/nifi/pull/1092 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3112) When running "nifi.sh start" errors that occur in the bootstrap are routed to dev/null
[ https://issues.apache.org/jira/browse/NIFI-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3112: -- Fix Version/s: 1.3.0 Status: Patch Available (was: Reopened) > When running "nifi.sh start" errors that occur in the bootstrap are routed > to dev/null > --- > > Key: NIFI-3112 > URL: https://issues.apache.org/jira/browse/NIFI-3112 > Project: Apache NiFi > Issue Type: Bug >Reporter: Joseph Percivall >Assignee: Aldrin Piri >Priority: Critical > Fix For: 1.3.0, 1.2.0 > > > The commit added in this PR[1] makes it so any errors that occur in the > bootstrap during a "start" command will get routed to dev/null and it will > silently fail. Nothing is logged to the bootstrap log either. If you do the > "run" command it will work as expected and show the error. > [1] https://github.com/apache/nifi/pull/1092 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-2199) NiFi cannot be restarted through SSH (nifi.sh hangs)
[
https://issues.apache.org/jira/browse/NIFI-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aldrin Piri updated NIFI-2199:
--
Fix Version/s: 1.3.0
Status: Patch Available (was: Reopened)
> NiFi cannot be restarted through SSH (nifi.sh hangs)
>
>
> Key: NIFI-2199
> URL: https://issues.apache.org/jira/browse/NIFI-2199
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.2.0, 0.6.1, 0.7.0, 0.5.1, 1.0.0
>Reporter: Michal Klempa
>Assignee: Aldrin Piri
>Priority: Minor
> Labels: initscript
> Fix For: 1.3.0, 1.1.0
>
>
> When NiFi is to restarted using SSH from remote host, nifi.sh causes SSH to
> hang on open io streams.
> Steps to reproduce:
> 1. HostA - NiFi instalation
> 2. HostB - client machine
> 3. log to HostB
> 4. issue a command
> {code}
> ssh root@HostA /etc/init.d/nifi restart
> {code}
> Expected behavior: NiFi is restarted, SSH command exits with 0
> Actual behavior: NiFi is restarted, SSH command hang on
> This seems to be somehow related to SSH handling IO streams of process. Seems
> like detached NiFi java process does not close stdin/out/err (i do not know
> precisely) leading to sshd waiting for some input/output to come to client.
> I was able to do a quick&dirty fix in nifi.sh as follows:
> 1. on existing nifi installation, in file /etc/init.d/nifi find the line
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ &)
> {code}
> its line number 214 (true branch of if [ "$1"] = "start"] condition).
> 2. replace it by line:
> {code}
> (cd "${NIFI_HOME}" && ${sudo_cmd_prefix} "${JAVA}" -cp
> "${BOOTSTRAP_CLASSPATH}" -Xms12m -Xmx24m
> -Dorg.apache.nifi.bootstrap.config.file="${BOOTSTRAP_CONF}"
> org.apache.nifi.bootstrap.RunNiFi $@ > /dev/null 2>&1 < /dev/null &)
> {code}
> This simply redirects stdin from /dev/null to NiFi java process and redirects
> stdout/err to /dev/null letting SSH to close the session.
> After applying this fix, I am able to restart NiFi remotely using SSH.
> Use case for this scenario: When Flow Manager develop flow.xml.gz on
> localhost/testing environments, usually deployment to production environment
> is handled by jenkins/bamboo CI tools. These tools need to log in, upload new
> flow.xml.gz and restart NiFi. All remotely using SSH.
> If somebody can advice me where in the source code is this line of code
> located, I can prepare a pull request for this quick&dirty fix.
> But. Maybe we may want to go further and investigate what to do with IO
> streams inside Java...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (NIFI-1345) Create diagram(s) of lifecycles of components for developer guide
[ https://issues.apache.org/jira/browse/NIFI-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned NIFI-1345: - Assignee: (was: Aldrin Piri) > Create diagram(s) of lifecycles of components for developer guide > - > > Key: NIFI-1345 > URL: https://issues.apache.org/jira/browse/NIFI-1345 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Affects Versions: 0.4.1 >Reporter: Aldrin Piri >Priority: Minor > > Diagrams would go a long way for showing lifecycle. This is partly prompted > by NIFI-1344. What I envision are state-transition like diagrams for our > various components showing how they move from state-to-state and the various > methods that are invoked along the edges. Our textual descriptions are quite > thorough, but can be hard to visualize how they all relate to each other from > a big picture perspective. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-690) Add filesystem considerations to the Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned NIFI-690: Assignee: (was: Aldrin Piri) > Add filesystem considerations to the Admin Guide > > > Key: NIFI-690 > URL: https://issues.apache.org/jira/browse/NIFI-690 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Aldrin Piri > > Add considerations for filesystem format and call out the importance of > mapping the system to expected data (large file vs small file) and highlight > how inodes can get exhausted with many small files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-1510) Integrate Coverity with Travis CI
[ https://issues.apache.org/jira/browse/NIFI-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned NIFI-1510: - Assignee: (was: Aldrin Piri) > Integrate Coverity with Travis CI > - > > Key: NIFI-1510 > URL: https://issues.apache.org/jira/browse/NIFI-1510 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Priority: Minor > > Coverity provides static analysis of the codebase. Having this integrate > with each Travis CI would be beneficial to ensure analysis is up to date. > Instructions here: https://scan.coverity.com/travis_ci -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-658) Create a "Getting Started"/"Try it now" documentation path
[ https://issues.apache.org/jira/browse/NIFI-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned NIFI-658: Assignee: (was: Aldrin Piri) > Create a "Getting Started"/"Try it now" documentation path > -- > > Key: NIFI-658 > URL: https://issues.apache.org/jira/browse/NIFI-658 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Aldrin Piri > > I think we need to call out how to "get NiFI running." > Right now, the only path that is immediately obvious is to do the development > path which is out of the realm of many people who are not developers and/or > want to sample the application before delving in further. > Otherwise, your path is to go through nifi docs and find your way to the > admin guide just to run the latest release. > We are making a more arduous path than necessary and subjecting users to a > path that may have no relevance to their intended usage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-3899) nifi.sh/bootstrap hangs when controlled by Saltstack
Aldrin Piri created NIFI-3899: - Summary: nifi.sh/bootstrap hangs when controlled by Saltstack Key: NIFI-3899 URL: https://issues.apache.org/jira/browse/NIFI-3899 Project: Apache NiFi Issue Type: Bug Components: Tools and Build Affects Versions: 1.2.0 Reporter: Joseph Gresock It was reported that the changes to revert how the process was started have caused NiFi to hang when driven by SaltStack even with the following PR that resolved the two issues listed in NIFI-2199 & NIFI-3112 This was reported here https://github.com/apache/nifi/pull/1786 in comment https://github.com/apache/nifi/pull/1786#issuecomment-301080248 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3901) Web Api - Address minor issues with the Provenance API
[ https://issues.apache.org/jira/browse/NIFI-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3901: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Web Api - Address minor issues with the Provenance API > -- > > Key: NIFI-3901 > URL: https://issues.apache.org/jira/browse/NIFI-3901 > Project: Apache NiFi > Issue Type: Bug >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Minor > Fix For: 1.3.0 > > > - POST /provenance/lineage returns 200 instead of 201 > - Cluster Node details not correctly set in replay response > - Cluster Node details not correctly set in lineage response -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (NIFI-3914) Remote Process Group will not Enable if any Input Port or Output Port is not connected
[ https://issues.apache.org/jira/browse/NIFI-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-3914: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Remote Process Group will not Enable if any Input Port or Output Port is not > connected > -- > > Key: NIFI-3914 > URL: https://issues.apache.org/jira/browse/NIFI-3914 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne > Fix For: 1.3.0 > > > If have a Remote Process Group with multiple Input Ports. If any of the ports > does not have an incoming connection, then when I right-click and choose > "Enable Transmission" it fails, telling me that "Port XYZ has no incoming > connections". The correct behavior is to only enable transmission for ports > that we are connected to. > A workaround in this case is to click "Remote Ports" and enable each port > individually. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (NIFI-2857) Document Site 2 Site protocol
[ https://issues.apache.org/jira/browse/NIFI-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-2857. --- Resolution: Duplicate > Document Site 2 Site protocol > - > > Key: NIFI-2857 > URL: https://issues.apache.org/jira/browse/NIFI-2857 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andre F de Miranda > > It would be great if we could document the Site 2 Site protocol, in special, > the ability to publish content to RPGs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-2857) Document Site 2 Site protocol
[ https://issues.apache.org/jira/browse/NIFI-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16029590#comment-16029590 ] Aldrin Piri commented on NIFI-2857: --- [~kdoran] Thanks for pointing out. I have resolved this as a duplicate of the initial issue. > Document Site 2 Site protocol > - > > Key: NIFI-2857 > URL: https://issues.apache.org/jira/browse/NIFI-2857 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: Andre F de Miranda > > It would be great if we could document the Site 2 Site protocol, in special, > the ability to publish content to RPGs -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-4011) Bump Dockerfile version to 1.3.0
Aldrin Piri created NIFI-4011: - Summary: Bump Dockerfile version to 1.3.0 Key: NIFI-4011 URL: https://issues.apache.org/jira/browse/NIFI-4011 Project: Apache NiFi Issue Type: Task Components: Docker Affects Versions: 1.3.0 Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 1.3.0 We need to bump the Dockerfiles to 1.3.0. Additionally, this should get incorporated into the release process such that they reflect the next snapshot version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (NIFI-3864) Update RM guide to handle Docker build preconditions
[ https://issues.apache.org/jira/browse/NIFI-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-3864. --- Resolution: Fixed > Update RM guide to handle Docker build preconditions > > > Key: NIFI-3864 > URL: https://issues.apache.org/jira/browse/NIFI-3864 > Project: Apache NiFi > Issue Type: Task > Components: Docker, Documentation & Website >Reporter: Aldrin Piri >Assignee: Aldrin Piri > Fix For: 1.3.0 > > > The Dockerbuild currently works off of archive.apache.org. Artifacts are > moved from dist to archive in an automated fashion. We need to update > verbiage such that we are sure the needed artifacts are present before > pushing the rel/ tag. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (NIFI-4011) Bump Dockerfile version to 1.3.0
[ https://issues.apache.org/jira/browse/NIFI-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved NIFI-4011. --- Resolution: Fixed > Bump Dockerfile version to 1.3.0 > > > Key: NIFI-4011 > URL: https://issues.apache.org/jira/browse/NIFI-4011 > Project: Apache NiFi > Issue Type: Task > Components: Docker >Affects Versions: 1.3.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri > Fix For: 1.3.0 > > > We need to bump the Dockerfiles to 1.3.0. Additionally, this should get > incorporated into the release process such that they reflect the next > snapshot version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (NIFI-4013) Create Maven archetypes for reporting tasks and record readers/writers
Aldrin Piri created NIFI-4013: - Summary: Create Maven archetypes for reporting tasks and record readers/writers Key: NIFI-4013 URL: https://issues.apache.org/jira/browse/NIFI-4013 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Aldrin Piri The Maven archetypes are a valuable set of tools to help people quickly create processors and controller services. With the introduction of the record format and its associated readers/writers, it would be helpful to allow folks to also quickly create these implementations as needed. Additionally, while perhaps less commonly created, supporting reporting tasks in a similar manner would also be helpful. https://cwiki.apache.org/confluence/display/NIFI/Maven+Projects+for+Extensions -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-4036) ConsumeEWS cannot handle 0 recipients
[ https://issues.apache.org/jira/browse/NIFI-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041394#comment-16041394 ] Aldrin Piri commented on NIFI-4036: --- Looks like we are not also adding the Bcc recipients here: https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-email-bundle/nifi-email-processors/src/main/java/org/apache/nifi/processors/email/ConsumeEWS.java#L394 That causes the following to check to fail (https://github.com/apache/commons-email/blob/EMAIL_1_4/src/main/java/org/apache/commons/mail/Email.java#L1338) resulting in the stacktrace attached. > ConsumeEWS cannot handle 0 recipients > - > > Key: NIFI-4036 > URL: https://issues.apache.org/jira/browse/NIFI-4036 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.2.0 > Environment: Windows 7, but also within a docker-environment >Reporter: Tim Fohrer > Attachments: nifi-app.log > > > ConsumeEWS throws exceptions (stacktrace as attachment), when a mail within > the folder which has to be read has 0 recipients (to) but only bcc recipients. > This mail cannot be fetched and further transported within the flow. > Even more problematic is the fact, that other mails, which are also in the > folder and have to be read and transported, get lost. nifi just seems to > delete them on the exchange server and then forgets about them. they do not > appear as provenance data nor as a message in the success queue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (NIFI-4036) ConsumeEWS cannot handle 0 recipients
[ https://issues.apache.org/jira/browse/NIFI-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041441#comment-16041441 ] Aldrin Piri edited comment on NIFI-4036 at 6/7/17 7:06 PM: --- Quick glances seem to indicate there is an issue with how the messages are queued and then handled when that error happens. Should get a test case incorporated into the code base to try to recreate. Should be testable without an actual EWS server needed. was (Author: aldrin): Quick glances seem to indicate there is an issue with how the messages are queued and then handled when that error happens. Should get a test case incorporated into the code base to try to recreate. Should be testable without an actual EWS needed. > ConsumeEWS cannot handle 0 recipients > - > > Key: NIFI-4036 > URL: https://issues.apache.org/jira/browse/NIFI-4036 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.2.0 > Environment: Windows 7, but also within a docker-environment >Reporter: Tim Fohrer > Attachments: nifi-app.log > > > ConsumeEWS throws exceptions (stacktrace as attachment), when a mail within > the folder which has to be read has 0 recipients (to) but only bcc recipients. > This mail cannot be fetched and further transported within the flow. > Even more problematic is the fact, that other mails, which are also in the > folder and have to be read and transported, get lost. nifi just seems to > delete them on the exchange server and then forgets about them. they do not > appear as provenance data nor as a message in the success queue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (NIFI-4036) ConsumeEWS cannot handle 0 recipients
[ https://issues.apache.org/jira/browse/NIFI-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041441#comment-16041441 ] Aldrin Piri commented on NIFI-4036: --- Quick glances seem to indicate there is an issue with how the messages are queued and then handled when that error happens. Should get a test case incorporated into the code base to try to recreate. Should be testable without an actual EWS needed. > ConsumeEWS cannot handle 0 recipients > - > > Key: NIFI-4036 > URL: https://issues.apache.org/jira/browse/NIFI-4036 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.2.0 > Environment: Windows 7, but also within a docker-environment >Reporter: Tim Fohrer > Attachments: nifi-app.log > > > ConsumeEWS throws exceptions (stacktrace as attachment), when a mail within > the folder which has to be read has 0 recipients (to) but only bcc recipients. > This mail cannot be fetched and further transported within the flow. > Even more problematic is the fact, that other mails, which are also in the > folder and have to be read and transported, get lost. nifi just seems to > delete them on the exchange server and then forgets about them. they do not > appear as provenance data nor as a message in the success queue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (NIFI-4037) Create gRPC client processor
[ https://issues.apache.org/jira/browse/NIFI-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri reassigned NIFI-4037: - Assignee: Michael Hogue > Create gRPC client processor > - > > Key: NIFI-4037 > URL: https://issues.apache.org/jira/browse/NIFI-4037 > Project: Apache NiFi > Issue Type: New Feature >Reporter: Michael Hogue >Assignee: Michael Hogue >Priority: Minor > > Create a simple gRPC [1] client processor similar to InvokeHTTP that would > allow the sharing of flow files to a configured remote gRPC server. > [1] http://www.grpc.io/about/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MINIFICPP-398) Support schema config version 4
Aldrin Piri created MINIFICPP-398: - Summary: Support schema config version 4 Key: MINIFICPP-398 URL: https://issues.apache.org/jira/browse/MINIFICPP-398 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: Aldrin Piri As part of MINIFI-66, and to help us carry out some initial C2 functionalities, a closer mapping of config schema to templates will allow us to more easily make use of registry functionality. This will require that instance based configuration (things like repositories, security and the like) are extracted to other files such as the conf and/or other .properties files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-393) add security support for MQTT
[ https://issues.apache.org/jira/browse/MINIFICPP-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-393. --- Resolution: Fixed Fix Version/s: (was: 1.0.0) 0.5.0 > add security support for MQTT > - > > Key: MINIFICPP-393 > URL: https://issues.apache.org/jira/browse/MINIFICPP-393 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: bqiu >Assignee: bqiu >Priority: Minor > Fix For: 0.5.0 > > > add security support for MQTT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-393) add security support for MQTT
[ https://issues.apache.org/jira/browse/MINIFICPP-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-393: -- Affects Version/s: (was: 1.0.0) > add security support for MQTT > - > > Key: MINIFICPP-393 > URL: https://issues.apache.org/jira/browse/MINIFICPP-393 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: bqiu >Assignee: bqiu >Priority: Minor > Fix For: 0.5.0 > > > add security support for MQTT -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-382) Add SUSE support to bootstrap process.
[ https://issues.apache.org/jira/browse/MINIFICPP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-382: -- Status: Patch Available (was: Open) > Add SUSE support to bootstrap process. > --- > > Key: MINIFICPP-382 > URL: https://issues.apache.org/jira/browse/MINIFICPP-382 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > Add support to bootstrap process. > > Currently have tested on OpenSUSE and SLES12. > > SLES12/OpenSUSE – build and tested, verifying SiteToSite > SLES11 – TBD -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-383) No matter the start directory for minifi.sh, repositories are created in the current working directory
[ https://issues.apache.org/jira/browse/MINIFICPP-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-383: -- Resolution: Fixed Status: Resolved (was: Patch Available) > No matter the start directory for minifi.sh, repositories are created in the > current working directory > -- > > Key: MINIFICPP-383 > URL: https://issues.apache.org/jira/browse/MINIFICPP-383 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.1.0, 0.2.0, 0.3.0 >Reporter: marco polo >Priority: Major > Fix For: 0.5.0 > > > No matter where the user starts MiNiFi from the directory in which the repos > are created is the current working directory. This should be changed to use a > persistent directory based on the root of the installation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-4878) Update Docker docs to include all environment variables used on startup
Aldrin Piri created NIFI-4878: - Summary: Update Docker docs to include all environment variables used on startup Key: NIFI-4878 URL: https://issues.apache.org/jira/browse/NIFI-4878 Project: Apache NiFi Issue Type: Improvement Components: Docker, Documentation & Website Reporter: Aldrin Piri Fix For: 1.5.0 -NIFI-4824- provided updates to allow specification of the various ports in the container on startup via varying environment variables to aid the issue of the host whitelisting. It does not appear this information is readily available in our docs and has caused some confusion by users when trying to connect to an instance. We need to update the docs to enumerate these scenarios as well as the environment variables that are anticipated. We could additionally enhance the experience via performing some logical checks. One example could be verifying that if a custom port is set and we are running secure, there is also an environment variable provided. Additionally, providing variables that would be unused, such as NIFI_WEB_HTTP_PORT when we are running secure could also cause an error/warning. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-4879) Provide error handling and argument verification of environment variables in Docker instances
Aldrin Piri created NIFI-4879: - Summary: Provide error handling and argument verification of environment variables in Docker instances Key: NIFI-4879 URL: https://issues.apache.org/jira/browse/NIFI-4879 Project: Apache NiFi Issue Type: Improvement Components: Docker Reporter: Aldrin Piri This stems from NIFI-4878. We have some logical understanding of what variables are expected and can catch these items with at least a warning, or perhaps, an error when incongruous environment variables are supplied (e.g. specifying HTTP Port when in secure mode or the inverse). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-382) Add SUSE support to bootstrap process.
[ https://issues.apache.org/jira/browse/MINIFICPP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-382: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Add SUSE support to bootstrap process. > --- > > Key: MINIFICPP-382 > URL: https://issues.apache.org/jira/browse/MINIFICPP-382 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > Add support to bootstrap process. > > Currently have tested on OpenSUSE and SLES12. > > SLES12/OpenSUSE – build and tested, verifying SiteToSite > SLES11 – TBD -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-400) Identify workaround for CURL ABI incompatibilities.
[ https://issues.apache.org/jira/browse/MINIFICPP-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-400. --- Resolution: Fixed > Identify workaround for CURL ABI incompatibilities. > > > Key: MINIFICPP-400 > URL: https://issues.apache.org/jira/browse/MINIFICPP-400 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFICPP-409) Remove unused artifacts from Configuration Listener removal
Aldrin Piri created MINIFICPP-409: - Summary: Remove unused artifacts from Configuration Listener removal Key: MINIFICPP-409 URL: https://issues.apache.org/jira/browse/MINIFICPP-409 Project: NiFi MiNiFi C++ Issue Type: Improvement Affects Versions: 0.4.0 Reporter: Aldrin Piri Assignee: Aldrin Piri With the introduction of C2 and related efforts, some artifacts were left behind when the Configuration Listener was removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-409) Remove unused artifacts from Configuration Listener removal
[ https://issues.apache.org/jira/browse/MINIFICPP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-409: -- Status: Patch Available (was: Open) > Remove unused artifacts from Configuration Listener removal > --- > > Key: MINIFICPP-409 > URL: https://issues.apache.org/jira/browse/MINIFICPP-409 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.4.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > With the introduction of C2 and related efforts, some artifacts were left > behind when the Configuration Listener was removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-409) Remove unused artifacts from Configuration Listener removal
[ https://issues.apache.org/jira/browse/MINIFICPP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-409: -- Fix Version/s: 0.5.0 > Remove unused artifacts from Configuration Listener removal > --- > > Key: MINIFICPP-409 > URL: https://issues.apache.org/jira/browse/MINIFICPP-409 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.4.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 0.5.0 > > > With the introduction of C2 and related efforts, some artifacts were left > behind when the Configuration Listener was removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-406) Change StreamFactory to use SSLContextService if one is available.
[ https://issues.apache.org/jira/browse/MINIFICPP-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-406. --- Resolution: Fixed Fix Version/s: 0.5.0 > Change StreamFactory to use SSLContextService if one is available. > --- > > Key: MINIFICPP-406 > URL: https://issues.apache.org/jira/browse/MINIFICPP-406 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > Currently socket coordination is done through minifi.properties and is > unaware of any context service. We should change this to make configuration > consistent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-408) Secure minifi controller
[ https://issues.apache.org/jira/browse/MINIFICPP-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-408: -- Resolution: Fixed Fix Version/s: 0.5.0 Status: Resolved (was: Patch Available) > Secure minifi controller > > > Key: MINIFICPP-408 > URL: https://issues.apache.org/jira/browse/MINIFICPP-408 > Project: NiFi MiNiFi C++ > Issue Type: Sub-task >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > MiNiFi Controller only works with non secure sockets. Give users the option > to secure their instance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-409) Remove unused artifacts from Configuration Listener removal
[ https://issues.apache.org/jira/browse/MINIFICPP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-409: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Remove unused artifacts from Configuration Listener removal > --- > > Key: MINIFICPP-409 > URL: https://issues.apache.org/jira/browse/MINIFICPP-409 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.4.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 0.5.0 > > > With the introduction of C2 and related efforts, some artifacts were left > behind when the Configuration Listener was removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-407) Change wording
[ https://issues.apache.org/jira/browse/MINIFICPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-407. --- Resolution: Fixed > Change wording > -- > > Key: MINIFICPP-407 > URL: https://issues.apache.org/jira/browse/MINIFICPP-407 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > Change wording of Readme to tell that we are GA -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFICPP-412) Publish MiNiFi Docs to website
Aldrin Piri created MINIFICPP-412: - Summary: Publish MiNiFi Docs to website Key: MINIFICPP-412 URL: https://issues.apache.org/jira/browse/MINIFICPP-412 Project: NiFi MiNiFi C++ Issue Type: Improvement Reporter: Aldrin Piri Items such as Processors, Extensions, and Expression language docs are currently only available with the source. We should also get these at least linked if not published to the MiNiFi site for easier consumption. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFICPP-412) Publish MiNiFi Docs to website
[ https://issues.apache.org/jira/browse/MINIFICPP-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373290#comment-16373290 ] Aldrin Piri commented on MINIFICPP-412: --- Should also capture updating these, if published, in our release process. > Publish MiNiFi Docs to website > -- > > Key: MINIFICPP-412 > URL: https://issues.apache.org/jira/browse/MINIFICPP-412 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: Aldrin Piri >Priority: Major > > Items such as Processors, Extensions, and Expression language docs are > currently only available with the source. We should also get these at least > linked if not published to the MiNiFi site for easier consumption. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-4616) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker that is SSL enabled
[ https://issues.apache.org/jira/browse/NIFI-4616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-4616: -- Fix Version/s: (was: 1.1.0) > ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to > communicate with Kafka broker that is SSL enabled > > > Key: NIFI-4616 > URL: https://issues.apache.org/jira/browse/NIFI-4616 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.4.0 >Reporter: Aldrin Piri >Priority: Major > > If I use ConsumeKafka and point to a broker that is in a bad state, I see > ConsumeKafka block indefinitely. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINIFICPP-411) MiNIFi Controller's output needs some fixing
[ https://issues.apache.org/jira/browse/MINIFICPP-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated MINIFICPP-411: -- Fix Version/s: 0.5.0 > MiNIFi Controller's output needs some fixing > > > Key: MINIFICPP-411 > URL: https://issues.apache.org/jira/browse/MINIFICPP-411 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > A few operations need improved verification. Read me is not correct markup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-411) MiNIFi Controller's output needs some fixing
[ https://issues.apache.org/jira/browse/MINIFICPP-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-411. --- Resolution: Fixed > MiNIFi Controller's output needs some fixing > > > Key: MINIFICPP-411 > URL: https://issues.apache.org/jira/browse/MINIFICPP-411 > Project: NiFi MiNiFi C++ > Issue Type: Bug >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > A few operations need improved verification. Read me is not correct markup -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-425) Fix travis linter errors
[ https://issues.apache.org/jira/browse/MINIFICPP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-425. --- Resolution: Fixed Fix Version/s: 0.5.0 > Fix travis linter errors > - > > Key: MINIFICPP-425 > URL: https://issues.apache.org/jira/browse/MINIFICPP-425 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > Fix travis linter errors -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-424) Update CAInfo manually so user does not have to update the cert bundle on their machine
[ https://issues.apache.org/jira/browse/MINIFICPP-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-424. --- Resolution: Fixed Fix Version/s: 0.5.0 > Update CAInfo manually so user does not have to update the cert bundle on > their machine > --- > > Key: MINIFICPP-424 > URL: https://issues.apache.org/jira/browse/MINIFICPP-424 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Reporter: marco polo >Assignee: marco polo >Priority: Major > Fix For: 0.5.0 > > > Update CAInfo manually so user does not have to update the cert bundle on > their machine. We should do this for the user's convenience. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINIFICPP-439) Allow cmake3 to take precedence over cmake in bootstrap
Aldrin Piri created MINIFICPP-439: - Summary: Allow cmake3 to take precedence over cmake in bootstrap Key: MINIFICPP-439 URL: https://issues.apache.org/jira/browse/MINIFICPP-439 Project: NiFi MiNiFi C++ Issue Type: Improvement Affects Versions: 0.4.0 Reporter: Aldrin Piri Assignee: Aldrin Piri For yum based distros, CMake 3+ is provided under command cmake3. Currently bootstrap, checks for and prefers the command cmake. This can be problematic in yum environments where both cmake and cmake3 are installed. Inverting these, to prefer cmake3 would be helpful for such cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (MINIFICPP-439) Allow cmake3 to take precedence over cmake in bootstrap
[ https://issues.apache.org/jira/browse/MINIFICPP-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri resolved MINIFICPP-439. --- Resolution: Done Fix Version/s: 0.5.0 > Allow cmake3 to take precedence over cmake in bootstrap > --- > > Key: MINIFICPP-439 > URL: https://issues.apache.org/jira/browse/MINIFICPP-439 > Project: NiFi MiNiFi C++ > Issue Type: Improvement >Affects Versions: 0.4.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 0.5.0 > > > For yum based distros, CMake 3+ is provided under command cmake3. Currently > bootstrap, checks for and prefers the command cmake. This can be problematic > in yum environments where both cmake and cmake3 are installed. Inverting > these, to prefer cmake3 would be helpful for such cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (NIFIREG-118) Create a NiFi Registry Docker Image
[ https://issues.apache.org/jira/browse/NIFIREG-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri closed NIFIREG-118. --- Resolution: Duplicate > Create a NiFi Registry Docker Image > --- > > Key: NIFIREG-118 > URL: https://issues.apache.org/jira/browse/NIFIREG-118 > Project: NiFi Registry > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > > Adding a supporting Dockerfile for Registry would help many users work > through some of the quick testing and evaluation of Registry in conjunction > with the NiFi image with the assistance of config scripts and/or > docker-compose. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5003) nifi.sh install is broken in systemd operating systems
[ https://issues.apache.org/jira/browse/NIFI-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410194#comment-16410194 ] Aldrin Piri commented on NIFI-5003: --- >From chat, this was Ubuntu 16.04.4 > nifi.sh install is broken in systemd operating systems > --- > > Key: NIFI-5003 > URL: https://issues.apache.org/jira/browse/NIFI-5003 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.4.0, 1.5.0 >Reporter: Samuel Miller >Priority: Major > > I've been unable to use systemctl after executing > `bin/nifi.sh install nifi` > > Using it generates the following errors when attempting to use either > systemctl commands or apt-get dist-upgrade commands: > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Max recursions depth 99 reached > > > My system: > $ java -version > java version "1.8.0_161" > Java(TM) SE Runtime Environment (build 1.8.0_161-b12) > Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode) > samuel@nifi-1:~$ mvn -version > The program 'mvn' is currently not installed. To run 'mvn' please ask your > administrator to install the package 'maven' > samuel@nifi-1:~$ uname -a > Linux nifi-1.west.usermind.com 4.4.0-1052-aws #61-Ubuntu SMP Mon Feb 12 > 23:05:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5003) nifi.sh install is broken in systemd operating systems
[ https://issues.apache.org/jira/browse/NIFI-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410207#comment-16410207 ] Aldrin Piri commented on NIFI-5003: --- exemplary work to support this: https://gist.github.com/ddewaele/54f67b0e9afaa538c31723cd2f609e14 > nifi.sh install is broken in systemd operating systems > --- > > Key: NIFI-5003 > URL: https://issues.apache.org/jira/browse/NIFI-5003 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.4.0, 1.5.0 >Reporter: Samuel Miller >Priority: Major > > I've been unable to use systemctl after executing > `bin/nifi.sh install nifi` > > Using it generates the following errors when attempting to use either > systemctl commands or apt-get dist-upgrade commands: > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Starting nifi depends on plymouth and therefore on system facility > `$all' which can not be true! > insserv: Max recursions depth 99 reached > > > My system: > $ java -version > java version "1.8.0_161" > Java(TM) SE Runtime Environment (build 1.8.0_161-b12) > Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode) > samuel@nifi-1:~$ mvn -version > The program 'mvn' is currently not installed. To run 'mvn' please ask your > administrator to install the package 'maven' > samuel@nifi-1:~$ uname -a > Linux nifi-1.west.usermind.com 4.4.0-1052-aws #61-Ubuntu SMP Mon Feb 12 > 23:05:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5006) Update docs to reflect 2018 where applicable
Aldrin Piri created NIFI-5006: - Summary: Update docs to reflect 2018 where applicable Key: NIFI-5006 URL: https://issues.apache.org/jira/browse/NIFI-5006 Project: Apache NiFi Issue Type: Task Reporter: Aldrin Piri Fix For: 1.7.0 While reviewing the RC1 for NiFi 1.6.0 I noticed that docs have not been updated to reflect the new year. We should update these when handling our next release. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5013) NiFi Standard Processors should build a test jar to reduce duplication
[ https://issues.apache.org/jira/browse/NIFI-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-5013: -- Status: Patch Available (was: Open) > NiFi Standard Processors should build a test jar to reduce duplication > -- > > Key: NIFI-5013 > URL: https://issues.apache.org/jira/browse/NIFI-5013 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > > There are some classes, notably TestServer, which are in the nifi standard > processors jar which could be used by other processors, either in the project > ( already 2 or 3 copies ) or in 3rd party processor/controller projects. > [link Apache > Maven|https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html] > details how to handle this case in two ways. > > # create a test-jar from the project > # create a new module to hold shared testing code and scope:test include it > While #2 is the preferred way, nifi should support #1 in the interim, until > some discussion on the location and structure of the test module(s) and the > classes that should be moved to them happens. The scope there will be quite > a bit larger. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5013) NiFi Standard Processors should build a test jar to reduce duplication
[ https://issues.apache.org/jira/browse/NIFI-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-5013: -- Resolution: Fixed Fix Version/s: 1.7.0 Status: Resolved (was: Patch Available) > NiFi Standard Processors should build a test jar to reduce duplication > -- > > Key: NIFI-5013 > URL: https://issues.apache.org/jira/browse/NIFI-5013 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > Fix For: 1.7.0 > > > There are some classes, notably TestServer, which are in the nifi standard > processors jar which could be used by other processors, either in the project > ( already 2 or 3 copies ) or in 3rd party processor/controller projects. > [link Apache > Maven|https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html] > details how to handle this case in two ways. > > # create a test-jar from the project > # create a new module to hold shared testing code and scope:test include it > While #2 is the preferred way, nifi should support #1 in the interim, until > some discussion on the location and structure of the test module(s) and the > classes that should be moved to them happens. The scope there will be quite > a bit larger. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5020) Consider treating test resources/utilities as a main dependency
Aldrin Piri created NIFI-5020: - Summary: Consider treating test resources/utilities as a main dependency Key: NIFI-5020 URL: https://issues.apache.org/jira/browse/NIFI-5020 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Aldrin Piri NIFI-5013 took care of consolidating duplicate resources by making a test-jar available. However, as reported on the mailing list, when building with maven.test.skip (this is distinct from skipTests), the test artifact will not be built and preclude projects that depend upon it (even in the scenario when all tests are skipped) from building correctly. Source mailing list thread: https://lists.apache.org/thread.html/ff4e44d1c40519959fbff579bad587a458833c703b5162248bf8812b@%3Cdev.nifi.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5020) Consider treating test resources/utilities as a main module
[ https://issues.apache.org/jira/browse/NIFI-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-5020: -- Summary: Consider treating test resources/utilities as a main module (was: Consider treating test resources/utilities as a main dependency) > Consider treating test resources/utilities as a main module > --- > > Key: NIFI-5020 > URL: https://issues.apache.org/jira/browse/NIFI-5020 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Aldrin Piri >Priority: Major > > NIFI-5013 took care of consolidating duplicate resources by making a test-jar > available. However, as reported on the mailing list, when building with > maven.test.skip (this is distinct from skipTests), the test artifact will not > be built and preclude projects that depend upon it (even in the scenario when > all tests are skipped) from building correctly. > Source mailing list thread: > https://lists.apache.org/thread.html/ff4e44d1c40519959fbff579bad587a458833c703b5162248bf8812b@%3Cdev.nifi.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
