[jira] [Commented] (NIFI-1170) TailFile "File to Tail" property should support Wildcards
[
https://issues.apache.org/jira/browse/NIFI-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472948#comment-15472948
]
ASF GitHub Bot commented on NIFI-1170:
--
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/980
@trixpan I modified the documentation as you suggest even though I do have
use cases where the appended file is static and rolling files contain the date.
I think you can give it a try... it may need a bit a polishing but it should
work. I tried to stay as close as possible to the original implementation, let
me know how it behaves when dealing with huge files :)
> TailFile "File to Tail" property should support Wildcards
> -
>
> Key: NIFI-1170
> URL: https://issues.apache.org/jira/browse/NIFI-1170
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 0.4.0
>Reporter: Andre
>
> Because of challenges around log rotation of high volume syslog and app
> producers, it is customary to logging platform developers to promote file
> variables based file names such as DynaFiles (rsyslog), Macros(syslog-ng)as
> alternatives to getting SIGHUPs being sent to the syslog daemon upon every
> file rotation.
> (To certain extent, used even NiFi's has similar patterns, like for example,
> when one uses Expression Language to set PutHDFS destination file).
> The current TailFile strategy suggests rotation patterns like:
> {code}
> log_folder/app.log
> log_folder/app.log.1
> log_folder/app.log.2
> log_folder/app.log.3
> {code}
> It is possible to fool the system to accept wildcards by simply using a
> strategy like:
> {code}
> log_folder/test1
> log_folder/server1
> log_folder/server2
> log_folder/server3
> {code}
> And configure *Rolling Filename Pattern* to * but it feels like a hack,
> rather than catering for an ever increasingly prevalent use case
> (DynaFile/macros/etc).
> It would be great if instead, TailFile had the ability to use wildcards on
> File to Tail property
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #980: NIFI-1170 - Improved TailFile processor to support multiple...
Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/980 @trixpan I modified the documentation as you suggest even though I do have use cases where the appended file is static and rolling files contain the date. I think you can give it a try... it may need a bit a polishing but it should work. I tried to stay as close as possible to the original implementation, let me know how it behaves when dealing with huge files :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2718) HTTP Site-to-Site doesn't report port auth failure well, compared to RAW
[ https://issues.apache.org/jira/browse/NIFI-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura updated NIFI-2718: Status: Patch Available (was: Open) > HTTP Site-to-Site doesn't report port auth failure well, compared to RAW > > > Key: NIFI-2718 > URL: https://issues.apache.org/jira/browse/NIFI-2718 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Koji Kawamura > > If 'send data via site-to-site' policy is removed for a client after the > client has already connected to that port, the client won't be able to > send/receive more data from the remote NiFi. > This is true for both RAW and HTTP transfer protocol, however the way that > error is reported on NiFi UI is different. HTTP Site-to-Site doesn't report > port auth failure well, compared to RAW. > Detail is reported here: > https://github.com/apache/nifi/pull/971#issuecomment-243823632 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2718) HTTP Site-to-Site doesn't report port auth failure well, compared to RAW
[ https://issues.apache.org/jira/browse/NIFI-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472921#comment-15472921 ] ASF GitHub Bot commented on NIFI-2718: -- GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi/pull/996 NIFI-2718: Show HTTP S2S Auth error on bulletin This commit fixes following two issues, that happens when a Root Group Port policy for S2S data transfer is removed at a remote NiFi, after a client NiFi has connected to that port: 1. At client side, Remote Process Group should show that authorization is failing on its bulletin, but the Exception is caught and ignored. Nothing is shown on the UI with HTTP transport protocol. RAW S2S shows error on RPG bulletin. This commit fixes HTTP S2S to behave the same.  2. At server side, corresponding input-port or output-port should show that it is accessed by an unauthorized client on its bulletin, but it's not shown with HTTP transport protocol. RAW S2S shows warning messages for this. This commit fixes HTTP S2S to behave the same.  In order to fix the 2nd issue above, request authorization at DataTransferResource is changed from using DataTransferAuthorizable directly, to call RootGroupPort.checkUserAuthorization(). Because the blettin is tied to the Port instance and it's difficult to produce blettin message from DataTransferResource. Since RootGroupPort.checkUserAuthorization uses DataTransferAuthorizable inside, the check logic stays the same as before. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijokarumawak/nifi nifi-2718 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/996.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #996 commit 8c9261f2cb5a8064f9e53049bac0f3830d357b80 Author: Koji Kawamura Date: 2016-09-08T05:37:30Z NIFI-2718: Show HTTP S2S Auth error on bulletin This commit fixes following two issues, that happens when a Root Group Port policy for S2S data transfer is removed at a remote NiFi, after a client NiFi has connected to that port: 1. At client side, Remote Process Group should show that authorization is failing on its bulletin, but the Exception is caught and ignored. Nothing is shown on the UI with HTTP transport protocol. RAW S2S shows error on RPG bulletin. This commit fixes HTTP S2S to behave the same. 2. At server side, corresponding input-port or output-port should show that it is accessed by an unauthorized client on its bulletin, but it's not shown with HTTP transport protocol. RAW S2S shows warning messages for this. This commit fixes HTTP S2S to behave the same. In order to fix the 2nd issue above, request authorization at DataTransferResource is changed from using DataTransferAuthorizable directly, to call RootGroupPort.checkUserAuthorization(). Because the blettin is tied to the Port instance and it's difficult to produce blettin message from this resource. Since RootGroupPort.checkUserAuthorization uses DataTransferAuthorizable inside, the check logic stays the same as before. > HTTP Site-to-Site doesn't report port auth failure well, compared to RAW > > > Key: NIFI-2718 > URL: https://issues.apache.org/jira/browse/NIFI-2718 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Koji Kawamura > > If 'send data via site-to-site' policy is removed for a client after the > client has already connected to that port, the client won't be able to > send/receive more data from the remote NiFi. > This is true for both RAW and HTTP transfer protocol, however the way that > error is reported on NiFi UI is different. HTTP Site-to-Site doesn't report > port auth failure well, compared to RAW. > Detail is reported here: > https://github.com/apache/nifi/pull/971#issuecomment-243823632 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #996: NIFI-2718: Show HTTP S2S Auth error on bulletin
GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi/pull/996 NIFI-2718: Show HTTP S2S Auth error on bulletin This commit fixes following two issues, that happens when a Root Group Port policy for S2S data transfer is removed at a remote NiFi, after a client NiFi has connected to that port: 1. At client side, Remote Process Group should show that authorization is failing on its bulletin, but the Exception is caught and ignored. Nothing is shown on the UI with HTTP transport protocol. RAW S2S shows error on RPG bulletin. This commit fixes HTTP S2S to behave the same.  2. At server side, corresponding input-port or output-port should show that it is accessed by an unauthorized client on its bulletin, but it's not shown with HTTP transport protocol. RAW S2S shows warning messages for this. This commit fixes HTTP S2S to behave the same.  In order to fix the 2nd issue above, request authorization at DataTransferResource is changed from using DataTransferAuthorizable directly, to call RootGroupPort.checkUserAuthorization(). Because the blettin is tied to the Port instance and it's difficult to produce blettin message from DataTransferResource. Since RootGroupPort.checkUserAuthorization uses DataTransferAuthorizable inside, the check logic stays the same as before. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijokarumawak/nifi nifi-2718 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/996.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #996 commit 8c9261f2cb5a8064f9e53049bac0f3830d357b80 Author: Koji Kawamura Date: 2016-09-08T05:37:30Z NIFI-2718: Show HTTP S2S Auth error on bulletin This commit fixes following two issues, that happens when a Root Group Port policy for S2S data transfer is removed at a remote NiFi, after a client NiFi has connected to that port: 1. At client side, Remote Process Group should show that authorization is failing on its bulletin, but the Exception is caught and ignored. Nothing is shown on the UI with HTTP transport protocol. RAW S2S shows error on RPG bulletin. This commit fixes HTTP S2S to behave the same. 2. At server side, corresponding input-port or output-port should show that it is accessed by an unauthorized client on its bulletin, but it's not shown with HTTP transport protocol. RAW S2S shows warning messages for this. This commit fixes HTTP S2S to behave the same. In order to fix the 2nd issue above, request authorization at DataTransferResource is changed from using DataTransferAuthorizable directly, to call RootGroupPort.checkUserAuthorization(). Because the blettin is tied to the Port instance and it's difficult to produce blettin message from this resource. Since RootGroupPort.checkUserAuthorization uses DataTransferAuthorizable inside, the check logic stays the same as before. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2747) Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH)
[ https://issues.apache.org/jira/browse/NIFI-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre updated NIFI-2747: Description: It would be great if we had a processor to support fuzzy hashing algorithms such as SpamSum/SSDeep was: It would be great if HashContent could support fuzzy hashing algorithms such as SpamSum/SSDeep > Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH) > - > > Key: NIFI-2747 > URL: https://issues.apache.org/jira/browse/NIFI-2747 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Andre > > It would be great if we had a processor to support fuzzy hashing algorithms > such as SpamSum/SSDeep -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2747) Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH)
[ https://issues.apache.org/jira/browse/NIFI-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre updated NIFI-2747: Summary: Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH) (was: HashContent should support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH)) > Add Processor support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH) > - > > Key: NIFI-2747 > URL: https://issues.apache.org/jira/browse/NIFI-2747 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Andre > > It would be great if HashContent could support fuzzy hashing algorithms such > as SpamSum/SSDeep -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2747) HashContent should support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH)
[ https://issues.apache.org/jira/browse/NIFI-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andre updated NIFI-2747: Summary: HashContent should support SSDeep (SpamSum) hashes (and possibly others e.g. TLSH) (was: HashContent should support SSDeep (SpamSum) hashes) > HashContent should support SSDeep (SpamSum) hashes (and possibly others e.g. > TLSH) > -- > > Key: NIFI-2747 > URL: https://issues.apache.org/jira/browse/NIFI-2747 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Andre > > It would be great if HashContent could support fuzzy hashing algorithms such > as SpamSum/SSDeep -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2747) HashContent should support SSDeep (SpamSum) hashes
[ https://issues.apache.org/jira/browse/NIFI-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472563#comment-15472563 ] Andre commented on NIFI-2747: - compatible library (MIT license) https://github.com/tdebatty/java-spamsum > HashContent should support SSDeep (SpamSum) hashes > -- > > Key: NIFI-2747 > URL: https://issues.apache.org/jira/browse/NIFI-2747 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Andre > > It would be great if HashContent could support fuzzy hashing algorithms such > as SpamSum/SSDeep -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2747) HashContent should support SSDeep (SpamSum) hashes
Andre created NIFI-2747: --- Summary: HashContent should support SSDeep (SpamSum) hashes Key: NIFI-2747 URL: https://issues.apache.org/jira/browse/NIFI-2747 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.0.0 Reporter: Andre It would be great if HashContent could support fuzzy hashing algorithms such as SpamSum/SSDeep -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2440) Add last modified time & timestamp attributes to flow files generated by ListSFTP processor
[ https://issues.apache.org/jira/browse/NIFI-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472457#comment-15472457 ] ASF GitHub Bot commented on NIFI-2440: -- Github user jskora commented on the issue: https://github.com/apache/nifi/pull/913 @joewitt Thanks, from what I can tell looking at JDK source the format spec drives the output more than the Locale, so I agree that the comments should cover it. @kirkalicious can you add the date format to the WritesAttribute description in ListSFTP like it is in [ListFile](https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListFile.java#L95)? I will commit it once you are done. Thanks! > Add last modified time & timestamp attributes to flow files generated by > ListSFTP processor > --- > > Key: NIFI-2440 > URL: https://issues.apache.org/jira/browse/NIFI-2440 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Kirk Tarou >Assignee: Joe Skora >Priority: Trivial > Original Estimate: 1h > Remaining Estimate: 1h > > The timestamp & last modified time attributes are not exposed in ListSFTP so > there's no way to preserve the timestamp of the remotely collected files when > writing them out to a file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #913: NIFI-2440 - Add 'file.lastModifiedTime' attribute to ListSF...
Github user jskora commented on the issue: https://github.com/apache/nifi/pull/913 @joewitt Thanks, from what I can tell looking at JDK source the format spec drives the output more than the Locale, so I agree that the comments should cover it. @kirkalicious can you add the date format to the WritesAttribute description in ListSFTP like it is in [ListFile](https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListFile.java#L95)? I will commit it once you are done. Thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #995: NIFI-1966: Resolved issue where two flows that are b...
GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/995 NIFI-1966: Resolved issue where two flows that are both empty but have different fingerprints (due to root group id being different) causes vote election to fail First Commit is a unit test that replicates the issue. This will fail without the second commit being applied. After applying the second commit, the tests should all pass. You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-1966-Part2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/995.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #995 commit dd2b47edff1a2c47afcc85d54a1024e5814e63a0 Author: Mark Payne Date: 2016-09-08T01:07:01Z NIFI-1966: Recreated issue that is outlined in JIRA (the reason for re-opening the ticket) that results in 'java.util.NoSuchElementException: No value present' in unit test commit 9db7d47826a76f1a5ad0acd9c1c476c0892fbd4c Author: Mark Payne Date: 2016-09-08T01:15:41Z NIFI-1966: Resolved issue where two flows that are both empty but have different fingerprints (due to root group id being different) causes vote election to fail --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-1966) Address Issue of Nodes Disagreeing About Flow Contents on Startup
[ https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472360#comment-15472360 ] ASF GitHub Bot commented on NIFI-1966: -- GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/995 NIFI-1966: Resolved issue where two flows that are both empty but have different fingerprints (due to root group id being different) causes vote election to fail First Commit is a unit test that replicates the issue. This will fail without the second commit being applied. After applying the second commit, the tests should all pass. You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-1966-Part2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/995.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #995 commit dd2b47edff1a2c47afcc85d54a1024e5814e63a0 Author: Mark Payne Date: 2016-09-08T01:07:01Z NIFI-1966: Recreated issue that is outlined in JIRA (the reason for re-opening the ticket) that results in 'java.util.NoSuchElementException: No value present' in unit test commit 9db7d47826a76f1a5ad0acd9c1c476c0892fbd4c Author: Mark Payne Date: 2016-09-08T01:15:41Z NIFI-1966: Resolved issue where two flows that are both empty but have different fingerprints (due to root group id being different) causes vote election to fail > Address Issue of Nodes Disagreeing About Flow Contents on Startup > - > > Key: NIFI-1966 > URL: https://issues.apache.org/jira/browse/NIFI-1966 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne >Priority: Blocker > Labels: migration > Fix For: 1.1.0 > > > During startup a coordinator is selected at random to act as the manager of > data flow and distributing it to other nodes. This works fine unless that > selected coordinator happens to have a uninheritable data flow. When this > occurs, the other nodes either are > - Able to connect to Coordinator and then unable to join due to an > uninheritable flow exception due to being presented with a bad data flow. In > this case, the node shut down. > - Unable to connect to the Coordinator due to lack of quorem and never > present with the bad data flow. In this case, the node ran its local flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1966) Address Issue of Nodes Disagreeing About Flow Contents on Startup
[ https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472335#comment-15472335 ] Mark Payne commented on NIFI-1966: -- Re-opening the ticket, as I have come across an issue. If all nodes in the cluster have an empty flow, but the flow is different between two of the nodes, we end up with the following warning in the logs: 2016-09-07 21:23:47,649 WARN [Process Cluster Protocol Request-9] org.apache.nifi.io.socket.SocketListener Dispatching socket request encountered exception due to: java.util.NoSuchElementException: No value present java.util.NoSuchElementException: No value present at java.util.Optional.get(Optional.java:135) ~[na:1.8.0_101] at org.apache.nifi.cluster.coordination.flow.PopularVoteFlowElection.performElection(PopularVoteFlowElection.java:166) ~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556] at org.apache.nifi.cluster.coordination.flow.PopularVoteFlowElection.isElectionComplete(PopularVoteFlowElection.java:87) ~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556] at org.apache.nifi.cluster.coordination.flow.PopularVoteFlowElection.castVote(PopularVoteFlowElection.java:118) ~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556] at org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.handleConnectionRequest(NodeClusterCoordinator.java:860) ~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556] at org.apache.nifi.cluster.coordination.node.NodeClusterCoordinator.handle(NodeClusterCoordinator.java:740) ~[nifi-framework-cluster-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556] at org.apache.nifi.cluster.protocol.impl.SocketProtocolListener.dispatchRequest(SocketProtocolListener.java:167) ~[nifi-framework-cluster-protocol-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556] at org.apache.nifi.io.socket.SocketListener$2$1.run(SocketListener.java:136) ~[nifi-socket-utils-1.0.0.2.0.0.0-556.jar:1.0.0.2.0.0.0-556] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_101] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_101] at java.lang.Thread.run(Thread.java:745) [na:1.8.0_101] > Address Issue of Nodes Disagreeing About Flow Contents on Startup > - > > Key: NIFI-1966 > URL: https://issues.apache.org/jira/browse/NIFI-1966 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne >Priority: Blocker > Labels: migration > Fix For: 1.1.0 > > > During startup a coordinator is selected at random to act as the manager of > data flow and distributing it to other nodes. This works fine unless that > selected coordinator happens to have a uninheritable data flow. When this > occurs, the other nodes either are > - Able to connect to Coordinator and then unable to join due to an > uninheritable flow exception due to being presented with a bad data flow. In > this case, the node shut down. > - Unable to connect to the Coordinator due to lack of quorem and never > present with the bad data flow. In this case, the node ran its local flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (NIFI-1966) Address Issue of Nodes Disagreeing About Flow Contents on Startup
[ https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reopened NIFI-1966: -- > Address Issue of Nodes Disagreeing About Flow Contents on Startup > - > > Key: NIFI-1966 > URL: https://issues.apache.org/jira/browse/NIFI-1966 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne >Priority: Blocker > Labels: migration > Fix For: 1.1.0 > > > During startup a coordinator is selected at random to act as the manager of > data flow and distributing it to other nodes. This works fine unless that > selected coordinator happens to have a uninheritable data flow. When this > occurs, the other nodes either are > - Able to connect to Coordinator and then unable to join due to an > uninheritable flow exception due to being presented with a bad data flow. In > this case, the node shut down. > - Unable to connect to the Coordinator due to lack of quorem and never > present with the bad data flow. In this case, the node ran its local flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1170) TailFile "File to Tail" property should support Wildcards
[
https://issues.apache.org/jira/browse/NIFI-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15472143#comment-15472143
]
ASF GitHub Bot commented on NIFI-1170:
--
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/980
Let me know when this is ready to test and I will give it a go
> TailFile "File to Tail" property should support Wildcards
> -
>
> Key: NIFI-1170
> URL: https://issues.apache.org/jira/browse/NIFI-1170
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 0.4.0
>Reporter: Andre
>
> Because of challenges around log rotation of high volume syslog and app
> producers, it is customary to logging platform developers to promote file
> variables based file names such as DynaFiles (rsyslog), Macros(syslog-ng)as
> alternatives to getting SIGHUPs being sent to the syslog daemon upon every
> file rotation.
> (To certain extent, used even NiFi's has similar patterns, like for example,
> when one uses Expression Language to set PutHDFS destination file).
> The current TailFile strategy suggests rotation patterns like:
> {code}
> log_folder/app.log
> log_folder/app.log.1
> log_folder/app.log.2
> log_folder/app.log.3
> {code}
> It is possible to fool the system to accept wildcards by simply using a
> strategy like:
> {code}
> log_folder/test1
> log_folder/server1
> log_folder/server2
> log_folder/server3
> {code}
> And configure *Rolling Filename Pattern* to * but it feels like a hack,
> rather than catering for an ever increasingly prevalent use case
> (DynaFile/macros/etc).
> It would be great if instead, TailFile had the ability to use wildcards on
> File to Tail property
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #980: NIFI-1170 - Improved TailFile processor to support multiple...
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/980 Let me know when this is ready to test and I will give it a go --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2629) Hide add property "+" in Processors, Controller Services and Reporting Tasks that don't allow dynamic properties
[ https://issues.apache.org/jira/browse/NIFI-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471997#comment-15471997 ] Joseph Witt commented on NIFI-2629: --- that seems to me like a totally fair compromise here [~tarouki]. I'm a +1 to that idea! > Hide add property "+" in Processors, Controller Services and Reporting Tasks > that don't allow dynamic properties > > > Key: NIFI-2629 > URL: https://issues.apache.org/jira/browse/NIFI-2629 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Core UI >Affects Versions: 0.7.0 >Reporter: Kirk Tarou >Priority: Minor > Attachments: Screen Shot 2016-09-07 at 3.20.04 PM.png, Screen Shot > 2016-09-07 at 3.20.20 PM.png > > > A few Processors, Controller Services and Reporting Tasks expect or allow > extra properties to be added on the 'Properties' tab in the Detail view. The > rest will show a "not a supported property" error. > To avoid confusion, the new property "+" icon should be hidden if dynamic > properties are not allowed. > The existence of a "DynamicProperty" annotation could be used as an indicator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2629) Hide add property "+" in Processors, Controller Services and Reporting Tasks that don't allow dynamic properties
[ https://issues.apache.org/jira/browse/NIFI-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Tarou updated NIFI-2629: - Attachment: Screen Shot 2016-09-07 at 3.20.20 PM.png Screen Shot 2016-09-07 at 3.20.04 PM.png I've created a branch locally that changes the icon color (but retains functionality) if it doesn't have the DynamicAttribute annotation Supports Dynamic Properties: On Thu, Sep 1, 2016 at 1:57 PM, ASF GitHub Bot (JIRA) -- -Kirk > Hide add property "+" in Processors, Controller Services and Reporting Tasks > that don't allow dynamic properties > > > Key: NIFI-2629 > URL: https://issues.apache.org/jira/browse/NIFI-2629 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Core UI >Affects Versions: 0.7.0 >Reporter: Kirk Tarou >Priority: Minor > Attachments: Screen Shot 2016-09-07 at 3.20.04 PM.png, Screen Shot > 2016-09-07 at 3.20.20 PM.png > > > A few Processors, Controller Services and Reporting Tasks expect or allow > extra properties to be added on the 'Properties' tab in the Detail view. The > rest will show a "not a supported property" error. > To avoid confusion, the new property "+" icon should be hidden if dynamic > properties are not allowed. > The existence of a "DynamicProperty" annotation could be used as an indicator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi-minifi pull request #32: MINIFI-104 - Making connection ids filesystem ...
GitHub user brosander opened a pull request: https://github.com/apache/nifi-minifi/pull/32 MINIFI-104 - Making connection ids filesystem friendly, unique You can merge this pull request into a Git repository by running: $ git pull https://github.com/brosander/nifi-minifi MINIFI-104 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi/pull/32.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #32 commit 1143b336df143c28051c558e68f20dd50d824d00 Author: Bryan Rosander Date: 2016-09-07T21:36:32Z MINIFI-104 - Making connection ids filesystem friendly, unique --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2695) Access Denied messages should include more information
[ https://issues.apache.org/jira/browse/NIFI-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-2695: -- Description: Access Denied errors should provide more information than just the statement that access has been denied. At a minimum, the component types (controller service, processor, process group, etc) and IDs for which access was denied should be provided in the message. For example, if the user is attempting to create a template that includes a child process group that has a controller service for which the user does not have read access, the request to create the template will be denied, and the user will be informed that it was denied. While this is correct, the user (and perhaps the admin) does not have a clear indication of which component involved in the request caused the request to be denied. If the component types and IDs (ie "Process Group 123456789") are shown in the error message (and logs), the user (and admin) have direct information to use to solve any policy changes that might need to be made to allow the user's request to complete successfully. was: Access Denied errors should provide more information than just the statement that access has been denied. At a minimum, the component types and IDs for which access was denied should be provided in the message. For example, if the user is attempting to create a template that includes a child process group that has a controller service for which the user does not have read access, the request to create the template will be denied, and the user will be informed that it was denied. While this is correct, the user (and perhaps the admin) does not have a clear indication of which component involved in the request caused the request to be denied. If the component types and IDs are shown in the error message (and logs), the user (and admin) have direct information to use to solve any policy changes that might need to be made to allow the user's request to complete successfully. > Access Denied messages should include more information > -- > > Key: NIFI-2695 > URL: https://issues.apache.org/jira/browse/NIFI-2695 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Core UI >Reporter: Jeff Storck >Priority: Minor > Fix For: 1.1.0 > > > Access Denied errors should provide more information than just the statement > that access has been denied. At a minimum, the component types (controller > service, processor, process group, etc) and IDs for which access was denied > should be provided in the message. > For example, if the user is attempting to create a template that includes a > child process group that has a controller service for which the user does not > have read access, the request to create the template will be denied, and the > user will be informed that it was denied. While this is correct, the user > (and perhaps the admin) does not have a clear indication of which component > involved in the request caused the request to be denied. > If the component types and IDs (ie "Process Group 123456789") are shown in > the error message (and logs), the user (and admin) have direct information to > use to solve any policy changes that might need to be made to allow the > user's request to complete successfully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated NIFI-2745: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471574#comment-15471574 ] ASF subversion and git services commented on NIFI-2745: --- Commit d36b76cc600b76748ffba9b94d6b702af552756f in nifi's branch refs/heads/master from [~ozhurakousky] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d36b76c ] NIFI-2745 added _source destination name_ attribute to ConsumeJMS This closes #992 > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471575#comment-15471575 ] ASF GitHub Bot commented on NIFI-2745: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/992 > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #992: NIFI-2745 added _source destination name_ attribute ...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/992 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471413#comment-15471413 ] ASF GitHub Bot commented on NIFI-2745: -- Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/992 Looks good. Was initially thrown off a bit by the instance variable but does appear consistent with current model so my concern is more stylistic than functional. +1 > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #992: NIFI-2745 added _source destination name_ attribute to Cons...
Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/992 Looks good. Was initially thrown off a bit by the instance variable but does appear consistent with current model so my concern is more stylistic than functional. +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2746) Error when accessing User page
[ https://issues.apache.org/jira/browse/NIFI-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2746: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Error when accessing User page > -- > > Key: NIFI-2746 > URL: https://issues.apache.org/jira/browse/NIFI-2746 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.1.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.1.0 > > > When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an > error, and the logs show a Null Pointer: > 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > java.lang.NullPointerException: null > at > org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) > ~[classes/:na] > at > org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) > ~[classes/:na] > at > org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) > ~[classes/:na] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_91] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_91] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > [jersey-servlet-1.19.jar:1.19] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [javax.servlet-api-3.1.0.jar:3.1.0] > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) > [jetty-servlets-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.apache.nifi.web.filter.RequestLogger.doFilter(RequestLogger.java:66) > [classes/:na] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.jav
[jira] [Commented] (NIFI-2746) Error when accessing User page
[ https://issues.apache.org/jira/browse/NIFI-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471388#comment-15471388 ] ASF GitHub Bot commented on NIFI-2746: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/993 > Error when accessing User page > -- > > Key: NIFI-2746 > URL: https://issues.apache.org/jira/browse/NIFI-2746 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.1.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.1.0 > > > When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an > error, and the logs show a Null Pointer: > 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > java.lang.NullPointerException: null > at > org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) > ~[classes/:na] > at > org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) > ~[classes/:na] > at > org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) > ~[classes/:na] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_91] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_91] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > [jersey-servlet-1.19.jar:1.19] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [javax.servlet-api-3.1.0.jar:3.1.0] > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) > [jetty-servlets-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.apache.nifi.web.filter.RequestLogger.doFilter(RequestLogger.java:66) > [classes/:na] >
[GitHub] nifi pull request #993: NIFI-2746: Ensure that the FlowController is injecte...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/993 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2746) Error when accessing User page
[ https://issues.apache.org/jira/browse/NIFI-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471387#comment-15471387 ] ASF subversion and git services commented on NIFI-2746: --- Commit 938e32ed97265c4b084c3405b79c493f1b08d91c in nifi's branch refs/heads/master from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=938e32e ] NIFI-2746: Ensure that the FlowController is injected into all ResourceApplications. This closes #993 > Error when accessing User page > -- > > Key: NIFI-2746 > URL: https://issues.apache.org/jira/browse/NIFI-2746 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.1.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.1.0 > > > When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an > error, and the logs show a Null Pointer: > 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > java.lang.NullPointerException: null > at > org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) > ~[classes/:na] > at > org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) > ~[classes/:na] > at > org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) > ~[classes/:na] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_91] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_91] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > [jersey-servlet-1.19.jar:1.19] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [javax.servlet-api-3.1.0.jar:3.1.0] > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) > [jetty-servlets-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$Cached
[jira] [Commented] (NIFI-2746) Error when accessing User page
[ https://issues.apache.org/jira/browse/NIFI-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471389#comment-15471389 ] ASF GitHub Bot commented on NIFI-2746: -- Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/993 Thanks @markap14. This has been merged to master. > Error when accessing User page > -- > > Key: NIFI-2746 > URL: https://issues.apache.org/jira/browse/NIFI-2746 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.1.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.1.0 > > > When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an > error, and the logs show a Null Pointer: > 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > java.lang.NullPointerException: null > at > org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) > ~[classes/:na] > at > org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) > ~[classes/:na] > at > org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) > ~[classes/:na] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_91] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_91] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > [jersey-servlet-1.19.jar:1.19] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [javax.servlet-api-3.1.0.jar:3.1.0] > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) > [jetty-servlets-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.apache.nifi.web.filter.RequestLogger.doFi
[GitHub] nifi issue #993: NIFI-2746: Ensure that the FlowController is injected into ...
Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/993 Thanks @markap14. This has been merged to master. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2724) JMX Processor
[ https://issues.apache.org/jira/browse/NIFI-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Burnett updated NIFI-2724: Labels: processor (was: newbie processor) Status: Patch Available (was: Open) Contribution for NIFI-2724 JMX Processor > JMX Processor > - > > Key: NIFI-2724 > URL: https://issues.apache.org/jira/browse/NIFI-2724 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Affects Versions: 1.0.0 > Environment: All platforms with Java RMI support for JMX >Reporter: Brian Burnett >Priority: Minor > Labels: processor > Fix For: 1.1.0 > > Attachments: 0001-NIFI-2724-New-JMX-Processor.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > The JMX Processor feature addition includes only GetJMX without > SecurityManager capabilities at this time. The processor in its current > state is capable of pulling MBean Property and Attribute values from a remote > RMI Server. Each set of Mbean data is wrapped in a JSON formatted FlowFile > for downstream processing. It has the ability to control content with > whitelist and blacklist properties. > Possible use for this processor and the reason it was created is to help make > sense of Kafka server metrics. > Will followup with a SecurityManager Context Service and PutJMX Processor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2724) JMX Processor
[ https://issues.apache.org/jira/browse/NIFI-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Burnett updated NIFI-2724: Attachment: 0001-NIFI-2724-New-JMX-Processor.patch Contribution git patch file for NIFI-2724 JMX Processor > JMX Processor > - > > Key: NIFI-2724 > URL: https://issues.apache.org/jira/browse/NIFI-2724 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Affects Versions: 1.0.0 > Environment: All platforms with Java RMI support for JMX >Reporter: Brian Burnett >Priority: Minor > Labels: newbie, processor > Fix For: 1.1.0 > > Attachments: 0001-NIFI-2724-New-JMX-Processor.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > The JMX Processor feature addition includes only GetJMX without > SecurityManager capabilities at this time. The processor in its current > state is capable of pulling MBean Property and Attribute values from a remote > RMI Server. Each set of Mbean data is wrapped in a JSON formatted FlowFile > for downstream processing. It has the ability to control content with > whitelist and blacklist properties. > Possible use for this processor and the reason it was created is to help make > sense of Kafka server metrics. > Will followup with a SecurityManager Context Service and PutJMX Processor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2262) SQL processors fail if column name contains characters illegal for Avro
[ https://issues.apache.org/jira/browse/NIFI-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-2262: --- Status: Patch Available (was: In Progress) > SQL processors fail if column name contains characters illegal for Avro > --- > > Key: NIFI-2262 > URL: https://issues.apache.org/jira/browse/NIFI-2262 > Project: Apache NiFi > Issue Type: Bug >Reporter: Matt Burgess >Assignee: Matt Burgess > > For SQL processors that output Avro (ExecuteSQL, QueryDatabaseTable, etc.), > if the SQL result set contains columns whose names contain Avro-illegal > characters (such as a period), then an error occurs: > org.apache.avro.SchemaParseException: Illegal character in: user.gender > These processors should either normalize the names for Avro automatically or > have a property indicating whether names should be normalized. > A workaround for ExecuteSQL in many cases is to alias the columns in the SQL. > This approach doesn't currently work in QueryDatabaseTable for incremental > fetch (i.e. maximum-value columns) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2262) SQL processors fail if column name contains characters illegal for Avro
[ https://issues.apache.org/jira/browse/NIFI-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471333#comment-15471333 ] ASF GitHub Bot commented on NIFI-2262: -- GitHub user mattyb149 opened a pull request: https://github.com/apache/nifi/pull/994 NIFI-2262: Added Avro-normalization of table/column names in SQL processors Affected processors are QueryDatabaseTable and ExecuteSQL, since they generate Avro output. GenerateTableFetch is not affected as it generates SQL, however I added the property to the AbstractDatabaseFetchProcessor class so it could be reused by future processors. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mattyb149/nifi NIFI-2262 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/994.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #994 commit f452d36d076200084cf0c8823979a948a070adc2 Author: Matt Burgess Date: 2016-09-07T17:53:47Z NIFI-2262: Added Avro-normalization of table/column names in SQL processors > SQL processors fail if column name contains characters illegal for Avro > --- > > Key: NIFI-2262 > URL: https://issues.apache.org/jira/browse/NIFI-2262 > Project: Apache NiFi > Issue Type: Bug >Reporter: Matt Burgess >Assignee: Matt Burgess > > For SQL processors that output Avro (ExecuteSQL, QueryDatabaseTable, etc.), > if the SQL result set contains columns whose names contain Avro-illegal > characters (such as a period), then an error occurs: > org.apache.avro.SchemaParseException: Illegal character in: user.gender > These processors should either normalize the names for Avro automatically or > have a property indicating whether names should be normalized. > A workaround for ExecuteSQL in many cases is to alias the columns in the SQL. > This approach doesn't currently work in QueryDatabaseTable for incremental > fetch (i.e. maximum-value columns) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #994: NIFI-2262: Added Avro-normalization of table/column ...
GitHub user mattyb149 opened a pull request: https://github.com/apache/nifi/pull/994 NIFI-2262: Added Avro-normalization of table/column names in SQL processors Affected processors are QueryDatabaseTable and ExecuteSQL, since they generate Avro output. GenerateTableFetch is not affected as it generates SQL, however I added the property to the AbstractDatabaseFetchProcessor class so it could be reused by future processors. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mattyb149/nifi NIFI-2262 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/994.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #994 commit f452d36d076200084cf0c8823979a948a070adc2 Author: Matt Burgess Date: 2016-09-07T17:53:47Z NIFI-2262: Added Avro-normalization of table/column names in SQL processors --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2714) Whitelist and Blacklist for Topics in ConsumeKafka
[ https://issues.apache.org/jira/browse/NIFI-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471263#comment-15471263 ] Sam Hjelmfelt commented on NIFI-2714: - Yes, that would be fine. Thanks. > Whitelist and Blacklist for Topics in ConsumeKafka > -- > > Key: NIFI-2714 > URL: https://issues.apache.org/jira/browse/NIFI-2714 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Sam Hjelmfelt >Assignee: Joseph Witt >Priority: Minor > > The Kafka API has methods to receive a pattern when selecting the topics to > consume. Allowing the user to provide a whitelist or blacklist regular > expression would improve the flexibility of this processor. This is similar > functionality to what is supported by the Kafka mirrormaker. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2746) Error when accessing User page
[ https://issues.apache.org/jira/browse/NIFI-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471249#comment-15471249 ] ASF GitHub Bot commented on NIFI-2746: -- Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/993 Reviewing... > Error when accessing User page > -- > > Key: NIFI-2746 > URL: https://issues.apache.org/jira/browse/NIFI-2746 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.1.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.1.0 > > > When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an > error, and the logs show a Null Pointer: > 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > java.lang.NullPointerException: null > at > org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) > ~[classes/:na] > at > org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) > ~[classes/:na] > at > org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) > ~[classes/:na] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_91] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_91] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > [jersey-servlet-1.19.jar:1.19] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [javax.servlet-api-3.1.0.jar:3.1.0] > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) > [jetty-servlets-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.apache.nifi.web.filter.RequestLogger.doFilter(RequestLogger.java:66) > [class
[GitHub] nifi issue #993: NIFI-2746: Ensure that the FlowController is injected into ...
Github user mcgilman commented on the issue: https://github.com/apache/nifi/pull/993 Reviewing... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (NIFI-2746) Error when accessing User page
[ https://issues.apache.org/jira/browse/NIFI-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-2746: - Assignee: Mark Payne Status: Patch Available (was: Open) > Error when accessing User page > -- > > Key: NIFI-2746 > URL: https://issues.apache.org/jira/browse/NIFI-2746 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.1.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.1.0 > > > When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an > error, and the logs show a Null Pointer: > 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > java.lang.NullPointerException: null > at > org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) > ~[classes/:na] > at > org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) > ~[classes/:na] > at > org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) > ~[classes/:na] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_91] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_91] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > [jersey-servlet-1.19.jar:1.19] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [javax.servlet-api-3.1.0.jar:3.1.0] > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) > [jetty-servlets-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.apache.nifi.web.filter.RequestLogger.doFilter(RequestLogger.java:66) > [classes/:na] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:167
[jira] [Commented] (NIFI-2746) Error when accessing User page
[ https://issues.apache.org/jira/browse/NIFI-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471231#comment-15471231 ] ASF GitHub Bot commented on NIFI-2746: -- GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/993 NIFI-2746: Ensure that the FlowController is injected into all ResourceApplications You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-2746 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/993.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #993 > Error when accessing User page > -- > > Key: NIFI-2746 > URL: https://issues.apache.org/jira/browse/NIFI-2746 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.1.0 >Reporter: Mark Payne >Priority: Blocker > Fix For: 1.1.0 > > > When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an > error, and the logs show a Null Pointer: > 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] > o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: > java.lang.NullPointerException. Returning Internal Server Error response. > java.lang.NullPointerException: null > at > org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) > ~[classes/:na] > at > org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) > ~[classes/:na] > at > org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) > ~[classes/:na] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[na:1.8.0_91] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[na:1.8.0_91] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[na:1.8.0_91] > at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) > ~[jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) > [jersey-server-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) > [jersey-servlet-1.19.jar:1.19] > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) > [jersey-servlet-1.19.jar:1.19] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > [javax.servlet-api-3.1.0.jar:3.1.0] > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) > [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:168
[GitHub] nifi pull request #993: NIFI-2746: Ensure that the FlowController is injecte...
GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/993 NIFI-2746: Ensure that the FlowController is injected into all ResourceApplications You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-2746 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/993.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #993 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-2746) Error when accessing User page
Mark Payne created NIFI-2746: Summary: Error when accessing User page Key: NIFI-2746 URL: https://issues.apache.org/jira/browse/NIFI-2746 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.1.0 Reporter: Mark Payne Priority: Blocker Fix For: 1.1.0 When I try to navigate to the Users page in 1.1.0-SNAPSHOT, I am seeing an error, and the logs show a Null Pointer: 2016-09-07 16:42:25,129 ERROR [NiFi Web Server-33364] o.a.nifi.web.api.config.ThrowableMapper An unexpected error has occurred: java.lang.NullPointerException. Returning Internal Server Error response. java.lang.NullPointerException: null at org.apache.nifi.web.api.ApplicationResource.ensureFlowInitialized(ApplicationResource.java:764) ~[classes/:na] at org.apache.nifi.web.api.ApplicationResource.isReplicateRequest(ApplicationResource.java:402) ~[classes/:na] at org.apache.nifi.web.api.TenantsResource.getUsers(TenantsResource.java:285) ~[classes/:na] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_91] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_91] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_91] at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_91] at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) ~[jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542) [jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473) [jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419) [jersey-server-1.19.jar:1.19] at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409) [jersey-server-1.19.jar:1.19] at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409) [jersey-servlet-1.19.jar:1.19] at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558) [jersey-servlet-1.19.jar:1.19] at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733) [jersey-servlet-1.19.jar:1.19] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [javax.servlet-api-3.1.0.jar:3.1.0] at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:51) [jetty-servlets-9.3.9.v20160517.jar:9.3.9.v20160517] at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] at org.apache.nifi.web.filter.RequestLogger.doFilter(RequestLogger.java:66) [classes/:na] at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1676) [jetty-servlet-9.3.9.v20160517.jar:9.3.9.v20160517] at ... This appears to affect only the master branch and no previously released artifacts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2262) SQL processors fail if column name contains characters illegal for Avro
[ https://issues.apache.org/jira/browse/NIFI-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess reassigned NIFI-2262: -- Assignee: Matt Burgess > SQL processors fail if column name contains characters illegal for Avro > --- > > Key: NIFI-2262 > URL: https://issues.apache.org/jira/browse/NIFI-2262 > Project: Apache NiFi > Issue Type: Bug >Reporter: Matt Burgess >Assignee: Matt Burgess > > For SQL processors that output Avro (ExecuteSQL, QueryDatabaseTable, etc.), > if the SQL result set contains columns whose names contain Avro-illegal > characters (such as a period), then an error occurs: > org.apache.avro.SchemaParseException: Illegal character in: user.gender > These processors should either normalize the names for Avro automatically or > have a property indicating whether names should be normalized. > A workaround for ExecuteSQL in many cases is to alias the columns in the SQL. > This approach doesn't currently work in QueryDatabaseTable for incremental > fetch (i.e. maximum-value columns) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2741) move all apache dependencies version to parent pom properties and replace version values with property strings
[
https://issues.apache.org/jira/browse/NIFI-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471021#comment-15471021
]
ASF subversion and git services commented on NIFI-2741:
---
Commit 80224e3e5ed7ee7b09c4985a920a7fa393bff26c in nifi's branch
refs/heads/master from [~vijay_k]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=80224e3 ]
NIFI-2741 Move HBase, Storm, Hive, and Kafka versions into properties.
Signed-off-by: Bryan Bende
> move all apache dependencies version to parent pom properties and replace
> version values with property strings
> --
>
> Key: NIFI-2741
> URL: https://issues.apache.org/jira/browse/NIFI-2741
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Vijay Kumar
>Assignee: Bryan Bende
> Fix For: 1.1.0
>
> Attachments:
> 0001-NIFI-2741-move-apache-dependencies-version-to-parent.patch
>
>
> For instance:
> https://github.com/apache/nifi/blob/master/nifi-external/nifi-storm-spout/pom.xml#L30
> Could be replaced with storm.version with parent pom.xml properties section
> updated as:
> {code}
>
> 1.0.1
>
> {code}
> Similarly:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hbase-bundle/pom.xml#L43
>
> Could be replaced with parent pom update:
> {code}
>
> 1.1.2
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #990: NIFI-2744 - turn hbase-client version into a pom.xml proper...
Github user bbende commented on the issue: https://github.com/apache/nifi/pull/990 @trixpan I just merged in a patch for https://issues.apache.org/jira/browse/NIFI-2741 that includes this same change, if you are good with it I think we can close this PR and JIRA. Sorry for the duplicate work. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (NIFI-2741) move all apache dependencies version to parent pom properties and replace version values with property strings
[
https://issues.apache.org/jira/browse/NIFI-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende resolved NIFI-2741.
---
Resolution: Fixed
> move all apache dependencies version to parent pom properties and replace
> version values with property strings
> --
>
> Key: NIFI-2741
> URL: https://issues.apache.org/jira/browse/NIFI-2741
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Vijay Kumar
>Assignee: Bryan Bende
> Fix For: 1.1.0
>
> Attachments:
> 0001-NIFI-2741-move-apache-dependencies-version-to-parent.patch
>
>
> For instance:
> https://github.com/apache/nifi/blob/master/nifi-external/nifi-storm-spout/pom.xml#L30
> Could be replaced with storm.version with parent pom.xml properties section
> updated as:
> {code}
>
> 1.0.1
>
> {code}
> Similarly:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hbase-bundle/pom.xml#L43
>
> Could be replaced with parent pom update:
> {code}
>
> 1.1.2
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2744) pom files should allow hbase version to be overwritten
[
https://issues.apache.org/jira/browse/NIFI-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471036#comment-15471036
]
ASF GitHub Bot commented on NIFI-2744:
--
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/990
No worries
> pom files should allow hbase version to be overwritten
> --
>
> Key: NIFI-2744
> URL: https://issues.apache.org/jira/browse/NIFI-2744
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As part of 1.0.0 we allowed users to compile NiFi against vendor maintained
> repositories.
> While this works very well for Hadoop (and HDFS), we have not allowed users
> to overwrite the HBASE version to use particular versions supported by a
> vendor (e.g. use {{1.1.1-mapr-1602-m7-5.1.0}} to enable NiFi to write into
> MapR-DB)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2744) pom files should allow hbase version to be overwritten
[
https://issues.apache.org/jira/browse/NIFI-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471034#comment-15471034
]
ASF GitHub Bot commented on NIFI-2744:
--
Github user trixpan closed the pull request at:
https://github.com/apache/nifi/pull/990
> pom files should allow hbase version to be overwritten
> --
>
> Key: NIFI-2744
> URL: https://issues.apache.org/jira/browse/NIFI-2744
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As part of 1.0.0 we allowed users to compile NiFi against vendor maintained
> repositories.
> While this works very well for Hadoop (and HDFS), we have not allowed users
> to overwrite the HBASE version to use particular versions supported by a
> vendor (e.g. use {{1.1.1-mapr-1602-m7-5.1.0}} to enable NiFi to write into
> MapR-DB)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #990: NIFI-2744 - turn hbase-client version into a pom.xml proper...
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/990 No worries --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #990: NIFI-2744 - turn hbase-client version into a pom.xml...
Github user trixpan closed the pull request at: https://github.com/apache/nifi/pull/990 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2744) pom files should allow hbase version to be overwritten
[
https://issues.apache.org/jira/browse/NIFI-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471025#comment-15471025
]
ASF GitHub Bot commented on NIFI-2744:
--
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/990
@trixpan I just merged in a patch for
https://issues.apache.org/jira/browse/NIFI-2741 that includes this same
change, if you are good with it I think we can close this PR and JIRA. Sorry
for the duplicate work.
> pom files should allow hbase version to be overwritten
> --
>
> Key: NIFI-2744
> URL: https://issues.apache.org/jira/browse/NIFI-2744
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As part of 1.0.0 we allowed users to compile NiFi against vendor maintained
> repositories.
> While this works very well for Hadoop (and HDFS), we have not allowed users
> to overwrite the HBASE version to use particular versions supported by a
> vendor (e.g. use {{1.1.1-mapr-1602-m7-5.1.0}} to enable NiFi to write into
> MapR-DB)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2741) move all apache dependencies version to parent pom properties and replace version values with property strings
[
https://issues.apache.org/jira/browse/NIFI-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471006#comment-15471006
]
Bryan Bende commented on NIFI-2741:
---
+1 Having these as properties is helpful for those who want to override them at
build time, verified this builds cleanly, will merge to master. Thanks Vijay.
> move all apache dependencies version to parent pom properties and replace
> version values with property strings
> --
>
> Key: NIFI-2741
> URL: https://issues.apache.org/jira/browse/NIFI-2741
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Vijay Kumar
>Assignee: Bryan Bende
> Fix For: 1.1.0
>
> Attachments:
> 0001-NIFI-2741-move-apache-dependencies-version-to-parent.patch
>
>
> For instance:
> https://github.com/apache/nifi/blob/master/nifi-external/nifi-storm-spout/pom.xml#L30
> Could be replaced with storm.version with parent pom.xml properties section
> updated as:
> {code}
>
> 1.0.1
>
> {code}
> Similarly:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hbase-bundle/pom.xml#L43
>
> Could be replaced with parent pom update:
> {code}
>
> 1.1.2
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (NIFI-2741) move all apache dependencies version to parent pom properties and replace version values with property strings
[
https://issues.apache.org/jira/browse/NIFI-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende reassigned NIFI-2741:
-
Assignee: Bryan Bende
> move all apache dependencies version to parent pom properties and replace
> version values with property strings
> --
>
> Key: NIFI-2741
> URL: https://issues.apache.org/jira/browse/NIFI-2741
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 1.0.0
>Reporter: Vijay Kumar
>Assignee: Bryan Bende
> Fix For: 1.1.0
>
> Attachments:
> 0001-NIFI-2741-move-apache-dependencies-version-to-parent.patch
>
>
> For instance:
> https://github.com/apache/nifi/blob/master/nifi-external/nifi-storm-spout/pom.xml#L30
> Could be replaced with storm.version with parent pom.xml properties section
> updated as:
> {code}
>
> 1.0.1
>
> {code}
> Similarly:
> https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hbase-bundle/pom.xml#L43
>
> Could be replaced with parent pom update:
> {code}
>
> 1.1.2
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470927#comment-15470927 ] Oleg Zhurakousky commented on NIFI-2745: The new attribute that will be injected into FlowFile is "jms.source.destination" and will correspond to the immediate destination a message was retrieved from. It may still match _jms_destination_ header > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated NIFI-2745: --- Status: Patch Available (was: Open) > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #992: NIFI-2745 added _source destination name_ attribute ...
GitHub user olegz opened a pull request: https://github.com/apache/nifi/pull/992 NIFI-2745 added _source destination name_ attribute to ConsumeJMS You can merge this pull request into a Git repository by running: $ git pull https://github.com/olegz/nifi NIFI-2745 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/992.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #992 commit ce8a8159a280d87bb9ace04b654b577839793345 Author: Oleg Zhurakousky Date: 2016-09-07T15:04:54Z NIFI-2745 added _source destination name_ attribute to ConsumeJMS --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470866#comment-15470866 ] ASF GitHub Bot commented on NIFI-2745: -- GitHub user olegz opened a pull request: https://github.com/apache/nifi/pull/992 NIFI-2745 added _source destination name_ attribute to ConsumeJMS You can merge this pull request into a Git repository by running: $ git pull https://github.com/olegz/nifi NIFI-2745 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/992.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #992 commit ce8a8159a280d87bb9ace04b654b577839793345 Author: Oleg Zhurakousky Date: 2016-09-07T15:04:54Z NIFI-2745 added _source destination name_ attribute to ConsumeJMS > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2383) ListFile does not detect new files
[ https://issues.apache.org/jira/browse/NIFI-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470857#comment-15470857 ] Joe Skora commented on NIFI-2383: - [~nadih], any more thoughts or feedback on this? > ListFile does not detect new files > -- > > Key: NIFI-2383 > URL: https://issues.apache.org/jira/browse/NIFI-2383 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: n h > Labels: ListFile > Fix For: 0.7.1 > > > ListFile does not detect directory updates correctly. It seems it only check > for file name and modified date. > Using a 2 processors flow: ListFile -> FetchFile, and configure FetchFile to > finally delete files. Following scenario fails: > 1. Create file1.txt somewhere outside of watching directory. > 2. Copy file1.txt to watching directory. > 3. Wait for FetchFile to fetch and delete file1.txt > 4. Copy file1.txt again to watching directory. > In the 2nd time ListFile does not detect "new copy of the same file > file1.txt" because file name and modified time are the same. Only creation > time is updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pradeep arumalla updated NIFI-2409: --- Attachment: screenshot-2.png > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > Attachments: screenshot-1.png, screenshot-2.png > > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470827#comment-15470827 ] pradeep arumalla commented on NIFI-2409: also, to confirm/verify that it worked for sometime, in screenshot-2, there are some files written using the same StoreInKiteDataset processor. Please ask for any information you need. > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > Attachments: screenshot-1.png, screenshot-2.png > > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470797#comment-15470797 ] pradeep arumalla commented on NIFI-2409: sorry for being late, please see the screen shot attached. > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > Attachments: screenshot-1.png > > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pradeep arumalla updated NIFI-2409: --- Attachment: screenshot-1.png > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > Attachments: screenshot-1.png > > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pradeep arumalla updated NIFI-2409: --- Attachment: screenshot-1.png > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] pradeep arumalla updated NIFI-2409: --- Attachment: (was: screenshot-1.png) > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky updated NIFI-2745: --- Fix Version/s: 1.1.0 > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
[ https://issues.apache.org/jira/browse/NIFI-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Zhurakousky reassigned NIFI-2745: -- Assignee: Oleg Zhurakousky > Add source destination to FlowFile attribute in ConsumeJMS processor > - > > Key: NIFI-2745 > URL: https://issues.apache.org/jira/browse/NIFI-2745 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David A. Wynne >Assignee: Oleg Zhurakousky >Priority: Minor > Fix For: 1.1.0 > > > The 'destination_name" header does not always correspond to the source > destination when consuming messages. This is managed by JMS provider and > depends on a lot of factors. So we essentially need additional attribute > (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2745) Add source destination to FlowFile attribute in ConsumeJMS processor
David A. Wynne created NIFI-2745: Summary: Add source destination to FlowFile attribute in ConsumeJMS processor Key: NIFI-2745 URL: https://issues.apache.org/jira/browse/NIFI-2745 Project: Apache NiFi Issue Type: Improvement Reporter: David A. Wynne Priority: Minor The 'destination_name" header does not always correspond to the source destination when consuming messages. This is managed by JMS provider and depends on a lot of factors. So we essentially need additional attribute (i.e., "source.destination") in FlowFile attributes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1966) Address Issue of Nodes Disagreeing About Flow Contents on Startup
[ https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470763#comment-15470763 ] Matt Gilman commented on NIFI-1966: --- Adding migration label as we need to document the new properties for voting on the flow. > Address Issue of Nodes Disagreeing About Flow Contents on Startup > - > > Key: NIFI-1966 > URL: https://issues.apache.org/jira/browse/NIFI-1966 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne >Priority: Blocker > Labels: migration > Fix For: 1.1.0 > > > During startup a coordinator is selected at random to act as the manager of > data flow and distributing it to other nodes. This works fine unless that > selected coordinator happens to have a uninheritable data flow. When this > occurs, the other nodes either are > - Able to connect to Coordinator and then unable to join due to an > uninheritable flow exception due to being presented with a bad data flow. In > this case, the node shut down. > - Unable to connect to the Coordinator due to lack of quorem and never > present with the bad data flow. In this case, the node ran its local flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1966) Address Issue of Nodes Disagreeing About Flow Contents on Startup
[ https://issues.apache.org/jira/browse/NIFI-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1966: -- Labels: migration (was: ) > Address Issue of Nodes Disagreeing About Flow Contents on Startup > - > > Key: NIFI-1966 > URL: https://issues.apache.org/jira/browse/NIFI-1966 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne >Priority: Blocker > Labels: migration > Fix For: 1.1.0 > > > During startup a coordinator is selected at random to act as the manager of > data flow and distributing it to other nodes. This works fine unless that > selected coordinator happens to have a uninheritable data flow. When this > occurs, the other nodes either are > - Able to connect to Coordinator and then unable to join due to an > uninheritable flow exception due to being presented with a bad data flow. In > this case, the node shut down. > - Unable to connect to the Coordinator due to lack of quorem and never > present with the bad data flow. In this case, the node ran its local flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2706) Update website graphics and basic styling
[ https://issues.apache.org/jira/browse/NIFI-2706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470755#comment-15470755 ] ASF GitHub Bot commented on NIFI-2706: -- Github user moranr closed the pull request at: https://github.com/apache/nifi-site/pull/4 > Update website graphics and basic styling > - > > Key: NIFI-2706 > URL: https://issues.apache.org/jira/browse/NIFI-2706 > Project: Apache NiFi > Issue Type: Task > Components: Documentation & Website >Reporter: Rob Moran >Assignee: Rob Moran > > Update the Apache NiFi website graphics, app screenshot, and background > colors to match redesigned UI. This task will also include similar updates to > the MiNiFi section of the website. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi-site pull request #4: NIFI-2706 new updates to MiNiFi section of site -...
Github user moranr closed the pull request at: https://github.com/apache/nifi-site/pull/4 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Resolved] (NIFI-2739) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker
[ https://issues.apache.org/jira/browse/NIFI-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne resolved NIFI-2739. -- Resolution: Fixed > ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to > communicate with Kafka broker > > > Key: NIFI-2739 > URL: https://issues.apache.org/jira/browse/NIFI-2739 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne > Fix For: 1.1.0 > > > If I use ConsumeKafka and point to a broker that is in a bad state, I see > ConsumeKafka block indefinitely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2739) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker
[ https://issues.apache.org/jira/browse/NIFI-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470550#comment-15470550 ] ASF subversion and git services commented on NIFI-2739: --- Commit 8d6e12fdc4002f6eba52edcf0670df40217eb43a in nifi's branch refs/heads/master from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=8d6e12f ] NIFI-2739: Call KafkaConsumer.wakeup() if consumer is blocking for at least 30 seconds when OnUnscheduled is called > ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to > communicate with Kafka broker > > > Key: NIFI-2739 > URL: https://issues.apache.org/jira/browse/NIFI-2739 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne > Fix For: 1.1.0 > > > If I use ConsumeKafka and point to a broker that is in a bad state, I see > ConsumeKafka block indefinitely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2739) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker
[ https://issues.apache.org/jira/browse/NIFI-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470552#comment-15470552 ] ASF GitHub Bot commented on NIFI-2739: -- Github user markap14 closed the pull request at: https://github.com/apache/nifi/pull/989 > ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to > communicate with Kafka broker > > > Key: NIFI-2739 > URL: https://issues.apache.org/jira/browse/NIFI-2739 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne > Fix For: 1.1.0 > > > If I use ConsumeKafka and point to a broker that is in a bad state, I see > ConsumeKafka block indefinitely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi pull request #989: NIFI-2739: Call KafkaConsumer.wakeup() if consumer i...
Github user markap14 closed the pull request at: https://github.com/apache/nifi/pull/989 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2739) ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to communicate with Kafka broker
[ https://issues.apache.org/jira/browse/NIFI-2739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470548#comment-15470548 ] ASF GitHub Bot commented on NIFI-2739: -- Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/989 @joewitt I actually went back & forth trying to decide if I should use 30 secs or 5 secs. I went with 30 secs just because it's what we use most often for default timeouts, but you're probably right - 5 secs is probably more than sufficient. Will update to use only 5 secs and then push. Thanks for reviewing! > ConsumeKafka and ConsumeKafka_0_10 can block indefinitely if unable to > communicate with Kafka broker > > > Key: NIFI-2739 > URL: https://issues.apache.org/jira/browse/NIFI-2739 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Reporter: Mark Payne >Assignee: Mark Payne > Fix For: 1.1.0 > > > If I use ConsumeKafka and point to a broker that is in a bad state, I see > ConsumeKafka block indefinitely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] nifi issue #989: NIFI-2739: Call KafkaConsumer.wakeup() if consumer is block...
Github user markap14 commented on the issue: https://github.com/apache/nifi/pull/989 @joewitt I actually went back & forth trying to decide if I should use 30 secs or 5 secs. I went with 30 secs just because it's what we use most often for default timeouts, but you're probably right - 5 secs is probably more than sufficient. Will update to use only 5 secs and then push. Thanks for reviewing! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] nifi pull request #988: NIFI-2735: Add AggregateValues processor for aggrega...
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/988#discussion_r77811419
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/AggregateValues.java
---
@@ -0,0 +1,580 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import com.jayway.jsonpath.Configuration;
+import com.jayway.jsonpath.DocumentContext;
+import com.jayway.jsonpath.InvalidJsonException;
+import com.jayway.jsonpath.JsonPath;
+import com.jayway.jsonpath.PathNotFoundException;
+import com.jayway.jsonpath.spi.json.JacksonJsonProvider;
+import net.sf.saxon.lib.NamespaceConstant;
+import net.sf.saxon.xpath.XPathEvaluator;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.ReadsAttribute;
+import org.apache.nifi.annotation.behavior.ReadsAttributes;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.Stateful;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.state.Scope;
+import org.apache.nifi.components.state.StateManager;
+import org.apache.nifi.components.state.StateMap;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.processor.AbstractSessionFactoryProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.ProcessSessionFactory;
+import org.apache.nifi.processor.ProcessorInitializationContext;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.stream.io.BufferedInputStream;
+import org.xml.sax.InputSource;
+
+import javax.xml.transform.Source;
+import javax.xml.xpath.XPathConstants;
+import javax.xml.xpath.XPathExpression;
+import javax.xml.xpath.XPathExpressionException;
+import javax.xml.xpath.XPathFactory;
+import javax.xml.xpath.XPathFactoryConfigurationException;
+import java.io.BufferedReader;
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.InputStreamReader;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+import static javax.xml.xpath.XPathConstants.NODESET;
+
+/**
+ * A processor to intermediateAggregate values from incoming flow files.
The flow files are expected to have certain attributes set to allow for
+ * aggregations over a batch of flow files.
+ */
+@EventDriven
+@SideEffectFree
+@SupportsBatching
+@Tags({"json", "xml", "csv", "aggregate"})
+@SeeAlso({SplitText.class, SplitJson.class, SplitXml.class})
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
+@CapabilityDescription("Aggregates values from incoming flow files based
on a path to the desired field and an aggregation operation (SUM, AVG, etc.). "
++ "The flow files are expected to have mime.type, fragment.count,
fragment.identi
[jira] [Commented] (NIFI-2735) Add processor to perform simple aggregations
[
https://issues.apache.org/jira/browse/NIFI-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470471#comment-15470471
]
ASF GitHub Bot commented on NIFI-2735:
--
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/988#discussion_r77811419
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/AggregateValues.java
---
@@ -0,0 +1,580 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import com.jayway.jsonpath.Configuration;
+import com.jayway.jsonpath.DocumentContext;
+import com.jayway.jsonpath.InvalidJsonException;
+import com.jayway.jsonpath.JsonPath;
+import com.jayway.jsonpath.PathNotFoundException;
+import com.jayway.jsonpath.spi.json.JacksonJsonProvider;
+import net.sf.saxon.lib.NamespaceConstant;
+import net.sf.saxon.xpath.XPathEvaluator;
+import org.apache.commons.lang3.StringUtils;
+import org.apache.nifi.annotation.behavior.EventDriven;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.ReadsAttribute;
+import org.apache.nifi.annotation.behavior.ReadsAttributes;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.Stateful;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.behavior.WritesAttribute;
+import org.apache.nifi.annotation.behavior.WritesAttributes;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.SeeAlso;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.components.state.Scope;
+import org.apache.nifi.components.state.StateManager;
+import org.apache.nifi.components.state.StateMap;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.flowfile.attributes.CoreAttributes;
+import org.apache.nifi.logging.ComponentLog;
+import org.apache.nifi.processor.AbstractSessionFactoryProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.ProcessSessionFactory;
+import org.apache.nifi.processor.ProcessorInitializationContext;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+import org.apache.nifi.stream.io.BufferedInputStream;
+import org.xml.sax.InputSource;
+
+import javax.xml.transform.Source;
+import javax.xml.xpath.XPathConstants;
+import javax.xml.xpath.XPathExpression;
+import javax.xml.xpath.XPathExpressionException;
+import javax.xml.xpath.XPathFactory;
+import javax.xml.xpath.XPathFactoryConfigurationException;
+import java.io.BufferedReader;
+import java.io.IOException;
+import java.io.InputStream;
+import java.io.InputStreamReader;
+import java.util.ArrayList;
+import java.util.Collections;
+import java.util.HashMap;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.concurrent.atomic.AtomicReference;
+
+import static javax.xml.xpath.XPathConstants.NODESET;
+
+/**
+ * A processor to intermediateAggregate values from incoming flow files.
The flow files are expected to have certain attributes set to allow for
+ * aggregations over a batch of flow files.
+ */
+@EventDriven
+@SideEffectFree
+@SupportsBatching
+@Tags({"json", "xml", "csv", "aggregate"})
+@SeeAlso({SplitText.class, SplitJson.class, SplitXml.class})
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
[jira] [Commented] (NIFI-2742) testSchemaFromResourceURI fails when -Pmapr is enabled
[
https://issues.apache.org/jira/browse/NIFI-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470459#comment-15470459
]
ASF GitHub Bot commented on NIFI-2742:
--
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/991
@joewitt I will be happy to address that! Changing the master LICENSE and
NOTICE files is one of my part time hobbies! :neutral_face:
> testSchemaFromResourceURI fails when -Pmapr is enabled
> --
>
> Key: NIFI-2742
> URL: https://issues.apache.org/jira/browse/NIFI-2742
> Project: Apache NiFi
> Issue Type: Wish
>Affects Versions: 1.0.0
> Environment: -Pmapr profile enabled
>Reporter: Andre
>Priority: Minor
>
> Found this compatibility issue when compiling NiFi 1.0.0 against the MapR
> profile:
> {code}
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 2, Time elapsed: 6.064 sec <<<
> FAILURE! - in org.apache.nifi.processors.kite.TestGetSchema
> testSchemaFromResourceURI(org.apache.nifi.processors.kite.TestGetSchema)
> Time elapsed: 6.04 sec <<< ERROR!
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/security/authentication/server/CookieSignatureSecretFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.conf.CoreDefaultProperties.(CoreDefaultProperties.java:297)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2147)
> at
> org.apache.hadoop.conf.Configuration.getProperties(Configuration.java:2362)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2579)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2531)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2444)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:1245)
> at org.apache.hadoop.fs.FileSystem.getDefaultUri(FileSystem.java:180)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:172)
> at
> org.kitesdk.data.DatasetDescriptor$Builder.(DatasetDescriptor.java:354)
> at
> org.apache.nifi.processors.kite.TestGetSchema.testSchemaFromResourceURI(TestGetSchema.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #991: NIFI-2742 - Explicitly declare the kite hadoop dependencies...
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/991 @joewitt I will be happy to address that! Changing the master LICENSE and NOTICE files is one of my part time hobbies! :neutral_face: --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2742) testSchemaFromResourceURI fails when -Pmapr is enabled
[
https://issues.apache.org/jira/browse/NIFI-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470447#comment-15470447
]
ASF GitHub Bot commented on NIFI-2742:
--
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/991
at the very least this PR will require substantive alterations to
LICENSE/NOTICE for the impacted nar(s).
> testSchemaFromResourceURI fails when -Pmapr is enabled
> --
>
> Key: NIFI-2742
> URL: https://issues.apache.org/jira/browse/NIFI-2742
> Project: Apache NiFi
> Issue Type: Wish
>Affects Versions: 1.0.0
> Environment: -Pmapr profile enabled
>Reporter: Andre
>Priority: Minor
>
> Found this compatibility issue when compiling NiFi 1.0.0 against the MapR
> profile:
> {code}
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 2, Time elapsed: 6.064 sec <<<
> FAILURE! - in org.apache.nifi.processors.kite.TestGetSchema
> testSchemaFromResourceURI(org.apache.nifi.processors.kite.TestGetSchema)
> Time elapsed: 6.04 sec <<< ERROR!
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/security/authentication/server/CookieSignatureSecretFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.conf.CoreDefaultProperties.(CoreDefaultProperties.java:297)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2147)
> at
> org.apache.hadoop.conf.Configuration.getProperties(Configuration.java:2362)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2579)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2531)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2444)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:1245)
> at org.apache.hadoop.fs.FileSystem.getDefaultUri(FileSystem.java:180)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:172)
> at
> org.kitesdk.data.DatasetDescriptor$Builder.(DatasetDescriptor.java:354)
> at
> org.apache.nifi.processors.kite.TestGetSchema.testSchemaFromResourceURI(TestGetSchema.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #991: NIFI-2742 - Explicitly declare the kite hadoop dependencies...
Github user joewitt commented on the issue: https://github.com/apache/nifi/pull/991 at the very least this PR will require substantive alterations to LICENSE/NOTICE for the impacted nar(s). --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2742) testSchemaFromResourceURI fails when -Pmapr is enabled
[
https://issues.apache.org/jira/browse/NIFI-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470441#comment-15470441
]
ASF GitHub Bot commented on NIFI-2742:
--
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/991
@rdblue would you have any feedback over this change? Not ideal but I
couldn't find a better way. Open to suggestions
> testSchemaFromResourceURI fails when -Pmapr is enabled
> --
>
> Key: NIFI-2742
> URL: https://issues.apache.org/jira/browse/NIFI-2742
> Project: Apache NiFi
> Issue Type: Wish
>Affects Versions: 1.0.0
> Environment: -Pmapr profile enabled
>Reporter: Andre
>Priority: Minor
>
> Found this compatibility issue when compiling NiFi 1.0.0 against the MapR
> profile:
> {code}
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 2, Time elapsed: 6.064 sec <<<
> FAILURE! - in org.apache.nifi.processors.kite.TestGetSchema
> testSchemaFromResourceURI(org.apache.nifi.processors.kite.TestGetSchema)
> Time elapsed: 6.04 sec <<< ERROR!
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/security/authentication/server/CookieSignatureSecretFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.conf.CoreDefaultProperties.(CoreDefaultProperties.java:297)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2147)
> at
> org.apache.hadoop.conf.Configuration.getProperties(Configuration.java:2362)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2579)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2531)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2444)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:1245)
> at org.apache.hadoop.fs.FileSystem.getDefaultUri(FileSystem.java:180)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:172)
> at
> org.kitesdk.data.DatasetDescriptor$Builder.(DatasetDescriptor.java:354)
> at
> org.apache.nifi.processors.kite.TestGetSchema.testSchemaFromResourceURI(TestGetSchema.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #991: NIFI-2742 - Explicitly declare the kite hadoop dependencies...
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/991 @rdblue would you have any feedback over this change? Not ideal but I couldn't find a better way. Open to suggestions --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2742) testSchemaFromResourceURI fails when -Pmapr is enabled
[
https://issues.apache.org/jira/browse/NIFI-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470435#comment-15470435
]
ASF GitHub Bot commented on NIFI-2742:
--
GitHub user trixpan opened a pull request:
https://github.com/apache/nifi/pull/991
NIFI-2742 - Explicitly declare the kite hadoop dependencies to allow …
…kite-processor to compile against vendor hadoop libraries
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trixpan/nifi NIFI-2742
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/991.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #991
commit 09cc2dae028cc6bf4cb87a8f4cb7caae5562649e
Author: Andre F de Miranda
Date: 2016-09-07T11:59:11Z
NIFI-2742 - Explicitly declare the kite hadoop dependencies to allow
kite-processor to compile against vendor hadoop libraries
> testSchemaFromResourceURI fails when -Pmapr is enabled
> --
>
> Key: NIFI-2742
> URL: https://issues.apache.org/jira/browse/NIFI-2742
> Project: Apache NiFi
> Issue Type: Wish
>Affects Versions: 1.0.0
> Environment: -Pmapr profile enabled
>Reporter: Andre
>Priority: Minor
>
> Found this compatibility issue when compiling NiFi 1.0.0 against the MapR
> profile:
> {code}
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 2, Time elapsed: 6.064 sec <<<
> FAILURE! - in org.apache.nifi.processors.kite.TestGetSchema
> testSchemaFromResourceURI(org.apache.nifi.processors.kite.TestGetSchema)
> Time elapsed: 6.04 sec <<< ERROR!
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/security/authentication/server/CookieSignatureSecretFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.conf.CoreDefaultProperties.(CoreDefaultProperties.java:297)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2147)
> at
> org.apache.hadoop.conf.Configuration.getProperties(Configuration.java:2362)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2579)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2531)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2444)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:1245)
> at org.apache.hadoop.fs.FileSystem.getDefaultUri(FileSystem.java:180)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:172)
> at
> org.kitesdk.data.DatasetDescriptor$Builder.(DatasetDescriptor.java:354)
> at
> org.apache.nifi.processors.kite.TestGetSchema.testSchemaFromResourceURI(TestGetSchema.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi pull request #991: NIFI-2742 - Explicitly declare the kite hadoop depen...
GitHub user trixpan opened a pull request: https://github.com/apache/nifi/pull/991 NIFI-2742 - Explicitly declare the kite hadoop dependencies to allow ⦠â¦kite-processor to compile against vendor hadoop libraries You can merge this pull request into a Git repository by running: $ git pull https://github.com/trixpan/nifi NIFI-2742 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/991.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #991 commit 09cc2dae028cc6bf4cb87a8f4cb7caae5562649e Author: Andre F de Miranda Date: 2016-09-07T11:59:11Z NIFI-2742 - Explicitly declare the kite hadoop dependencies to allow kite-processor to compile against vendor hadoop libraries --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Comment Edited] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470319#comment-15470319 ] Andre edited comment on NIFI-2409 at 9/7/16 11:13 AM: -- [~pradeepbill] any luck with the screenshots? was (Author: trixpan): [~pradeedbill] any luck with the screenshots? > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2409) the dataset url says is invalid, even though it is a valid dataset url
[ https://issues.apache.org/jira/browse/NIFI-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470319#comment-15470319 ] Andre commented on NIFI-2409: - [~pradeedbill] any luck with the screenshots? > the dataset url says is invalid, even though it is a valid dataset url > -- > > Key: NIFI-2409 > URL: https://issues.apache.org/jira/browse/NIFI-2409 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration >Affects Versions: 0.6.1 >Reporter: pradeep arumalla >Priority: Blocker > > hi there, I am using StoreInKiteDataset , and when I give the dataset URI as > "dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset > URI is invalid:unknown dataset URI", not sure why its saying invalid.The same > dataset url worked a week ago. > I used Kite command > >./kite-dataset create dataset:hdfs:/user/xxx/dataset --schema > >hdfs:/user/xxx/schemas/yy.avsc --format parquet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2744) pom files should allow hbase version to be overwritten
[
https://issues.apache.org/jira/browse/NIFI-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470307#comment-15470307
]
ASF GitHub Bot commented on NIFI-2744:
--
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/990
@mattyb149 seems like this one is also required to address @xmlking
concerns around MapR-DB
> pom files should allow hbase version to be overwritten
> --
>
> Key: NIFI-2744
> URL: https://issues.apache.org/jira/browse/NIFI-2744
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As part of 1.0.0 we allowed users to compile NiFi against vendor maintained
> repositories.
> While this works very well for Hadoop (and HDFS), we have not allowed users
> to overwrite the HBASE version to use particular versions supported by a
> vendor (e.g. use {{1.1.1-mapr-1602-m7-5.1.0}} to enable NiFi to write into
> MapR-DB)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi issue #990: NIFI-2744 - turn hbase-client version into a pom.xml proper...
Github user trixpan commented on the issue: https://github.com/apache/nifi/pull/990 @mattyb149 seems like this one is also required to address @xmlking concerns around MapR-DB --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (NIFI-2744) pom files should allow hbase version to be overwritten
[
https://issues.apache.org/jira/browse/NIFI-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470294#comment-15470294
]
ASF GitHub Bot commented on NIFI-2744:
--
GitHub user trixpan opened a pull request:
https://github.com/apache/nifi/pull/990
NIFI-2744 - turn hbase-client version into a pom.xml property
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trixpan/nifi NIFI-2744
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/990.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #990
> pom files should allow hbase version to be overwritten
> --
>
> Key: NIFI-2744
> URL: https://issues.apache.org/jira/browse/NIFI-2744
> Project: Apache NiFi
> Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Andre
>Assignee: Andre
> Fix For: 1.1.0
>
>
> As part of 1.0.0 we allowed users to compile NiFi against vendor maintained
> repositories.
> While this works very well for Hadoop (and HDFS), we have not allowed users
> to overwrite the HBASE version to use particular versions supported by a
> vendor (e.g. use {{1.1.1-mapr-1602-m7-5.1.0}} to enable NiFi to write into
> MapR-DB)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] nifi pull request #990: NIFI-2744 - turn hbase-client version into a pom.xml...
GitHub user trixpan opened a pull request: https://github.com/apache/nifi/pull/990 NIFI-2744 - turn hbase-client version into a pom.xml property You can merge this pull request into a Git repository by running: $ git pull https://github.com/trixpan/nifi NIFI-2744 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/990.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #990 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (NIFI-2744) pom files should allow hbase version to be overwritten
Andre created NIFI-2744:
---
Summary: pom files should allow hbase version to be overwritten
Key: NIFI-2744
URL: https://issues.apache.org/jira/browse/NIFI-2744
Project: Apache NiFi
Issue Type: Improvement
Affects Versions: 1.0.0
Reporter: Andre
Assignee: Andre
Fix For: 1.1.0
As part of 1.0.0 we allowed users to compile NiFi against vendor maintained
repositories.
While this works very well for Hadoop (and HDFS), we have not allowed users to
overwrite the HBASE version to use particular versions supported by a vendor
(e.g. use {{1.1.1-mapr-1602-m7-5.1.0}} to enable NiFi to write into MapR-DB)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2579) Support accessing FlowFile content directly via expression language
[
https://issues.apache.org/jira/browse/NIFI-2579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470068#comment-15470068
]
Raymond commented on NIFI-2579:
---
I agree that first putting the content into an attribute is not logical. I also
have an use case where one needs to dump content or use the content in a script
or sql than one would like to do something like the following expression:
${fileContent}
or if the content isn't a string
${fileContent:toString()}
> Support accessing FlowFile content directly via expression language
> ---
>
> Key: NIFI-2579
> URL: https://issues.apache.org/jira/browse/NIFI-2579
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Randy Gelhausen
>
> If you want to use a FlowFile's content in routing logic, or in metadata for
> external APIs, you must use an ExtractText processor to pull the content into
> an attribute. This is confusing and seems extraneous- the natural inclination
> is to dive into expression language seeking the "content" property which
> doesn't exist today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-2742) testSchemaFromResourceURI fails when -Pmapr is enabled
[
https://issues.apache.org/jira/browse/NIFI-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470003#comment-15470003
]
Andre commented on NIFI-2742:
-
[~ntarasenko], would you have an idea if this is related to
https://issues.cloudera.org/browse/KITE-1061 ?
> testSchemaFromResourceURI fails when -Pmapr is enabled
> --
>
> Key: NIFI-2742
> URL: https://issues.apache.org/jira/browse/NIFI-2742
> Project: Apache NiFi
> Issue Type: Wish
>Affects Versions: 1.0.0
> Environment: -Pmapr profile enabled
>Reporter: Andre
>Priority: Minor
>
> Found this compatibility issue when compiling NiFi 1.0.0 against the MapR
> profile:
> {code}
> Tests run: 3, Failures: 0, Errors: 1, Skipped: 2, Time elapsed: 6.064 sec <<<
> FAILURE! - in org.apache.nifi.processors.kite.TestGetSchema
> testSchemaFromResourceURI(org.apache.nifi.processors.kite.TestGetSchema)
> Time elapsed: 6.04 sec <<< ERROR!
> java.lang.NoClassDefFoundError:
> org/apache/hadoop/security/authentication/server/CookieSignatureSecretFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.conf.CoreDefaultProperties.(CoreDefaultProperties.java:297)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2147)
> at
> org.apache.hadoop.conf.Configuration.getProperties(Configuration.java:2362)
> at
> org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:2579)
> at
> org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:2531)
> at
> org.apache.hadoop.conf.Configuration.getProps(Configuration.java:2444)
> at org.apache.hadoop.conf.Configuration.get(Configuration.java:1245)
> at org.apache.hadoop.fs.FileSystem.getDefaultUri(FileSystem.java:180)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:172)
> at
> org.kitesdk.data.DatasetDescriptor$Builder.(DatasetDescriptor.java:354)
> at
> org.apache.nifi.processors.kite.TestGetSchema.testSchemaFromResourceURI(TestGetSchema.java:89)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
