[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14631309#comment-14631309 ] ASF subversion and git services commented on NIFI-656: -- Commit 16cc08748d4063d3440a12f9dd3f9f248e2814ee in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=16cc087 ] NIFI-656: - Adding links to download 0.2.0-incubating. Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-768) Update nifi-site code for TLP move
[ https://issues.apache.org/jira/browse/NIFI-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629630#comment-14629630 ] ASF subversion and git services commented on NIFI-768: -- Commit 00344624855f0ed215857a01593c397dd39d99ec in incubator-nifi's branch refs/heads/develop from [~joewitt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0034462 ] NIFI-768 staging changes needed for website in prep for move to TLP site. Still need to update some links once git and svn move. Update nifi-site code for TLP move -- Key: NIFI-768 URL: https://issues.apache.org/jira/browse/NIFI-768 Project: Apache NiFi Issue Type: Task Components: Documentation Website Reporter: Joseph Witt Assignee: Joseph Witt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-753) NPE when reading in provenance data
[ https://issues.apache.org/jira/browse/NIFI-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629827#comment-14629827 ] ASF subversion and git services commented on NIFI-753: -- Commit c0f110467997d1e05e58ef444385478ba05a59e5 in incubator-nifi's branch refs/heads/master from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c0f1104 ] NIFI-753: when truncating value, take null values into account NPE when reading in provenance data --- Key: NIFI-753 URL: https://issues.apache.org/jira/browse/NIFI-753 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.2.0 Reporter: Mark Payne Assignee: Mark Payne Priority: Blocker Fix For: 0.2.0 Attachments: 0001-NIFI-753-when-truncating-value-take-null-values-into.patch If an attribute is removed, NiFi will fail to restart: Caused by: java.lang.RuntimeException: Unable to create Provenance Repository at org.apache.nifi.controller.FlowController.init(FlowController.java:411) ~[na:na] at org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:350) ~[na:na] at org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:63) ~[na:na] at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168) ~[na:na] ... 130 common frames omitted Caused by: java.lang.NullPointerException: null at org.apache.nifi.provenance.StandardRecordReader.readAttributes(StandardRecordReader.java:372) ~[na:na] at org.apache.nifi.provenance.StandardRecordReader.nextRecord(StandardRecordReader.java:313) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.mergeJournals(PersistentProvenanceRepository.java:1356) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.recoverJournalFiles(PersistentProvenanceRepository.java:1136) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.recover(PersistentProvenanceRepository.java:572) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.initialize(PersistentProvenanceRepository.java:212) ~[na:na] at org.apache.nifi.controller.FlowController.init(FlowController.java:407) ~[na:na] ... 133 common frames omitted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629842#comment-14629842 ] ASF subversion and git services commented on NIFI-656: -- Commit e4f51eac9d1b9eabbb091a9f2c3eb1fee453cfc6 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e4f51ea ] NIFI-656-RC1 prepare release nifi-0.2.0-incubating-RC1 Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629843#comment-14629843 ] ASF subversion and git services commented on NIFI-656: -- Commit de8ec6f92c85970b1665765e0b11d04e486cc966 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=de8ec6f ] NIFI-656-RC1 prepare for next development iteration Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629830#comment-14629830 ] ASF subversion and git services commented on NIFI-656: -- Commit de8ec6f92c85970b1665765e0b11d04e486cc966 in incubator-nifi's branch refs/heads/master from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=de8ec6f ] NIFI-656-RC1 prepare for next development iteration Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-705) TestHandleHttpRequest#testRequestAddedToService fails in Ubuntu 14.04
[ https://issues.apache.org/jira/browse/NIFI-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629828#comment-14629828 ] ASF subversion and git services commented on NIFI-705: -- Commit df92dff8bb1ca0bdcebd5658aaae1234b2f5f209 in incubator-nifi's branch refs/heads/master from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=df92dff ] NIFI-705 Preventing the processor from initializing each time it is waiting for the request. TestHandleHttpRequest#testRequestAddedToService fails in Ubuntu 14.04 - Key: NIFI-705 URL: https://issues.apache.org/jira/browse/NIFI-705 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.1.0, 0.2.0 Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.2.0 Attachments: 0001-NIFI-705-Preventing-the-processor-from-initializing-.patch Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.675 sec FAILURE! - in org.apache.nifi.processors.standard.TestHandleHttpRequest testRequestAddedToService(org.apache.nifi.processors.standard.TestHandleHttpRequest) Time elapsed: 6.675 sec FAILURE! java.lang.AssertionError: Could not invoke methods annotated with @OnScheduled annotation due to: java.lang.reflect.InvocationTargetException at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:199) at org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:182) at org.apache.nifi.processors.standard.TestHandleHttpRequest.testRequestAddedToService(TestHandleHttpRequest.java:100) ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629850#comment-14629850 ] ASF subversion and git services commented on NIFI-656: -- Commit a3fab8f1244e02e8bdcf3f775af35ab37d4a in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=a3f ] NIFI-656: - Updating version of flume bundle that was added during release vote. Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14629876#comment-14629876 ] ASF subversion and git services commented on NIFI-656: -- Commit 54ad9c89914a265c5e8e89fdf83cd83d83a83ff5 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=54ad9c8 ] NIFI-656: - Updating version of flume bundle that was added during release vote. Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-751) Add Processor To Convert Avro Formats
[ https://issues.apache.org/jira/browse/NIFI-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626282#comment-14626282 ] ASF subversion and git services commented on NIFI-751: -- Commit 8ff69ca2d1bc5b7d651b7495f2ce45def12bebc2 in incubator-nifi's branch refs/heads/develop from [~joewitt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=8ff69ca ] NIFI-751 PR #70 removed extraneous reference to abstract properties pulling in hadoop conf Add Processor To Convert Avro Formats - Key: NIFI-751 URL: https://issues.apache.org/jira/browse/NIFI-751 Project: Apache NiFi Issue Type: Improvement Components: Extensions Affects Versions: 0.1.0 Reporter: Alan Jackoway When working with data from external sources, such as complex WSDL, I frequently wind up with complex nested data that is difficult to work with even when converted to Avro format. Specifically, I often have two needs: * Converting types of data, usually from string to long, double, etc. when APIs give only string data back. * Flattening data by taking fields out of nested records and putting them on the top level of the Avro file. Unfortunately the Kite JSONToAvro processor only supports exact conversions from JSON to a matching Avro schema and will not do data transformations of this type. Proposed processor to come. Discussed this with [~rdblue], so tagging him here as I don't have permission to set a CC for some reason. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-751) Add Processor To Convert Avro Formats
[ https://issues.apache.org/jira/browse/NIFI-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626281#comment-14626281 ] ASF subversion and git services commented on NIFI-751: -- Commit bb64e70e6fbda12a9e0388b5c2240d96d34ac6bf in incubator-nifi's branch refs/heads/develop from [~jackowaya] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=bb64e70 ] NIFI-751 Add Processor To Convert Avro Formats Implemented a new NiFi processor that allows avro records to be converted from one Avro schema to another. This supports.. * Flattening records using . notation like parent.id * Simple type conversions to String or base primitive types. * Specifying field renames using dynamic properties. Signed-off-by: joewitt joew...@apache.org Add Processor To Convert Avro Formats - Key: NIFI-751 URL: https://issues.apache.org/jira/browse/NIFI-751 Project: Apache NiFi Issue Type: Improvement Components: Extensions Affects Versions: 0.1.0 Reporter: Alan Jackoway When working with data from external sources, such as complex WSDL, I frequently wind up with complex nested data that is difficult to work with even when converted to Avro format. Specifically, I often have two needs: * Converting types of data, usually from string to long, double, etc. when APIs give only string data back. * Flattening data by taking fields out of nested records and putting them on the top level of the Avro file. Unfortunately the Kite JSONToAvro processor only supports exact conversions from JSON to a matching Avro schema and will not do data transformations of this type. Proposed processor to come. Discussed this with [~rdblue], so tagging him here as I don't have permission to set a CC for some reason. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-685) Proxy Support for GetHTTP and PostHTTP processors
[ https://issues.apache.org/jira/browse/NIFI-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14626295#comment-14626295 ] ASF subversion and git services commented on NIFI-685: -- Commit 4dc126aff8751e66018ac03260f3061b97719487 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=4dc126a ] NIFI-685: This is merged. This closes #67 Proxy Support for GetHTTP and PostHTTP processors - Key: NIFI-685 URL: https://issues.apache.org/jira/browse/NIFI-685 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 0.2.0 Reporter: Andrew Hulbert Priority: Minor Fix For: 0.2.0 Add http web proxy support to GetHTTP and PostHTTP processors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-589) Add processors that can run Apache Flume sources/sinks
[ https://issues.apache.org/jira/browse/NIFI-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627069#comment-14627069 ] ASF subversion and git services commented on NIFI-589: -- Commit 95b22713fc848005a526b3e71f7b19bb7ae1db00 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=95b2271 ] This closes #51 Feedback on been provided in NIFI-589 Add processors that can run Apache Flume sources/sinks -- Key: NIFI-589 URL: https://issues.apache.org/jira/browse/NIFI-589 Project: Apache NiFi Issue Type: New Feature Components: Extensions Affects Versions: 0.1.0 Reporter: Joey Echeverria Assignee: Joey Echeverria Attachments: Basic_Flume_Test.xml, Flume_File_Roll_Test.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-589) Add processors that can run Apache Flume sources/sinks
[ https://issues.apache.org/jira/browse/NIFI-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627053#comment-14627053 ] ASF subversion and git services commented on NIFI-589: -- Commit 6f3039c8c38d6af399f5a896fb7879db111ab4fe in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=6f3039c ] NIFI-589: - Tweaking license files. Add processors that can run Apache Flume sources/sinks -- Key: NIFI-589 URL: https://issues.apache.org/jira/browse/NIFI-589 Project: Apache NiFi Issue Type: New Feature Components: Extensions Affects Versions: 0.1.0 Reporter: Joey Echeverria Assignee: Joey Echeverria Attachments: Basic_Flume_Test.xml, Flume_File_Roll_Test.xml -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-685) Proxy Support for GetHTTP and PostHTTP processors
[ https://issues.apache.org/jira/browse/NIFI-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627194#comment-14627194 ] ASF subversion and git services commented on NIFI-685: -- Commit 65c82cc0ea4ccde35b5ded34b6b84afe959f62cb in incubator-nifi's branch refs/heads/develop from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=65c82cc ] This closes #67. Code has been merged as per NIFI-685 Proxy Support for GetHTTP and PostHTTP processors - Key: NIFI-685 URL: https://issues.apache.org/jira/browse/NIFI-685 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 0.2.0 Reporter: Andrew Hulbert Priority: Minor Fix For: 0.2.0 Add http web proxy support to GetHTTP and PostHTTP processors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-751) Add Processor To Convert Avro Formats
[ https://issues.apache.org/jira/browse/NIFI-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14627199#comment-14627199 ] ASF subversion and git services commented on NIFI-751: -- Commit ec6be9eaa3942e9ca9f8e4a1e788ab831e739514 in incubator-nifi's branch refs/heads/develop from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=ec6be9e ] This closes #70. Code has been merged as per NIFI-751 Add Processor To Convert Avro Formats - Key: NIFI-751 URL: https://issues.apache.org/jira/browse/NIFI-751 Project: Apache NiFi Issue Type: Improvement Components: Extensions Affects Versions: 0.1.0 Reporter: Alan Jackoway When working with data from external sources, such as complex WSDL, I frequently wind up with complex nested data that is difficult to work with even when converted to Avro format. Specifically, I often have two needs: * Converting types of data, usually from string to long, double, etc. when APIs give only string data back. * Flattening data by taking fields out of nested records and putting them on the top level of the Avro file. Unfortunately the Kite JSONToAvro processor only supports exact conversions from JSON to a matching Avro schema and will not do data transformations of this type. Proposed processor to come. Discussed this with [~rdblue], so tagging him here as I don't have permission to set a CC for some reason. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-685) Proxy Support for GetHTTP and PostHTTP processors
[ https://issues.apache.org/jira/browse/NIFI-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14623398#comment-14623398 ] ASF subversion and git services commented on NIFI-685: -- Commit 7f6f404baa1826462384de6c35be823189a36821 in incubator-nifi's branch refs/heads/develop from [~joewitt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=7f6f404 ] NIFI-685 This closes #67. Was merged/closed in JIRA but not github Proxy Support for GetHTTP and PostHTTP processors - Key: NIFI-685 URL: https://issues.apache.org/jira/browse/NIFI-685 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 0.2.0 Reporter: Andrew Hulbert Priority: Minor Fix For: 0.2.0 Add http web proxy support to GetHTTP and PostHTTP processors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618672#comment-14618672 ] ASF subversion and git services commented on NIFI-656: -- Commit 74b3a63f1522060b7e694e0ea665f6009d2aee31 in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating-rc1 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=74b3a63 ] NIFI-656-RC1 prepare for next development iteration Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618671#comment-14618671 ] ASF subversion and git services commented on NIFI-656: -- Commit 551df4deb0d62939ec50bde24219a47442bafaae in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating-rc1 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=551df4d ] NIFI-656-RC1 prepare release nifi-0.2.0-incubating-RC1 Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-705) TestHandleHttpRequest#testRequestAddedToService fails in Ubuntu 14.04
[ https://issues.apache.org/jira/browse/NIFI-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14618998#comment-14618998 ] ASF subversion and git services commented on NIFI-705: -- Commit df92dff8bb1ca0bdcebd5658aaae1234b2f5f209 in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=df92dff ] NIFI-705 Preventing the processor from initializing each time it is waiting for the request. TestHandleHttpRequest#testRequestAddedToService fails in Ubuntu 14.04 - Key: NIFI-705 URL: https://issues.apache.org/jira/browse/NIFI-705 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.1.0, 0.2.0 Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.2.0 Attachments: 0001-NIFI-705-Preventing-the-processor-from-initializing-.patch Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.675 sec FAILURE! - in org.apache.nifi.processors.standard.TestHandleHttpRequest testRequestAddedToService(org.apache.nifi.processors.standard.TestHandleHttpRequest) Time elapsed: 6.675 sec FAILURE! java.lang.AssertionError: Could not invoke methods annotated with @OnScheduled annotation due to: java.lang.reflect.InvocationTargetException at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:199) at org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:182) at org.apache.nifi.processors.standard.TestHandleHttpRequest.testRequestAddedToService(TestHandleHttpRequest.java:100) ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-705) TestHandleHttpRequest#testRequestAddedToService fails in Ubuntu 14.04
[ https://issues.apache.org/jira/browse/NIFI-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619000#comment-14619000 ] ASF subversion and git services commented on NIFI-705: -- Commit df92dff8bb1ca0bdcebd5658aaae1234b2f5f209 in incubator-nifi's branch refs/heads/develop from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=df92dff ] NIFI-705 Preventing the processor from initializing each time it is waiting for the request. TestHandleHttpRequest#testRequestAddedToService fails in Ubuntu 14.04 - Key: NIFI-705 URL: https://issues.apache.org/jira/browse/NIFI-705 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.1.0, 0.2.0 Reporter: Aldrin Piri Assignee: Aldrin Piri Fix For: 0.2.0 Attachments: 0001-NIFI-705-Preventing-the-processor-from-initializing-.patch Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.675 sec FAILURE! - in org.apache.nifi.processors.standard.TestHandleHttpRequest testRequestAddedToService(org.apache.nifi.processors.standard.TestHandleHttpRequest) Time elapsed: 6.675 sec FAILURE! java.lang.AssertionError: Could not invoke methods annotated with @OnScheduled annotation due to: java.lang.reflect.InvocationTargetException at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:199) at org.apache.nifi.util.StandardProcessorTestRunner.run(StandardProcessorTestRunner.java:182) at org.apache.nifi.processors.standard.TestHandleHttpRequest.testRequestAddedToService(TestHandleHttpRequest.java:100) ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619192#comment-14619192 ] ASF subversion and git services commented on NIFI-656: -- Commit e4f51eac9d1b9eabbb091a9f2c3eb1fee453cfc6 in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating-rc1 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e4f51ea ] NIFI-656-RC1 prepare release nifi-0.2.0-incubating-RC1 Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619193#comment-14619193 ] ASF subversion and git services commented on NIFI-656: -- Commit de8ec6f92c85970b1665765e0b11d04e486cc966 in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating-rc1 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=de8ec6f ] NIFI-656-RC1 prepare for next development iteration Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14617049#comment-14617049 ] ASF subversion and git services commented on NIFI-656: -- Commit fbd0a9f2482b242676c970b25fd91d642c2617de in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating-rc1 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=fbd0a9f ] NIFI-656-RC1 prepare for next development iteration Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-656) Release Manager: Release 0.2.0
[ https://issues.apache.org/jira/browse/NIFI-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14617048#comment-14617048 ] ASF subversion and git services commented on NIFI-656: -- Commit 19bdb1722eca1e569a44ee14b365170a771a29b8 in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating-rc1 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=19bdb17 ] NIFI-656-RC1 prepare release nifi-0.2.0-incubating-RC1 Release Manager: Release 0.2.0 -- Key: NIFI-656 URL: https://issues.apache.org/jira/browse/NIFI-656 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Joseph Witt Assignee: Matt Gilman Fix For: 0.2.0 This is a ticket to track general commits needed to conduct the release management activities themselves. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-753) NPE when reading in provenance data
[ https://issues.apache.org/jira/browse/NIFI-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14617785#comment-14617785 ] ASF subversion and git services commented on NIFI-753: -- Commit c0f110467997d1e05e58ef444385478ba05a59e5 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c0f1104 ] NIFI-753: when truncating value, take null values into account NPE when reading in provenance data --- Key: NIFI-753 URL: https://issues.apache.org/jira/browse/NIFI-753 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.2.0 Reporter: Mark Payne Assignee: Mark Payne Priority: Blocker Fix For: 0.2.0 Attachments: 0001-NIFI-753-when-truncating-value-take-null-values-into.patch If an attribute is removed, NiFi will fail to restart: Caused by: java.lang.RuntimeException: Unable to create Provenance Repository at org.apache.nifi.controller.FlowController.init(FlowController.java:411) ~[na:na] at org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:350) ~[na:na] at org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:63) ~[na:na] at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168) ~[na:na] ... 130 common frames omitted Caused by: java.lang.NullPointerException: null at org.apache.nifi.provenance.StandardRecordReader.readAttributes(StandardRecordReader.java:372) ~[na:na] at org.apache.nifi.provenance.StandardRecordReader.nextRecord(StandardRecordReader.java:313) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.mergeJournals(PersistentProvenanceRepository.java:1356) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.recoverJournalFiles(PersistentProvenanceRepository.java:1136) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.recover(PersistentProvenanceRepository.java:572) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.initialize(PersistentProvenanceRepository.java:212) ~[na:na] at org.apache.nifi.controller.FlowController.init(FlowController.java:407) ~[na:na] ... 133 common frames omitted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-753) NPE when reading in provenance data
[ https://issues.apache.org/jira/browse/NIFI-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14617806#comment-14617806 ] ASF subversion and git services commented on NIFI-753: -- Commit c0f110467997d1e05e58ef444385478ba05a59e5 in incubator-nifi's branch refs/heads/release-nifi-0.2.0-incubating from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c0f1104 ] NIFI-753: when truncating value, take null values into account NPE when reading in provenance data --- Key: NIFI-753 URL: https://issues.apache.org/jira/browse/NIFI-753 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.2.0 Reporter: Mark Payne Assignee: Mark Payne Priority: Blocker Fix For: 0.2.0 Attachments: 0001-NIFI-753-when-truncating-value-take-null-values-into.patch If an attribute is removed, NiFi will fail to restart: Caused by: java.lang.RuntimeException: Unable to create Provenance Repository at org.apache.nifi.controller.FlowController.init(FlowController.java:411) ~[na:na] at org.apache.nifi.controller.FlowController.createStandaloneInstance(FlowController.java:350) ~[na:na] at org.apache.nifi.spring.FlowControllerFactoryBean.getObject(FlowControllerFactoryBean.java:63) ~[na:na] at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:168) ~[na:na] ... 130 common frames omitted Caused by: java.lang.NullPointerException: null at org.apache.nifi.provenance.StandardRecordReader.readAttributes(StandardRecordReader.java:372) ~[na:na] at org.apache.nifi.provenance.StandardRecordReader.nextRecord(StandardRecordReader.java:313) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.mergeJournals(PersistentProvenanceRepository.java:1356) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.recoverJournalFiles(PersistentProvenanceRepository.java:1136) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.recover(PersistentProvenanceRepository.java:572) ~[na:na] at org.apache.nifi.provenance.PersistentProvenanceRepository.initialize(PersistentProvenanceRepository.java:212) ~[na:na] at org.apache.nifi.controller.FlowController.init(FlowController.java:407) ~[na:na] ... 133 common frames omitted -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-735) DocGenerator should call @OnShutdown after its done generating the docs
[ https://issues.apache.org/jira/browse/NIFI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616088#comment-14616088 ] ASF subversion and git services commented on NIFI-735: -- Commit bd9782cb43ece682c853d9a75279ebe76f968044 in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=bd9782c ] NIFI-735: DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs DocGenerator should call @OnShutdown after its done generating the docs --- Key: NIFI-735 URL: https://issues.apache.org/jira/browse/NIFI-735 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch Per [~mcgilman] +0 for triggering OnRemoved and OnShutdown after initialization and before being done with instance +0 for triggering OnRemoved and OnShutdown and not their deprecated counterparts Change code to call annotations *after* the documentation has been generated for that component. Also invoke both the new annotations and the deprecated annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-735) DocGenerator should call @OnShutdown after its done generating the docs
[ https://issues.apache.org/jira/browse/NIFI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616089#comment-14616089 ] ASF subversion and git services commented on NIFI-735: -- Commit 93546760be2223f40215a0aeb9614dbb9bdb148f in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=9354676 ] Merge branch 'develop' into NIFI-735 DocGenerator should call @OnShutdown after its done generating the docs --- Key: NIFI-735 URL: https://issues.apache.org/jira/browse/NIFI-735 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch Per [~mcgilman] +0 for triggering OnRemoved and OnShutdown after initialization and before being done with instance +0 for triggering OnRemoved and OnShutdown and not their deprecated counterparts Change code to call annotations *after* the documentation has been generated for that component. Also invoke both the new annotations and the deprecated annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-735) DocGenerator should call @OnShutdown after its done generating the docs
[ https://issues.apache.org/jira/browse/NIFI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616090#comment-14616090 ] ASF subversion and git services commented on NIFI-735: -- Commit c769742d9b10145c26a0b6cd75b9ae75bbdc9589 in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c769742 ] NIFI-735: removing call to OnRemoved and updating unit tests DocGenerator should call @OnShutdown after its done generating the docs --- Key: NIFI-735 URL: https://issues.apache.org/jira/browse/NIFI-735 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch Per [~mcgilman] +0 for triggering OnRemoved and OnShutdown after initialization and before being done with instance +0 for triggering OnRemoved and OnShutdown and not their deprecated counterparts Change code to call annotations *after* the documentation has been generated for that component. Also invoke both the new annotations and the deprecated annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-735) DocGenerator should call @OnShutdown after its done generating the docs
[ https://issues.apache.org/jira/browse/NIFI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616091#comment-14616091 ] ASF subversion and git services commented on NIFI-735: -- Commit 9fa03b43245cfba27fe084ac46b44f39856dbcbb in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=9fa03b4 ] Merge branch 'NIFI-735' into develop DocGenerator should call @OnShutdown after its done generating the docs --- Key: NIFI-735 URL: https://issues.apache.org/jira/browse/NIFI-735 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch Per [~mcgilman] +0 for triggering OnRemoved and OnShutdown after initialization and before being done with instance +0 for triggering OnRemoved and OnShutdown and not their deprecated counterparts Change code to call annotations *after* the documentation has been generated for that component. Also invoke both the new annotations and the deprecated annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-750) NiFi Storm Spout should allow FlowFile attributes to be put into Tuple values
[ https://issues.apache.org/jira/browse/NIFI-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14614047#comment-14614047 ] ASF subversion and git services commented on NIFI-750: -- Commit 0d2842e4f9df2c1734c409d80511601765d8dc1b in incubator-nifi's branch refs/heads/develop from [~bbende] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0d2842e ] NIFI-750 adding a way to specify attribute names when constructing the spout NiFi Storm Spout should allow FlowFile attributes to be put into Tuple values - Key: NIFI-750 URL: https://issues.apache.org/jira/browse/NIFI-750 Project: Apache NiFi Issue Type: Improvement Reporter: Bryan Bende Assignee: Bryan Bende Priority: Minor Fix For: 0.2.0 Attachments: NIFI-750.patch It would be helpful if the NiFiSpout provided a way to take FlowFile attributes and place them into individual values in each Tuple. This would help when connecting bolts to the spout using a field grouping where all tuples with the same value for a given field will be sent to the same bolt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-679) InvokeHTTP - Add support for basic authentication
[ https://issues.apache.org/jira/browse/NIFI-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613178#comment-14613178 ] ASF subversion and git services commented on NIFI-679: -- Commit 9d6458ab2800add00312e129bf60cd04ead350f9 in incubator-nifi's branch refs/heads/develop from [~jskora] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=9d6458a ] NIFI-679: Incorporate Basic Authentication handling into InvokeHTTP processor. Signed-off-by: Matt Gilman matt.c.gil...@gmail.com InvokeHTTP - Add support for basic authentication - Key: NIFI-679 URL: https://issues.apache.org/jira/browse/NIFI-679 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Matt Gilman Priority: Minor Fix For: 0.2.0 Attachments: nifi-679.patch InvokeHTTP should optionally support username/password for web services that do not employ certificate based authentication. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-733) GetKafka group identifier is ignored
[ https://issues.apache.org/jira/browse/NIFI-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613188#comment-14613188 ] ASF subversion and git services commented on NIFI-733: -- Commit 786bc1d61260e2d8558747ca206d360aebdd1994 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=786bc1d ] NIFI-733: Make use of Client Name, Zookeeper Timeout, Kafka Timeout properties and add new Group ID property GetKafka group identifier is ignored Key: NIFI-733 URL: https://issues.apache.org/jira/browse/NIFI-733 Project: Apache NiFi Issue Type: Bug Components: Extensions Reporter: Joseph Witt Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-733-Make-use-of-Client-Name-Zookeeper-Timeout-K.patch A NiFi user reported that the GetKafka processor has a group identifier feature that doesn't work as expected. After initial code review it appears the group identifier property that a user can set is ignored which appears to be a bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-472) When running NiFi with the run.as property specified in the bootstrap.conf file, the run.as user should own the nifi.pid file
[ https://issues.apache.org/jira/browse/NIFI-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613223#comment-14613223 ] ASF subversion and git services commented on NIFI-472: -- Commit 136974af7c63bdb8c4c99c1a02c6b34011e2e17f in incubator-nifi's branch refs/heads/develop from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=136974a ] NIFI-472: Refining the mechanism to carry out running as a different user pushing the handling of this primarily to the controlling script rather than the Java code. Making changes to the assembly such that permissions are provided on a group level control basis. When running NiFi with the run.as property specified in the bootstrap.conf file, the run.as user should own the nifi.pid file --- Key: NIFI-472 URL: https://issues.apache.org/jira/browse/NIFI-472 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Aldrin Piri Fix For: 0.2.0 Attachments: 0001-NIFI-472-Refining-the-mechanism-to-carry-out-running.patch Currently, if I set the run.as user to something like nifi and then I run bin/nifi.sh start, a file named nifi.pid is created in the bin/ directory, but it is owned by me. It should instead be owned by the run.as user (nifi). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-749) Unit tests fail on Windows for InvokeHTTP
[ https://issues.apache.org/jira/browse/NIFI-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613307#comment-14613307 ] ASF subversion and git services commented on NIFI-749: -- Commit 74b48009376e950bfa455be31e15f13cde7d27b9 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=74b4800 ] NIFI-749: Ignore line endings in unit test Unit tests fail on Windows for InvokeHTTP - Key: NIFI-749 URL: https://issues.apache.org/jira/browse/NIFI-749 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.2.0 Reporter: Mark Payne Priority: Blocker Fix For: 0.2.0 Attachments: 0001-NIFI-749-Ignore-line-endings-in-unit-test.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-717) nifi-bootstrap.log written to directory relative to current working directory
[ https://issues.apache.org/jira/browse/NIFI-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613356#comment-14613356 ] ASF subversion and git services commented on NIFI-717: -- Commit a2b9d70ac43f6f3162abb7706f9021ce3e3993f0 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=a2b9d70 ] NIFI-717: Set working directory to $NIFI_HOME before running starting nifi in linux nifi-bootstrap.log written to directory relative to current working directory - Key: NIFI-717 URL: https://issues.apache.org/jira/browse/NIFI-717 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Priority: Minor Fix For: 0.2.0 Attachments: 0001-NIFI-717-Set-working-directory-to-NIFI_HOME-before-r.patch It appears that nifi-bootstrap.log is written to a directory that is relative to the current working directory. If NiFi is launched from outside $NIFI_HOME the logs end up outside of $NIFI_HOME. It is confusing since its configured to be written to logs/ just like nifi-app.log and nifi-user.log but it is written to logs/ in a different location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-717) nifi-bootstrap.log written to directory relative to current working directory
[ https://issues.apache.org/jira/browse/NIFI-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613357#comment-14613357 ] ASF subversion and git services commented on NIFI-717: -- Commit f3b55d46d6a374ee27b2decb3ee7284fd294a10d in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=f3b55d4 ] Merge branch 'NIFI-717' into develop nifi-bootstrap.log written to directory relative to current working directory - Key: NIFI-717 URL: https://issues.apache.org/jira/browse/NIFI-717 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Priority: Minor Fix For: 0.2.0 Attachments: 0001-NIFI-717-Set-working-directory-to-NIFI_HOME-before-r.patch It appears that nifi-bootstrap.log is written to a directory that is relative to the current working directory. If NiFi is launched from outside $NIFI_HOME the logs end up outside of $NIFI_HOME. It is confusing since its configured to be written to logs/ just like nifi-app.log and nifi-user.log but it is written to logs/ in a different location. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-743) .getSolr-mock-processor and .httpCache-mock-processor files in conf dir
[ https://issues.apache.org/jira/browse/NIFI-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613351#comment-14613351 ] ASF subversion and git services commented on NIFI-743: -- Commit 63a900852769bbd7bedc2b460a291a9de0bd9a15 in incubator-nifi's branch refs/heads/develop from [~bbende] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=63a9008 ] NIFI-743 Moving OnShutdown to OnStopped for GetSolr and GetHttp Adding OnRemoved methods to GetSolr and GetHttp Signed-off-by: Mark Payne marka...@hotmail.com .getSolr-mock-processor and .httpCache-mock-processor files in conf dir --- Key: NIFI-743 URL: https://issues.apache.org/jira/browse/NIFI-743 Project: Apache NiFi Issue Type: Bug Components: Tools and Build Reporter: Mark Payne Assignee: Bryan Bende Fix For: 0.2.0 Attachments: NIFI-743-2.patch, NIFI-743.patch I'm not sure where these are coming from but when I do a clean build, I'm ending up with 2 files in the conf/ directory that shouldn't be there: .httpCache-mock-processor and .getSolr-mock-processor. Not sure if these were created when I did the build or when I launched the application, but either way they shouldn't be there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-745) Disabling Controller Service stuck
[ https://issues.apache.org/jira/browse/NIFI-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613406#comment-14613406 ] ASF subversion and git services commented on NIFI-745: -- Commit 208402472dd99c629afc056f4464b925b8f834ab in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=2084024 ] NIFI-745: Only call methods with @OnDisabled once, regardless of whether or not they succeed Disabling Controller Service stuck -- Key: NIFI-745 URL: https://issues.apache.org/jira/browse/NIFI-745 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Fix For: 0.2.0 Attachments: 0001-NIFI-745-Only-call-methods-with-OnDisabled-once-rega.patch Per the nifi-api a controller service OnDisable method will be invoked when the user disables that service. If that method fails with an exception it will be retried a short time later. This will continue until it successfully completes. Unfortunately, this means that if services continually throws an exception during OnDisable the user will not be able to do anything with the service. This is because controller services need to be Disabled in order to support editing its configuration or attempting to Enable. The service in question will not transition to the Disabled state until its OnDisable completes without issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-685) Proxy Support for GetHTTP and PostHTTP processors
[ https://issues.apache.org/jira/browse/NIFI-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613320#comment-14613320 ] ASF subversion and git services commented on NIFI-685: -- Commit 2a4e5e12855364c6d4b14f1ef1445e08d1f4fe08 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=2a4e5e1 ] NIFI-685: Fixed checkstyle violation of using import with * Proxy Support for GetHTTP and PostHTTP processors - Key: NIFI-685 URL: https://issues.apache.org/jira/browse/NIFI-685 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 0.2.0 Reporter: Andrew Hulbert Priority: Minor Fix For: 0.2.0 Add http web proxy support to GetHTTP and PostHTTP processors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-720) If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start
[ https://issues.apache.org/jira/browse/NIFI-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613329#comment-14613329 ] ASF subversion and git services commented on NIFI-720: -- Commit 8da7327188ebdb3cbadda257429e4967be07bf77 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=8da7327 ] NIFI-720: Ensure that if Reporting Task stopped while @OnScheduled method is failing that it does not start running when configuration is fixed If Reporting Task fails to start properly and is then stopped, it can continue to run once it is able to start -- Key: NIFI-720 URL: https://issues.apache.org/jira/browse/NIFI-720 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-720-Ensure-that-if-Reporting-Task-stopped-while.patch Steps to replicate: Create a MonitorMemory reporting task. Set an invalid value for the Memory Pool Start the reporting task See that errors are logged indicating that it couldn't start properly Stop Reporting Task Change Memory Pool to a valid value MonitorMemory will begin to run. Clicking Start will cause two threads to now run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-694) If Enabling Controller Service fails, no indication is provided to user
[ https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612010#comment-14612010 ] ASF subversion and git services commented on NIFI-694: -- Commit c3dff409024d00208c68323ad1989bd2b93b7c0c in incubator-nifi's branch refs/heads/NIFI-724 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c3dff40 ] NIFI-694: - Ensuring bulletins are not lost when updating a reporting task. If Enabling Controller Service fails, no indication is provided to user --- Key: NIFI-694 URL: https://issues.apache.org/jira/browse/NIFI-694 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Mark Payne Fix For: 0.2.0 To replicate the issue: 1. Add a DBCPService controller service. 2. Configure service. For the Driver Url use file://tmp/non-existent-file or use an invalid Driver Class Name. 3. Click Apply. 4. Click Enable. The UI will show the spinner indefinitely, as the service will keep failing to enable because it throws Exceptions from its @OnEnabled method. The UI should provide some sort of indication that this is occurring. Otherwise, it appears to the user that the system is non-responsive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-724) Controller Services and Reporting Tasks should be able to emit bulletins
[ https://issues.apache.org/jira/browse/NIFI-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612501#comment-14612501 ] ASF subversion and git services commented on NIFI-724: -- Commit eddc071b8efc3c6ca86e373b56f214514b2abd0a in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=eddc071 ] Merge branch 'develop' into NIFI-724 Controller Services and Reporting Tasks should be able to emit bulletins Key: NIFI-724 URL: https://issues.apache.org/jira/browse/NIFI-724 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-724) Controller Services and Reporting Tasks should be able to emit bulletins
[ https://issues.apache.org/jira/browse/NIFI-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612497#comment-14612497 ] ASF subversion and git services commented on NIFI-724: -- Commit e7c0461b15bff045d68e7ae8814eda2073cba209 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e7c0461 ] NIFI-724: Ensure that bulletins generated for reporting tasks and controller services are shown at Controller level as well as component level Controller Services and Reporting Tasks should be able to emit bulletins Key: NIFI-724 URL: https://issues.apache.org/jira/browse/NIFI-724 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-695) Cancel Enable/Disable controller service should provide immediate feedback to user
[ https://issues.apache.org/jira/browse/NIFI-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612500#comment-14612500 ] ASF subversion and git services commented on NIFI-695: -- Commit 566c4fe8d78b769fc31c8d5bed90daccbc817e27 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=566c4fe ] NIFI-695: - Providing immediate feedback when canceling a request to [en|dis]able a controller service. - Reporting to the user after a request has been canceled. Cancel Enable/Disable controller service should provide immediate feedback to user -- Key: NIFI-695 URL: https://issues.apache.org/jira/browse/NIFI-695 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Priority: Minor Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-694) If Enabling Controller Service fails, no indication is provided to user
[ https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612498#comment-14612498 ] ASF subversion and git services commented on NIFI-694: -- Commit 4fd1e9494e41bea198dabedacee16ed018a3a7b7 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=4fd1e94 ] NIFI-694: - Fixing bug when clearing bulletins from the reporting task table. - Allowed ENABLING state to trigger transition to next step of the enable/disable request. If Enabling Controller Service fails, no indication is provided to user --- Key: NIFI-694 URL: https://issues.apache.org/jira/browse/NIFI-694 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Mark Payne Fix For: 0.2.0 To replicate the issue: 1. Add a DBCPService controller service. 2. Configure service. For the Driver Url use file://tmp/non-existent-file or use an invalid Driver Class Name. 3. Click Apply. 4. Click Enable. The UI will show the spinner indefinitely, as the service will keep failing to enable because it throws Exceptions from its @OnEnabled method. The UI should provide some sort of indication that this is occurring. Otherwise, it appears to the user that the system is non-responsive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-694) If Enabling Controller Service fails, no indication is provided to user
[ https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612499#comment-14612499 ] ASF subversion and git services commented on NIFI-694: -- Commit c3dff409024d00208c68323ad1989bd2b93b7c0c in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c3dff40 ] NIFI-694: - Ensuring bulletins are not lost when updating a reporting task. If Enabling Controller Service fails, no indication is provided to user --- Key: NIFI-694 URL: https://issues.apache.org/jira/browse/NIFI-694 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Mark Payne Fix For: 0.2.0 To replicate the issue: 1. Add a DBCPService controller service. 2. Configure service. For the Driver Url use file://tmp/non-existent-file or use an invalid Driver Class Name. 3. Click Apply. 4. Click Enable. The UI will show the spinner indefinitely, as the service will keep failing to enable because it throws Exceptions from its @OnEnabled method. The UI should provide some sort of indication that this is occurring. Otherwise, it appears to the user that the system is non-responsive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-741) link to contributor guide from landing page
[ https://issues.apache.org/jira/browse/NIFI-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612837#comment-14612837 ] ASF subversion and git services commented on NIFI-741: -- Commit 1688943 from [~aldrin] in branch 'site/trunk' [ https://svn.apache.org/r1688943 ] NIFI-741 Adding Contributor Guide link to the Community section of the navigation link to contributor guide from landing page --- Key: NIFI-741 URL: https://issues.apache.org/jira/browse/NIFI-741 Project: Apache NiFi Issue Type: Task Components: Documentation Website Reporter: Sean Busbey Assignee: Aldrin Piri I tried finding the contributor guide while responding to a mailing list question and the closest I got was a small bit at the end of our dev guide: http://nifi.incubator.apache.org/docs/nifi-docs/html/developer-guide.html#how-to-contribute-to-apache-nifi Later Joe pointed to the actual contrib guide on the wiki: https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide we should link to this document from the community tab (or maybe development? I'd favor community) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-741) link to contributor guide from landing page
[ https://issues.apache.org/jira/browse/NIFI-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612834#comment-14612834 ] ASF subversion and git services commented on NIFI-741: -- Commit 063afe2a0dfbd7d256ad6e1df07886013f6b9503 in incubator-nifi's branch refs/heads/develop from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=063afe2 ] NIFI-741: Adding a link to the contributor guide in the Community section of navigation. link to contributor guide from landing page --- Key: NIFI-741 URL: https://issues.apache.org/jira/browse/NIFI-741 Project: Apache NiFi Issue Type: Task Components: Documentation Website Reporter: Sean Busbey Assignee: Aldrin Piri I tried finding the contributor guide while responding to a mailing list question and the closest I got was a small bit at the end of our dev guide: http://nifi.incubator.apache.org/docs/nifi-docs/html/developer-guide.html#how-to-contribute-to-apache-nifi Later Joe pointed to the actual contrib guide on the wiki: https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide we should link to this document from the community tab (or maybe development? I'd favor community) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-695) Cancel Enable/Disable controller service should provide immediate feedback to user
[ https://issues.apache.org/jira/browse/NIFI-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14612282#comment-14612282 ] ASF subversion and git services commented on NIFI-695: -- Commit 566c4fe8d78b769fc31c8d5bed90daccbc817e27 in incubator-nifi's branch refs/heads/NIFI-724 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=566c4fe ] NIFI-695: - Providing immediate feedback when canceling a request to [en|dis]able a controller service. - Reporting to the user after a request has been canceled. Cancel Enable/Disable controller service should provide immediate feedback to user -- Key: NIFI-695 URL: https://issues.apache.org/jira/browse/NIFI-695 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Priority: Minor Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-694) If Enabling Controller Service fails, no indication is provided to user
[ https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14610778#comment-14610778 ] ASF subversion and git services commented on NIFI-694: -- Commit 4fd1e9494e41bea198dabedacee16ed018a3a7b7 in incubator-nifi's branch refs/heads/NIFI-724 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=4fd1e94 ] NIFI-694: - Fixing bug when clearing bulletins from the reporting task table. - Allowed ENABLING state to trigger transition to next step of the enable/disable request. If Enabling Controller Service fails, no indication is provided to user --- Key: NIFI-694 URL: https://issues.apache.org/jira/browse/NIFI-694 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Mark Payne Fix For: 0.2.0 To replicate the issue: 1. Add a DBCPService controller service. 2. Configure service. For the Driver Url use file://tmp/non-existent-file or use an invalid Driver Class Name. 3. Click Apply. 4. Click Enable. The UI will show the spinner indefinitely, as the service will keep failing to enable because it throws Exceptions from its @OnEnabled method. The UI should provide some sort of indication that this is occurring. Otherwise, it appears to the user that the system is non-responsive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-724) Controller Services and Reporting Tasks should be able to emit bulletins
[ https://issues.apache.org/jira/browse/NIFI-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14610629#comment-14610629 ] ASF subversion and git services commented on NIFI-724: -- Commit e7c0461b15bff045d68e7ae8814eda2073cba209 in incubator-nifi's branch refs/heads/NIFI-724 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e7c0461 ] NIFI-724: Ensure that bulletins generated for reporting tasks and controller services are shown at Controller level as well as component level Controller Services and Reporting Tasks should be able to emit bulletins Key: NIFI-724 URL: https://issues.apache.org/jira/browse/NIFI-724 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-719) For Reporting Tasks, ConfigurationContext should provide scheduling information
[ https://issues.apache.org/jira/browse/NIFI-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14610493#comment-14610493 ] ASF subversion and git services commented on NIFI-719: -- Commit a09180799d8a84108c3f5665668bded284768ecf in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=a091807 ] NIFI-719: merged with develop For Reporting Tasks, ConfigurationContext should provide scheduling information Key: NIFI-719 URL: https://issues.apache.org/jira/browse/NIFI-719 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-719-Expose-scheduling-period-to-the-Configurati.patch Currently the ConfigurationContext does not provide any information about scheduling, as it was originally designed for Controller Services. However, it is used also for Reporting Tasks, and should have methods Long getSchedulingPeriod(TimeUnit timeUnit) and String getSchedulingPeriod() as the ReportingInitializationContext does. These methods should return null for Controller Services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-719) For Reporting Tasks, ConfigurationContext should provide scheduling information
[ https://issues.apache.org/jira/browse/NIFI-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14610492#comment-14610492 ] ASF subversion and git services commented on NIFI-719: -- Commit ba3155980efd846b45bd47eefa14f503a13908f3 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=ba31559 ] NIFI-719: Expose scheduling period to the ConfigurationContext For Reporting Tasks, ConfigurationContext should provide scheduling information Key: NIFI-719 URL: https://issues.apache.org/jira/browse/NIFI-719 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-719-Expose-scheduling-period-to-the-Configurati.patch Currently the ConfigurationContext does not provide any information about scheduling, as it was originally designed for Controller Services. However, it is used also for Reporting Tasks, and should have methods Long getSchedulingPeriod(TimeUnit timeUnit) and String getSchedulingPeriod() as the ReportingInitializationContext does. These methods should return null for Controller Services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-731) If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic
[ https://issues.apache.org/jira/browse/NIFI-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608514#comment-14608514 ] ASF subversion and git services commented on NIFI-731: -- Commit 4b5ba3c4e9bbb2be5bd3f9bdf40159179a3b30e2 in incubator-nifi's branch refs/heads/NIFI-731 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=4b5ba3c ] NIFI-731: Try using a Stack to hold FLowFIle Repo partitions so that we tend to use the same partition to avoid disk seeks/thrashing If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic --- Key: NIFI-731 URL: https://issues.apache.org/jira/browse/NIFI-731 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 When the FlowFile Repository marks claims as destructable, it puts the notification on a queue that the content repo pulls from. If the content repo cannot keep up, the queue will fill, resulting in backpressure, that prevents the FlowFile repository from being updated. This, in turn, causes Processors to block, waiting on space to become available. This is by design. However, the capacity of this queue is quite large, and the content repo drains the entire queue, then destroys all content claims that are on it. As a result, this act of destroying claims can be quite long, and Processors can block for quite a period of time, leading to very sporadic performance. Instead, the content repo should pull from the queue and destroy the claims one at a time or in small batches, instead of draining the entire queue each time. This should result in much less sporadic behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-731) If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic
[ https://issues.apache.org/jira/browse/NIFI-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608777#comment-14608777 ] ASF subversion and git services commented on NIFI-731: -- Commit 94b4eddb00055fccbe57c5e3fb2ed93c0e91c153 in incubator-nifi's branch refs/heads/NIFI-731 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=94b4edd ] NIFI-731: fixed issue with how bulletins were emitted by content claim manager If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic --- Key: NIFI-731 URL: https://issues.apache.org/jira/browse/NIFI-731 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-731-Refactored-how-Content-and-FlowFile-Repos-i.patch When the FlowFile Repository marks claims as destructable, it puts the notification on a queue that the content repo pulls from. If the content repo cannot keep up, the queue will fill, resulting in backpressure, that prevents the FlowFile repository from being updated. This, in turn, causes Processors to block, waiting on space to become available. This is by design. However, the capacity of this queue is quite large, and the content repo drains the entire queue, then destroys all content claims that are on it. As a result, this act of destroying claims can be quite long, and Processors can block for quite a period of time, leading to very sporadic performance. Instead, the content repo should pull from the queue and destroy the claims one at a time or in small batches, instead of draining the entire queue each time. This should result in much less sporadic behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-731) If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic
[ https://issues.apache.org/jira/browse/NIFI-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608776#comment-14608776 ] ASF subversion and git services commented on NIFI-731: -- Commit b3eb4a1a0f29d0f94639174dfbd7ea05307cb99a in incubator-nifi's branch refs/heads/NIFI-731 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=b3eb4a1 ] Revert NIFI-731: Try using a Stack to hold FLowFIle Repo partitions so that we tend to use the same partition to avoid disk seeks/thrashing This reverts commit 4b5ba3c4e9bbb2be5bd3f9bdf40159179a3b30e2. If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic --- Key: NIFI-731 URL: https://issues.apache.org/jira/browse/NIFI-731 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-731-Refactored-how-Content-and-FlowFile-Repos-i.patch When the FlowFile Repository marks claims as destructable, it puts the notification on a queue that the content repo pulls from. If the content repo cannot keep up, the queue will fill, resulting in backpressure, that prevents the FlowFile repository from being updated. This, in turn, causes Processors to block, waiting on space to become available. This is by design. However, the capacity of this queue is quite large, and the content repo drains the entire queue, then destroys all content claims that are on it. As a result, this act of destroying claims can be quite long, and Processors can block for quite a period of time, leading to very sporadic performance. Instead, the content repo should pull from the queue and destroy the claims one at a time or in small batches, instead of draining the entire queue each time. This should result in much less sporadic behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-731) If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic
[ https://issues.apache.org/jira/browse/NIFI-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608775#comment-14608775 ] ASF subversion and git services commented on NIFI-731: -- Commit 1677db6261c2c77df15c2e46a54d7428fc91fc57 in incubator-nifi's branch refs/heads/NIFI-731 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=1677db6 ] NIFI-731: Deleted unused method If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic --- Key: NIFI-731 URL: https://issues.apache.org/jira/browse/NIFI-731 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-731-Refactored-how-Content-and-FlowFile-Repos-i.patch When the FlowFile Repository marks claims as destructable, it puts the notification on a queue that the content repo pulls from. If the content repo cannot keep up, the queue will fill, resulting in backpressure, that prevents the FlowFile repository from being updated. This, in turn, causes Processors to block, waiting on space to become available. This is by design. However, the capacity of this queue is quite large, and the content repo drains the entire queue, then destroys all content claims that are on it. As a result, this act of destroying claims can be quite long, and Processors can block for quite a period of time, leading to very sporadic performance. Instead, the content repo should pull from the queue and destroy the claims one at a time or in small batches, instead of draining the entire queue each time. This should result in much less sporadic behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-694) If Enabling Controller Service fails, no indication is provided to user
[ https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608787#comment-14608787 ] ASF subversion and git services commented on NIFI-694: -- Commit 59aa8ffe100645498fdd4cea2214a203e3a3d433 in incubator-nifi's branch refs/heads/NIFI-724 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=59aa8ff ] NIFI-694: - Showing bulletins in the controller service and reporting task tables. - Fixed issue typo when emitting controller service bulletins. If Enabling Controller Service fails, no indication is provided to user --- Key: NIFI-694 URL: https://issues.apache.org/jira/browse/NIFI-694 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Mark Payne Fix For: 0.2.0 To replicate the issue: 1. Add a DBCPService controller service. 2. Configure service. For the Driver Url use file://tmp/non-existent-file or use an invalid Driver Class Name. 3. Click Apply. 4. Click Enable. The UI will show the spinner indefinitely, as the service will keep failing to enable because it throws Exceptions from its @OnEnabled method. The UI should provide some sort of indication that this is occurring. Otherwise, it appears to the user that the system is non-responsive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-738) Do not write conversion error messages to flow file content
[ https://issues.apache.org/jira/browse/NIFI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14606865#comment-14606865 ] ASF subversion and git services commented on NIFI-738: -- Commit 50215707f7e4ab2207041ed1e31e7ba2d88de7b4 in incubator-nifi's branch refs/heads/develop from [~joewitt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=5021570 ] This closes #69 NIFI-738 Do not write conversion error messages to flow file content --- Key: NIFI-738 URL: https://issues.apache.org/jira/browse/NIFI-738 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.1.0 Reporter: Ryan Blue Assignee: Ryan Blue Fix For: 0.2.0 NIFI-551 extended the error handling provided by the ConvertJSONToAvro processor, but wrote error messages as the content of a file sent on the failure relationship. I think the right thing to do is to output the bad records as the file content and put the error messages in the outgoing attributes. NIFI-551 wasn't included in 0.1.0, so changing this behavior is safe. Consequently, I'd like to get this fix into 0.2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-738) Do not write conversion error messages to flow file content
[ https://issues.apache.org/jira/browse/NIFI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14606857#comment-14606857 ] ASF subversion and git services commented on NIFI-738: -- Commit 2e32e0e2b82e071734919589ed680513edfd39ed in incubator-nifi's branch refs/heads/develop from [~b...@cloudera.com] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=2e32e0e ] NIFI-738: Improve error handling for CSV and JSON conversion. Changes: * Send bad record information on the incompatible relationship * Use an attribute, errors for summarized error messages * Send no error content for now, original content can't be accessed * Summarize similar error messages with N similar failures * Add similar error handling to CSV conversion Signed-off-by: joewitt joew...@apache.org Do not write conversion error messages to flow file content --- Key: NIFI-738 URL: https://issues.apache.org/jira/browse/NIFI-738 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.1.0 Reporter: Ryan Blue Assignee: Ryan Blue Fix For: 0.2.0 NIFI-551 extended the error handling provided by the ConvertJSONToAvro processor, but wrote error messages as the content of a file sent on the failure relationship. I think the right thing to do is to output the bad records as the file content and put the error messages in the outgoing attributes. NIFI-551 wasn't included in 0.1.0, so changing this behavior is safe. Consequently, I'd like to get this fix into 0.2.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-737) Typo in developer guide 'lot message'
[ https://issues.apache.org/jira/browse/NIFI-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604865#comment-14604865 ] ASF subversion and git services commented on NIFI-737: -- Commit 846d2f4472edd0795f1647686821576669ee1cb3 in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=846d2f4 ] NIFI-737: Typo in developer guide 'lot message' Typo in developer guide 'lot message' - Key: NIFI-737 URL: https://issues.apache.org/jira/browse/NIFI-737 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Priority: Trivial Fix For: 0.2.0 Attachments: 0001-NIFI-737-Typo-in-developer-guide-lot-message.patch [The Developer Guide|https://nifi.incubator.apache.org/docs/nifi-docs/html/developer-guide.html#onshutdown] has a typo: _If such a method throws an Exception, a *lot* message will be generated, and the Exception will otherwise be ignored; other methods with this annotation will still be invoked. Methods with this annotation must take zero arguments._ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-737) Typo in developer guide 'lot message'
[ https://issues.apache.org/jira/browse/NIFI-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604866#comment-14604866 ] ASF subversion and git services commented on NIFI-737: -- Commit 4dc2ea6d477ca0c03d78c42e8958e0af58e084be in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=4dc2ea6 ] Merge branch 'NIFI-737' into develop Typo in developer guide 'lot message' - Key: NIFI-737 URL: https://issues.apache.org/jira/browse/NIFI-737 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Priority: Trivial Fix For: 0.2.0 Attachments: 0001-NIFI-737-Typo-in-developer-guide-lot-message.patch [The Developer Guide|https://nifi.incubator.apache.org/docs/nifi-docs/html/developer-guide.html#onshutdown] has a typo: _If such a method throws an Exception, a *lot* message will be generated, and the Exception will otherwise be ignored; other methods with this annotation will still be invoked. Methods with this annotation must take zero arguments._ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-735) DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs
[ https://issues.apache.org/jira/browse/NIFI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604906#comment-14604906 ] ASF subversion and git services commented on NIFI-735: -- Commit 93546760be2223f40215a0aeb9614dbb9bdb148f in incubator-nifi's branch refs/heads/NIFI-735 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=9354676 ] Merge branch 'develop' into NIFI-735 DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs --- Key: NIFI-735 URL: https://issues.apache.org/jira/browse/NIFI-735 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Fix For: 0.2.0 Attachments: 0001-NIFI-735-DocGenerator-should-on-OnUnscheduled-and-On.patch Per [~mcgilman] +0 for triggering OnRemoved and OnShutdown after initialization and before being done with instance +0 for triggering OnRemoved and OnShutdown and not their deprecated counterparts Change code to call annotations *after* the documentation has been generated for that component. Also invoke both the new annotations and the deprecated annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-737) Typo in developer guide 'lot message'
[ https://issues.apache.org/jira/browse/NIFI-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604904#comment-14604904 ] ASF subversion and git services commented on NIFI-737: -- Commit 846d2f4472edd0795f1647686821576669ee1cb3 in incubator-nifi's branch refs/heads/NIFI-735 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=846d2f4 ] NIFI-737: Typo in developer guide 'lot message' Typo in developer guide 'lot message' - Key: NIFI-737 URL: https://issues.apache.org/jira/browse/NIFI-737 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Priority: Trivial Fix For: 0.2.0 Attachments: 0001-NIFI-737-Typo-in-developer-guide-lot-message.patch [The Developer Guide|https://nifi.incubator.apache.org/docs/nifi-docs/html/developer-guide.html#onshutdown] has a typo: _If such a method throws an Exception, a *lot* message will be generated, and the Exception will otherwise be ignored; other methods with this annotation will still be invoked. Methods with this annotation must take zero arguments._ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-735) DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs
[ https://issues.apache.org/jira/browse/NIFI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604907#comment-14604907 ] ASF subversion and git services commented on NIFI-735: -- Commit c769742d9b10145c26a0b6cd75b9ae75bbdc9589 in incubator-nifi's branch refs/heads/NIFI-735 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c769742 ] NIFI-735: removing call to OnRemoved and updating unit tests DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs --- Key: NIFI-735 URL: https://issues.apache.org/jira/browse/NIFI-735 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Fix For: 0.2.0 Attachments: 0001-NIFI-735-DocGenerator-should-on-OnUnscheduled-and-On.patch Per [~mcgilman] +0 for triggering OnRemoved and OnShutdown after initialization and before being done with instance +0 for triggering OnRemoved and OnShutdown and not their deprecated counterparts Change code to call annotations *after* the documentation has been generated for that component. Also invoke both the new annotations and the deprecated annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-737) Typo in developer guide 'lot message'
[ https://issues.apache.org/jira/browse/NIFI-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604905#comment-14604905 ] ASF subversion and git services commented on NIFI-737: -- Commit 4dc2ea6d477ca0c03d78c42e8958e0af58e084be in incubator-nifi's branch refs/heads/NIFI-735 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=4dc2ea6 ] Merge branch 'NIFI-737' into develop Typo in developer guide 'lot message' - Key: NIFI-737 URL: https://issues.apache.org/jira/browse/NIFI-737 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Priority: Trivial Fix For: 0.2.0 Attachments: 0001-NIFI-737-Typo-in-developer-guide-lot-message.patch [The Developer Guide|https://nifi.incubator.apache.org/docs/nifi-docs/html/developer-guide.html#onshutdown] has a typo: _If such a method throws an Exception, a *lot* message will be generated, and the Exception will otherwise be ignored; other methods with this annotation will still be invoked. Methods with this annotation must take zero arguments._ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-731) If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic
[ https://issues.apache.org/jira/browse/NIFI-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604801#comment-14604801 ] ASF subversion and git services commented on NIFI-731: -- Commit bb5128be2246dc48d5200e98572c47ff7cdfb905 in incubator-nifi's branch refs/heads/NIFI-731 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=bb5128b ] NIFI-731: Updated admin guide to explain the flowfile repo properties more; added new property for now often to 'sync' the flowfile repo; allowed number of partitions in flowfile repo to be changed after repo created. Minor tweaks to content repo and its communication with flowfile repo via ContentClaimManager If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic --- Key: NIFI-731 URL: https://issues.apache.org/jira/browse/NIFI-731 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 When the FlowFile Repository marks claims as destructable, it puts the notification on a queue that the content repo pulls from. If the content repo cannot keep up, the queue will fill, resulting in backpressure, that prevents the FlowFile repository from being updated. This, in turn, causes Processors to block, waiting on space to become available. This is by design. However, the capacity of this queue is quite large, and the content repo drains the entire queue, then destroys all content claims that are on it. As a result, this act of destroying claims can be quite long, and Processors can block for quite a period of time, leading to very sporadic performance. Instead, the content repo should pull from the queue and destroy the claims one at a time or in small batches, instead of draining the entire queue each time. This should result in much less sporadic behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-731) If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic
[ https://issues.apache.org/jira/browse/NIFI-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604800#comment-14604800 ] ASF subversion and git services commented on NIFI-731: -- Commit fb0a1a76f431148fa9664e565c94cf334498dbf8 in incubator-nifi's branch refs/heads/NIFI-731 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=fb0a1a7 ] NIFI-731: Merged develop to branch If content repo is unable to destroy content as fast as it is generated, nifi performance becomes very sporadic --- Key: NIFI-731 URL: https://issues.apache.org/jira/browse/NIFI-731 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 When the FlowFile Repository marks claims as destructable, it puts the notification on a queue that the content repo pulls from. If the content repo cannot keep up, the queue will fill, resulting in backpressure, that prevents the FlowFile repository from being updated. This, in turn, causes Processors to block, waiting on space to become available. This is by design. However, the capacity of this queue is quite large, and the content repo drains the entire queue, then destroys all content claims that are on it. As a result, this act of destroying claims can be quite long, and Processors can block for quite a period of time, leading to very sporadic performance. Instead, the content repo should pull from the queue and destroy the claims one at a time or in small batches, instead of draining the entire queue each time. This should result in much less sporadic behavior. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604277#comment-14604277 ] ASF subversion and git services commented on NIFI-632: -- Commit 8f36ba1ab417bdd6f6d3c3884e4abf750c5ea226 in incubator-nifi's branch refs/heads/develop from [~joewitt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=8f36ba1 ] NIFI-632 fixed versioning issue Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604284#comment-14604284 ] ASF subversion and git services commented on NIFI-632: -- Commit e35f348b831f5a27960d0d2dec4787860941fe29 in incubator-nifi's branch refs/heads/develop from [~joewitt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e35f348 ] NIFI-632 removed logs dir that showed up - root issue still unknown Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-735) DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs
[ https://issues.apache.org/jira/browse/NIFI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604312#comment-14604312 ] ASF subversion and git services commented on NIFI-735: -- Commit bd9782cb43ece682c853d9a75279ebe76f968044 in incubator-nifi's branch refs/heads/NIFI-735 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=bd9782c ] NIFI-735: DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs DocGenerator should on @OnUnscheduled and @OnStopped after its done generating the docs --- Key: NIFI-735 URL: https://issues.apache.org/jira/browse/NIFI-735 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Fix For: 0.2.0 Per [~mcgilman] +0 for triggering OnRemoved and OnShutdown after initialization and before being done with instance +0 for triggering OnRemoved and OnShutdown and not their deprecated counterparts Change code to call annotations *after* the documentation has been generated for that component. Also invoke both the new annotations and the deprecated annotations. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-680) Processor docs don't always need to mention Sensitive properties or EL
[
https://issues.apache.org/jira/browse/NIFI-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603856#comment-14603856
]
ASF subversion and git services commented on NIFI-680:
--
Commit 47847ab404d325663ed08b400da81337a79e298d in incubator-nifi's branch
refs/heads/develop from [~danbress]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=47847ab ]
NIFI-680 Processor docs don't always need to mention Sensitive properties or EL
Processor docs don't always need to mention Sensitive properties or EL
--
Key: NIFI-680
URL: https://issues.apache.org/jira/browse/NIFI-680
Project: Apache NiFi
Issue Type: Improvement
Components: Documentation Website
Affects Versions: 0.1.0
Reporter: Mike Drob
Assignee: Dan Bress
Priority: Minor
Fix For: 0.2.0
Attachments:
0001-NIFI-680-Processor-docs-don-t-always-need-to-mention.patch
If a processor doesn't have any properties that use the Apache NiFi EL or
have any sensitive properties, then there is no reason to mention them in the
preamble to the attribute table on the processor documentation. I'd like to
imagine that this can all be auto-detected.
For example, on
shttps://nifi.incubator.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html
the paragraph could be reduced to:
{quote}
In the list below, the names of required properties appear in bold. Any other
properties (not in bold) are considered optional. The table also indicates
any default values.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-704) StandardProcessorTestRunner should allow you to wait before calling OnUnScheduled methods
[ https://issues.apache.org/jira/browse/NIFI-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603857#comment-14603857 ] ASF subversion and git services commented on NIFI-704: -- Commit 6b4e90dd5dabff82b1aeae8d9c64cdd32112b33d in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=6b4e90d ] NIFI-704 StandardProcessorTestRunner should allow you to wait before calling OnUnScheduled methods StandardProcessorTestRunner should allow you to wait before calling OnUnScheduled methods - Key: NIFI-704 URL: https://issues.apache.org/jira/browse/NIFI-704 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-NIFI-704-StandardProcessorTestRunner-should-allow-yo.patch [StandardProcessorTestRunner does not wait|https://github.com/apache/incubator-nifi/blob/develop/nifi/nifi-mock/src/main/java/org/apache/nifi/util/StandardProcessorTestRunner.java#L208-L210] for the processor 'run' calls to finish before invoking the @OnUnscheduled methods. This may result in the Processor 'run' calls acting weird, because @OnUnscheduled has been called. Notice that [ExecutorService.shutdown()|http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ExecutorService.html#shutdown%28%29] says _This method does not wait for previously submitted tasks to complete execution. Use awaitTermination to do that._ I would suggest that the StandardProcessorTestRunner either always wait for the processor run calls to finish, or let you specify an amount of time to wait for them to finish. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-680) Processor docs don't always need to mention Sensitive properties or EL
[
https://issues.apache.org/jira/browse/NIFI-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603858#comment-14603858
]
ASF subversion and git services commented on NIFI-680:
--
Commit cc3be416b26c9733f84b2acff590389ed1dd1abc in incubator-nifi's branch
refs/heads/develop from [~danbress]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=cc3be41 ]
Merge branch 'develop' into NIFI-680
Conflicts:
nifi/nifi-mock/src/main/java/org/apache/nifi/util/StandardProcessorTestRunner.java
nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java
nifi/nifi-mock/src/test/java/org/apache/nifi/util/CurrentTestStandardProcessorTestRunner.java
Processor docs don't always need to mention Sensitive properties or EL
--
Key: NIFI-680
URL: https://issues.apache.org/jira/browse/NIFI-680
Project: Apache NiFi
Issue Type: Improvement
Components: Documentation Website
Affects Versions: 0.1.0
Reporter: Mike Drob
Assignee: Dan Bress
Priority: Minor
Fix For: 0.2.0
Attachments:
0001-NIFI-680-Processor-docs-don-t-always-need-to-mention.patch
If a processor doesn't have any properties that use the Apache NiFi EL or
have any sensitive properties, then there is no reason to mention them in the
preamble to the attribute table on the processor documentation. I'd like to
imagine that this can all be auto-detected.
For example, on
shttps://nifi.incubator.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html
the paragraph could be reduced to:
{quote}
In the list below, the names of required properties appear in bold. Any other
properties (not in bold) are considered optional. The table also indicates
any default values.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603811#comment-14603811 ] ASF subversion and git services commented on NIFI-632: -- Commit 40b55efbd7082935accb37c17bacbcb8d1f1cd38 in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=40b55ef ] Merge branch 'develop' into NIFI-632 Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603807#comment-14603807 ] ASF subversion and git services commented on NIFI-632: -- Commit e1a59c47b7373c1165cc10623e4a2c945e470a4b in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e1a59c4 ] NIFI-632 moving thread startup from constructor to initialize methods Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603808#comment-14603808 ] ASF subversion and git services commented on NIFI-632: -- Commit cad8aa11e1adb57052303912b9adc90aaeff708f in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=cad8aa1 ] NIFI-632 adding VolatileContentRepository and VolatileFlowFile repository to service definition file Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603810#comment-14603810 ] ASF subversion and git services commented on NIFI-632: -- Commit 28bfb70e46a3099139e810b5ee93d7335ddb880c in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=28bfb70 ] Merge branch 'develop' into NIFI-632 Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603809#comment-14603809 ] ASF subversion and git services commented on NIFI-632: -- Commit 46aa2685e3162ee6afbf68a0ac68d5206cb9c500 in incubator-nifi's branch refs/heads/develop from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=46aa268 ] Merge branch 'develop' into NIFI-632 Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-680) Processor docs don't always need to mention Sensitive properties or EL
[
https://issues.apache.org/jira/browse/NIFI-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603838#comment-14603838
]
ASF subversion and git services commented on NIFI-680:
--
Commit cc3be416b26c9733f84b2acff590389ed1dd1abc in incubator-nifi's branch
refs/heads/NIFI-680 from [~danbress]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=cc3be41 ]
Merge branch 'develop' into NIFI-680
Conflicts:
nifi/nifi-mock/src/main/java/org/apache/nifi/util/StandardProcessorTestRunner.java
nifi/nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java
nifi/nifi-mock/src/test/java/org/apache/nifi/util/CurrentTestStandardProcessorTestRunner.java
Processor docs don't always need to mention Sensitive properties or EL
--
Key: NIFI-680
URL: https://issues.apache.org/jira/browse/NIFI-680
Project: Apache NiFi
Issue Type: Improvement
Components: Documentation Website
Affects Versions: 0.1.0
Reporter: Mike Drob
Assignee: Dan Bress
Priority: Minor
Fix For: 0.2.0
Attachments:
0001-NIFI-680-Processor-docs-don-t-always-need-to-mention.patch
If a processor doesn't have any properties that use the Apache NiFi EL or
have any sensitive properties, then there is no reason to mention them in the
preamble to the attribute table on the processor documentation. I'd like to
imagine that this can all be auto-detected.
For example, on
shttps://nifi.incubator.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.HashContent/index.html
the paragraph could be reduced to:
{quote}
In the list below, the names of required properties appear in bold. Any other
properties (not in bold) are considered optional. The table also indicates
any default values.
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603837#comment-14603837 ] ASF subversion and git services commented on NIFI-632: -- Commit 40b55efbd7082935accb37c17bacbcb8d1f1cd38 in incubator-nifi's branch refs/heads/NIFI-680 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=40b55ef ] Merge branch 'develop' into NIFI-632 Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-683) When connecting to cluster, splash screen remains indefinitely if error sent back
[ https://issues.apache.org/jira/browse/NIFI-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603835#comment-14603835 ] ASF subversion and git services commented on NIFI-683: -- Commit 0df351dcb47432dd0cacf31a2ed5e5765aa96f03 in incubator-nifi's branch refs/heads/NIFI-680 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0df351d ] NIFI-683: - Fixing typo. When connecting to cluster, splash screen remains indefinitely if error sent back - Key: NIFI-683 URL: https://issues.apache.org/jira/browse/NIFI-683 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Mark Payne Assignee: Matt Gilman Fix For: 0.2.0 Attachments: 0001-NIFI-683.patch, 0002-NIFI-683.patch I created a cluster with the NCM running on my host and a single node running in a VM. In the VM, I configured the node to report its fully qualified hostname. The Host running the NCM, however, does not recognize the fully qualified hostname of the VM and gets a Socket Read timeout. This is returned to the UI as a 409: Conflict. The UI ignores this, leaving the splash screen. The UI should instead report back an error, as it does if there are no connected nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-728) Unit test failure on multi-core/fast system builds: nifi-distributed-cache-server
[ https://issues.apache.org/jira/browse/NIFI-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603836#comment-14603836 ] ASF subversion and git services commented on NIFI-728: -- Commit f58972e566448886cdf984e6c8a34c83674b0705 in incubator-nifi's branch refs/heads/NIFI-680 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=f58972e ] NIFI-728: Allow Mock Framework to use property descriptors from subclasses that are created for unit testing Unit test failure on multi-core/fast system builds: nifi-distributed-cache-server - Key: NIFI-728 URL: https://issues.apache.org/jira/browse/NIFI-728 Project: Apache NiFi Issue Type: Bug Reporter: Joseph Witt Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-728-Allow-Mock-Framework-to-use-property-descri.patch Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.16 sec FAILURE! - in org.apache.nifi.distributed.cache.server.TestServerAndClient testNonPersistentMapServerAndClient(org.apache.nifi.distributed.cache.server.TestServerAndClient) Time elapsed: 0.001 sec FAILURE! java.lang.AssertionError: Failed to enable Controller Service MapServer[id=server] due to java.net.BindException: Address already in use at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.StandardProcessorTestRunner.enableControllerService(StandardProcessorTestRunner.java:616) at org.apache.nifi.distributed.cache.server.TestServerAndClient.testNonPersistentMapServerAndClient(TestServerAndClient.java:322) Results : Failed tests: TestServerAndClient.testNonPersistentMapServerAndClient:322 Failed to enable Controller Service MapServer[id=server] due to java.net.BindException: Address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-721) Typos in ExtractText
[ https://issues.apache.org/jira/browse/NIFI-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603775#comment-14603775 ] ASF subversion and git services commented on NIFI-721: -- Commit 0c5b78f03f9fa2a91a52347114a073a8c6ee59e6 in incubator-nifi's branch refs/heads/NIFI-632 from [~aldrin] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0c5b78f ] NIFI-721: Correcting typos in capability description and dynamic property of ExtractText. Typos in ExtractText Key: NIFI-721 URL: https://issues.apache.org/jira/browse/NIFI-721 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.1.0 Reporter: Aldrin Piri Assignee: Aldrin Piri Priority: Trivial Fix For: 0.2.0 Attachments: 0001-NIFI-721-Correcting-typos-in-capability-description-.patch Capture is misspelled in the capability description and the dynamic property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-683) When connecting to cluster, splash screen remains indefinitely if error sent back
[ https://issues.apache.org/jira/browse/NIFI-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603776#comment-14603776 ] ASF subversion and git services commented on NIFI-683: -- Commit 0df351dcb47432dd0cacf31a2ed5e5765aa96f03 in incubator-nifi's branch refs/heads/NIFI-632 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0df351d ] NIFI-683: - Fixing typo. When connecting to cluster, splash screen remains indefinitely if error sent back - Key: NIFI-683 URL: https://issues.apache.org/jira/browse/NIFI-683 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Mark Payne Assignee: Matt Gilman Fix For: 0.2.0 Attachments: 0001-NIFI-683.patch, 0002-NIFI-683.patch I created a cluster with the NCM running on my host and a single node running in a VM. In the VM, I configured the node to report its fully qualified hostname. The Host running the NCM, however, does not recognize the fully qualified hostname of the VM and gets a Socket Read timeout. This is returned to the UI as a 409: Conflict. The UI ignores this, leaving the splash screen. The UI should instead report back an error, as it does if there are no connected nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-704) StandardProcessorTestRunner should allow you to wait before calling OnUnScheduled methods
[ https://issues.apache.org/jira/browse/NIFI-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603779#comment-14603779 ] ASF subversion and git services commented on NIFI-704: -- Commit 6b4e90dd5dabff82b1aeae8d9c64cdd32112b33d in incubator-nifi's branch refs/heads/NIFI-680 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=6b4e90d ] NIFI-704 StandardProcessorTestRunner should allow you to wait before calling OnUnScheduled methods StandardProcessorTestRunner should allow you to wait before calling OnUnScheduled methods - Key: NIFI-704 URL: https://issues.apache.org/jira/browse/NIFI-704 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Affects Versions: 0.1.0 Reporter: Dan Bress Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-NIFI-704-StandardProcessorTestRunner-should-allow-yo.patch [StandardProcessorTestRunner does not wait|https://github.com/apache/incubator-nifi/blob/develop/nifi/nifi-mock/src/main/java/org/apache/nifi/util/StandardProcessorTestRunner.java#L208-L210] for the processor 'run' calls to finish before invoking the @OnUnscheduled methods. This may result in the Processor 'run' calls acting weird, because @OnUnscheduled has been called. Notice that [ExecutorService.shutdown()|http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ExecutorService.html#shutdown%28%29] says _This method does not wait for previously submitted tasks to complete execution. Use awaitTermination to do that._ I would suggest that the StandardProcessorTestRunner either always wait for the processor run calls to finish, or let you specify an amount of time to wait for them to finish. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-728) Unit test failure on multi-core/fast system builds: nifi-distributed-cache-server
[ https://issues.apache.org/jira/browse/NIFI-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603777#comment-14603777 ] ASF subversion and git services commented on NIFI-728: -- Commit f58972e566448886cdf984e6c8a34c83674b0705 in incubator-nifi's branch refs/heads/NIFI-632 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=f58972e ] NIFI-728: Allow Mock Framework to use property descriptors from subclasses that are created for unit testing Unit test failure on multi-core/fast system builds: nifi-distributed-cache-server - Key: NIFI-728 URL: https://issues.apache.org/jira/browse/NIFI-728 Project: Apache NiFi Issue Type: Bug Reporter: Joseph Witt Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-728-Allow-Mock-Framework-to-use-property-descri.patch Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.16 sec FAILURE! - in org.apache.nifi.distributed.cache.server.TestServerAndClient testNonPersistentMapServerAndClient(org.apache.nifi.distributed.cache.server.TestServerAndClient) Time elapsed: 0.001 sec FAILURE! java.lang.AssertionError: Failed to enable Controller Service MapServer[id=server] due to java.net.BindException: Address already in use at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.StandardProcessorTestRunner.enableControllerService(StandardProcessorTestRunner.java:616) at org.apache.nifi.distributed.cache.server.TestServerAndClient.testNonPersistentMapServerAndClient(TestServerAndClient.java:322) Results : Failed tests: TestServerAndClient.testNonPersistentMapServerAndClient:322 Failed to enable Controller Service MapServer[id=server] due to java.net.BindException: Address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-632) Documentation Generation: Nar ClassLoader
[ https://issues.apache.org/jira/browse/NIFI-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603778#comment-14603778 ] ASF subversion and git services commented on NIFI-632: -- Commit 40b55efbd7082935accb37c17bacbcb8d1f1cd38 in incubator-nifi's branch refs/heads/NIFI-632 from [~danbress] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=40b55ef ] Merge branch 'develop' into NIFI-632 Documentation Generation: Nar ClassLoader - Key: NIFI-632 URL: https://issues.apache.org/jira/browse/NIFI-632 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 0.1.0 Reporter: Matt Gilman Assignee: Dan Bress Priority: Minor Fix For: 0.2.0 Attachments: 0001-Squashed-commit-of-the-following.patch When auto generating component documentation the NarThreadContextClassLoader needs to be set in case the component attempts to load anything off of its classpath. Without this, the documentation generation fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-728) Unit test failure on multi-core/fast system builds: nifi-distributed-cache-server
[ https://issues.apache.org/jira/browse/NIFI-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14601232#comment-14601232 ] ASF subversion and git services commented on NIFI-728: -- Commit f58972e566448886cdf984e6c8a34c83674b0705 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=f58972e ] NIFI-728: Allow Mock Framework to use property descriptors from subclasses that are created for unit testing Unit test failure on multi-core/fast system builds: nifi-distributed-cache-server - Key: NIFI-728 URL: https://issues.apache.org/jira/browse/NIFI-728 Project: Apache NiFi Issue Type: Bug Reporter: Joseph Witt Assignee: Mark Payne Fix For: 0.2.0 Attachments: 0001-NIFI-728-Allow-Mock-Framework-to-use-property-descri.patch Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 4.16 sec FAILURE! - in org.apache.nifi.distributed.cache.server.TestServerAndClient testNonPersistentMapServerAndClient(org.apache.nifi.distributed.cache.server.TestServerAndClient) Time elapsed: 0.001 sec FAILURE! java.lang.AssertionError: Failed to enable Controller Service MapServer[id=server] due to java.net.BindException: Address already in use at org.junit.Assert.fail(Assert.java:88) at org.apache.nifi.util.StandardProcessorTestRunner.enableControllerService(StandardProcessorTestRunner.java:616) at org.apache.nifi.distributed.cache.server.TestServerAndClient.testNonPersistentMapServerAndClient(TestServerAndClient.java:322) Results : Failed tests: TestServerAndClient.testNonPersistentMapServerAndClient:322 Failed to enable Controller Service MapServer[id=server] due to java.net.BindException: Address already in use -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-724) Controller Services and Reporting Tasks should be able to emit bulletins
[ https://issues.apache.org/jira/browse/NIFI-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14601311#comment-14601311 ] ASF subversion and git services commented on NIFI-724: -- Commit 0a7ab1a06dd8b7164413bdcd0a85a4c457d3da71 in incubator-nifi's branch refs/heads/NIFI-724 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0a7ab1a ] NIFI-724: merged changes Controller Services and Reporting Tasks should be able to emit bulletins Key: NIFI-724 URL: https://issues.apache.org/jira/browse/NIFI-724 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-724) Controller Services and Reporting Tasks should be able to emit bulletins
[ https://issues.apache.org/jira/browse/NIFI-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14601310#comment-14601310 ] ASF subversion and git services commented on NIFI-724: -- Commit e240e07aaebea1fd66b22fce8aec3f0005fd3f60 in incubator-nifi's branch refs/heads/NIFI-724 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e240e07 ] NIFI-724: Enable bulletins for reporting tasks and controller services Controller Services and Reporting Tasks should be able to emit bulletins Key: NIFI-724 URL: https://issues.apache.org/jira/browse/NIFI-724 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-694) If Enabling Controller Service fails, no indication is provided to user
[ https://issues.apache.org/jira/browse/NIFI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14601697#comment-14601697 ] ASF subversion and git services commented on NIFI-694: -- Commit 7a28903402192819accaded9a90adfdfad852776 in incubator-nifi's branch refs/heads/NIFI-724 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=7a28903 ] NIFI-694: - Showing bulletins for services and referencing components when enabling and disabling. If Enabling Controller Service fails, no indication is provided to user --- Key: NIFI-694 URL: https://issues.apache.org/jira/browse/NIFI-694 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Mark Payne Fix For: 0.2.0 To replicate the issue: 1. Add a DBCPService controller service. 2. Configure service. For the Driver Url use file://tmp/non-existent-file or use an invalid Driver Class Name. 3. Click Apply. 4. Click Enable. The UI will show the spinner indefinitely, as the service will keep failing to enable because it throws Exceptions from its @OnEnabled method. The UI should provide some sort of indication that this is occurring. Otherwise, it appears to the user that the system is non-responsive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-683) When connecting to cluster, splash screen remains indefinitely if error sent back
[ https://issues.apache.org/jira/browse/NIFI-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599385#comment-14599385 ] ASF subversion and git services commented on NIFI-683: -- Commit 3a05a7da721d70767ab3ad9a6827a10e2d318725 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=3a05a7d ] NIFI-683: - Add explicit handling of errors that occur during the initial page loading. When connecting to cluster, splash screen remains indefinitely if error sent back - Key: NIFI-683 URL: https://issues.apache.org/jira/browse/NIFI-683 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Mark Payne Assignee: Matt Gilman Fix For: 0.2.0 Attachments: 0001-NIFI-683.patch, 0002-NIFI-683.patch I created a cluster with the NCM running on my host and a single node running in a VM. In the VM, I configured the node to report its fully qualified hostname. The Host running the NCM, however, does not recognize the fully qualified hostname of the VM and gets a Socket Read timeout. This is returned to the UI as a 409: Conflict. The UI ignores this, leaving the splash screen. The UI should instead report back an error, as it does if there are no connected nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-683) When connecting to cluster, splash screen remains indefinitely if error sent back
[ https://issues.apache.org/jira/browse/NIFI-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599386#comment-14599386 ] ASF subversion and git services commented on NIFI-683: -- Commit 0df351dcb47432dd0cacf31a2ed5e5765aa96f03 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0df351d ] NIFI-683: - Fixing typo. When connecting to cluster, splash screen remains indefinitely if error sent back - Key: NIFI-683 URL: https://issues.apache.org/jira/browse/NIFI-683 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Mark Payne Assignee: Matt Gilman Fix For: 0.2.0 Attachments: 0001-NIFI-683.patch, 0002-NIFI-683.patch I created a cluster with the NCM running on my host and a single node running in a VM. In the VM, I configured the node to report its fully qualified hostname. The Host running the NCM, however, does not recognize the fully qualified hostname of the VM and gets a Socket Read timeout. This is returned to the UI as a 409: Conflict. The UI ignores this, leaving the splash screen. The UI should instead report back an error, as it does if there are no connected nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-724) Controller Services and Reporting Tasks should be able to emit bulletins
[ https://issues.apache.org/jira/browse/NIFI-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14599844#comment-14599844 ] ASF subversion and git services commented on NIFI-724: -- Commit f1adb8bf034a8407dfdd655e441c74c10a61b18f in incubator-nifi's branch refs/heads/NIFI-724 from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=f1adb8b ] NIFI-724: Enable bulletins for reporting tasks and controller services Controller Services and Reporting Tasks should be able to emit bulletins Key: NIFI-724 URL: https://issues.apache.org/jira/browse/NIFI-724 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Fix For: 0.2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-718) nifi.sh install does not properly install nifi as a linux service
[ https://issues.apache.org/jira/browse/NIFI-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14597771#comment-14597771 ] ASF subversion and git services commented on NIFI-718: -- Commit 1faca8c93ea617a80bbeaa7ebd318b477f4ebd07 in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=1faca8c ] NIFI-718: Add links to /etc/rc2.d when installing nifi as a linux service nifi.sh install does not properly install nifi as a linux service - Key: NIFI-718 URL: https://issues.apache.org/jira/browse/NIFI-718 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Priority: Critical Fix For: 0.2.0 Attachments: 0001-NIFI-718-Add-links-to-etc-rc2.d-when-installing-nifi.patch After running bin/nifi.sh install, users can now start and stop nfii as a service by using service nifi start and service nifi stop. However, the service is not recognized by systemctl or chkconfig, and the service does not start automatically on system reboot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-718) nifi.sh install does not properly install nifi as a linux service
[ https://issues.apache.org/jira/browse/NIFI-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14597772#comment-14597772 ] ASF subversion and git services commented on NIFI-718: -- Commit 169256015bdef5d2bae6d4676ef776b06cdb42cd in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=1692560 ] Merge branch 'NIFI-718' into develop nifi.sh install does not properly install nifi as a linux service - Key: NIFI-718 URL: https://issues.apache.org/jira/browse/NIFI-718 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Mark Payne Assignee: Mark Payne Priority: Critical Fix For: 0.2.0 Attachments: 0001-NIFI-718-Add-links-to-etc-rc2.d-when-installing-nifi.patch After running bin/nifi.sh install, users can now start and stop nfii as a service by using service nifi start and service nifi stop. However, the service is not recognized by systemctl or chkconfig, and the service does not start automatically on system reboot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-378) MergeContent in Defragment mode will merge fragments without checking index
[ https://issues.apache.org/jira/browse/NIFI-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14597802#comment-14597802 ] ASF subversion and git services commented on NIFI-378: -- Commit e767f5ce02c36f41874d4f97abdb50c643662deb in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=e767f5c ] Merge branch 'NIFI-378' into develop MergeContent in Defragment mode will merge fragments without checking index --- Key: NIFI-378 URL: https://issues.apache.org/jira/browse/NIFI-378 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 0.0.1 Reporter: Michael Moser Assignee: Mark Payne Priority: Minor Fix For: 0.2.0 Attachments: 0001-NIFI-378-updated-documentation-to-explain-contract-o.patch When in Defragment mode, the MergeContent processor looks for fragment.identifier and fragment.count attributes in order to place FlowFiles in the correct bin. The fragment.index attribute is ignored. If you happen to have many FlowFile in the queue to MergeContent, and they all have fragment.identifier=foo and fragment.count=2, then it will merge two FlowFiles that have fragment.index=1 or it will merge two FlowFiles that have fragment.index=2. Granted this may seem odd. The use case is to give the MergeContent processor two input queues. We configure one queue to contain files with fragment.index=1 and the other queue to contain files with fragment.index=2. We want one file from each queue to be merged. Instead it will merge two files from the same queue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
