[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927790#comment-16927790 ] David Sargrad commented on NIFI-6327: - Never mind on the last comment.. I was struggling with a nar file project that had the wrong artifact id... I'm all good now. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png, > image-2019-09-11-09-00-29-639.png, image-2019-09-11-09-05-05-837.png, > image-2019-09-11-09-52-46-872.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927587#comment-16927587 ] David Sargrad edited comment on NIFI-6327 at 9/11/19 1:53 PM: -- Part of my problem is that intellij is loading the class file from the target folder of the source project.. not from the NAR file itself. So the breakpoints aren't lining up. !image-2019-09-11-09-52-46-872.png! was (Author: dsargrad): Part of my problem is that intellij is loading the class file from the target folder of the source project.. not from the NAR file itself. !image-2019-09-11-09-52-46-872.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png, > image-2019-09-11-09-00-29-639.png, image-2019-09-11-09-05-05-837.png, > image-2019-09-11-09-52-46-872.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927587#comment-16927587 ] David Sargrad commented on NIFI-6327: - Part of my problem is that intellij is loading the class file from the target folder of the source project.. not from the NAR file itself. !image-2019-09-11-09-52-46-872.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png, > image-2019-09-11-09-00-29-639.png, image-2019-09-11-09-05-05-837.png, > image-2019-09-11-09-52-46-872.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-09-11-09-52-46-872.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png, > image-2019-09-11-09-00-29-639.png, image-2019-09-11-09-05-05-837.png, > image-2019-09-11-09-52-46-872.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927539#comment-16927539 ] David Sargrad edited comment on NIFI-6327 at 9/11/19 1:05 PM: -- I'm having a fair amount of success with single step debugging in my custom nifi processors. I use the remote debugging option to connect to the instance of NiFi that I've built from source. As you see I can then set a breakpoint right at the point where the server is started. !image-2019-09-11-08-58-20-082.png! II am struggling to find out the proper way to load my NAR file into my intellij project. I've tried to use the Project Structure Settings as follows. I add another library and then browse to my custom nifi project. In the following picture I've browsed to the trunk of "consume_solace_text" !image-2019-09-11-09-00-29-639.png! This sort of seems to work, but intellij seems to get confused by the .class and source files in that project. I am still able to single-step debug, but I sometimes have to unload and reload the project.. Is there a cleaner way for me to point to the "nar" file that contains my built custom processor !image-2019-09-11-09-05-05-837.png! was (Author: dsargrad): I'm having a fair amount of success with single step debugging in my custom nifi processors. I use the remote debugging option to connect to the instance of NiFi that I've built from source. As you see I can then set a breakpoint right at the point where the server is started. !image-2019-09-11-08-58-20-082.png! II am struggling to find out the proper way to load my NAR file into my intellij project. I've tried to use the Project Structure Settings as follows. I add another library and then browse to my custom nifi project. In the following picture I've browsed to the trunk of "consume_solace_text" !image-2019-09-11-09-00-29-639.png! This sort of seems to work, but intellij seems to get confused by the .class and source files in that project. I am still able to single-step debug, but I sometimes have to unload and reload the project.. Is there a cleaner way for me to point to the "nar" file that contains my built custom processor > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png, > image-2019-09-11-09-00-29-639.png, image-2019-09-11-09-05-05-837.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !i
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927539#comment-16927539 ] David Sargrad commented on NIFI-6327: - I'm having a fair amount of success with single step debugging in my custom nifi processors. I use the remote debugging option to connect to the instance of NiFi that I've built from source. As you see I can then set a breakpoint right at the point where the server is started. !image-2019-09-11-08-58-20-082.png! II am struggling to find out the proper way to load my NAR file into my intellij project. I've tried to use the Project Structure Settings as follows. I add another library and then browse to my custom nifi project. In the following picture I've browsed to the trunk of "consume_solace_text" !image-2019-09-11-09-00-29-639.png! This sort of seems to work, but intellij seems to get confused by the .class and source files in that project. I am still able to single-step debug, but I sometimes have to unload and reload the project.. Is there a cleaner way for me to point to the "nar" file that contains my built custom processor > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png, > image-2019-09-11-09-00-29-639.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-09-11-09-00-29-639.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png, > image-2019-09-11-09-00-29-639.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-09-11-08-58-20-082.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png, image-2019-09-11-08-58-20-082.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6488) NiFi web interface often non-responsive
[ https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6488: Attachment: image-2019-08-30-08-03-39-877.png > NiFi web interface often non-responsive > > > Key: NIFI-6488 > URL: https://issues.apache.org/jira/browse/NIFI-6488 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 > Environment: centos 7 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-08-28-08-15-51-702.png, > image-2019-08-30-08-03-39-877.png > > > I have been using NiFi for close to a year. Currently most of my experience > has been with building custom processors and prototyping a variety of flows. > > Often the NiFi web interface becomes non-responsive. Its typically during a > flow integration phase, where I leave flowfiles sitting in queues, sometimes > 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small > flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the > filled queues is in the tens of megabytes. > > I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum > allocated heap size. I'd think that NiFi protects against non-responsive UI's > by shedding load, presenting a warning, or doing something to preserve its > operational state. > > What is the best way for me to isolate this issue? I'd like to understand > exactly what drives NiFi to be non-responsive. If there is anything that I > can do to isolate this, and to help the NiFi team make this more robust, I'm > glad to dig. > > Its been impossible for me to exactly characterize the conditions that lead > to a non-responsive NiFi UI. However I see this fairly frequently. > > I've updated the following picture. Since it did not seem to attach before. > I've also added a view of the memory and CPU consumption. In this particular > case I waited for about 30 seconds and eventually the NiFi user interface > came to life. > !image-2019-08-28-08-15-51-702.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFI-6488) NiFi web interface often non-responsive
[ https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919480#comment-16919480 ] David Sargrad commented on NIFI-6488: - !image-2019-08-30-08-03-39-877.png! > NiFi web interface often non-responsive > > > Key: NIFI-6488 > URL: https://issues.apache.org/jira/browse/NIFI-6488 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 > Environment: centos 7 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-08-28-08-15-51-702.png, > image-2019-08-30-08-03-39-877.png > > > I have been using NiFi for close to a year. Currently most of my experience > has been with building custom processors and prototyping a variety of flows. > > Often the NiFi web interface becomes non-responsive. Its typically during a > flow integration phase, where I leave flowfiles sitting in queues, sometimes > 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small > flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the > filled queues is in the tens of megabytes. > > I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum > allocated heap size. I'd think that NiFi protects against non-responsive UI's > by shedding load, presenting a warning, or doing something to preserve its > operational state. > > What is the best way for me to isolate this issue? I'd like to understand > exactly what drives NiFi to be non-responsive. If there is anything that I > can do to isolate this, and to help the NiFi team make this more robust, I'm > glad to dig. > > Its been impossible for me to exactly characterize the conditions that lead > to a non-responsive NiFi UI. However I see this fairly frequently. > > I've updated the following picture. Since it did not seem to attach before. > I've also added a view of the memory and CPU consumption. In this particular > case I waited for about 30 seconds and eventually the NiFi user interface > came to life. > !image-2019-08-28-08-15-51-702.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFI-6488) NiFi web interface often non-responsive
[ https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917817#comment-16917817 ] David Sargrad commented on NIFI-6488: - The flows I am using are relatively small... perhaps a dozen processors or so. I am doing a lot of JMS, Kafka, and Mongo stuff... > NiFi web interface often non-responsive > > > Key: NIFI-6488 > URL: https://issues.apache.org/jira/browse/NIFI-6488 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 > Environment: centos 7 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-08-28-08-15-51-702.png > > > I have been using NiFi for close to a year. Currently most of my experience > has been with building custom processors and prototyping a variety of flows. > > Often the NiFi web interface becomes non-responsive. Its typically during a > flow integration phase, where I leave flowfiles sitting in queues, sometimes > 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small > flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the > filled queues is in the tens of megabytes. > > I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum > allocated heap size. I'd think that NiFi protects against non-responsive UI's > by shedding load, presenting a warning, or doing something to preserve its > operational state. > > What is the best way for me to isolate this issue? I'd like to understand > exactly what drives NiFi to be non-responsive. If there is anything that I > can do to isolate this, and to help the NiFi team make this more robust, I'm > glad to dig. > > Its been impossible for me to exactly characterize the conditions that lead > to a non-responsive NiFi UI. However I see this fairly frequently. > > I've updated the following picture. Since it did not seem to attach before. > I've also added a view of the memory and CPU consumption. In this particular > case I waited for about 30 seconds and eventually the NiFi user interface > came to life. > !image-2019-08-28-08-15-51-702.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFI-6488) NiFi web interface often non-responsive
[ https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917814#comment-16917814 ] David Sargrad commented on NIFI-6488: - I am using chrome. The UI seems to become unresponsive over time. Typically it has no problem handling the initial page load. However when it becomes unresponsive, it seems to be that initial load.. Once it loads (when it loads) it seems ok. I sometimes just restart NiFi, since I wait for the page to load and it doesnt. I have no problems of this nature for my "production NiFi" instances. I've only experienced this, as I mentioned, in what I would call "developer instances".. However even in these instances it strikes me that there is an issue that is worth looking at. > NiFi web interface often non-responsive > > > Key: NIFI-6488 > URL: https://issues.apache.org/jira/browse/NIFI-6488 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 > Environment: centos 7 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-08-28-08-15-51-702.png > > > I have been using NiFi for close to a year. Currently most of my experience > has been with building custom processors and prototyping a variety of flows. > > Often the NiFi web interface becomes non-responsive. Its typically during a > flow integration phase, where I leave flowfiles sitting in queues, sometimes > 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small > flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the > filled queues is in the tens of megabytes. > > I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum > allocated heap size. I'd think that NiFi protects against non-responsive UI's > by shedding load, presenting a warning, or doing something to preserve its > operational state. > > What is the best way for me to isolate this issue? I'd like to understand > exactly what drives NiFi to be non-responsive. If there is anything that I > can do to isolate this, and to help the NiFi team make this more robust, I'm > glad to dig. > > Its been impossible for me to exactly characterize the conditions that lead > to a non-responsive NiFi UI. However I see this fairly frequently. > > I've updated the following picture. Since it did not seem to attach before. > I've also added a view of the memory and CPU consumption. In this particular > case I waited for about 30 seconds and eventually the NiFi user interface > came to life. > !image-2019-08-28-08-15-51-702.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFI-6488) NiFi web interface often non-responsive
[ https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917726#comment-16917726 ] David Sargrad commented on NIFI-6488: - [~joewitt] I do understand the need to ensure that the data flow is treated as the number one concern. However I do believe that there are HMI architectures that can ensure that this is the case. The current issue that I see seems to be that the HMI is so tightly coupled to the core data processing application. I do know there is work afoot to refactor the HMI. I wonder if this includes an eye towards a design element that further decouples the HMI, from the core. > NiFi web interface often non-responsive > > > Key: NIFI-6488 > URL: https://issues.apache.org/jira/browse/NIFI-6488 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 > Environment: centos 7 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-08-28-08-15-51-702.png > > > I have been using NiFi for close to a year. Currently most of my experience > has been with building custom processors and prototyping a variety of flows. > > Often the NiFi web interface becomes non-responsive. Its typically during a > flow integration phase, where I leave flowfiles sitting in queues, sometimes > 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small > flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the > filled queues is in the tens of megabytes. > > I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum > allocated heap size. I'd think that NiFi protects against non-responsive UI's > by shedding load, presenting a warning, or doing something to preserve its > operational state. > > What is the best way for me to isolate this issue? I'd like to understand > exactly what drives NiFi to be non-responsive. If there is anything that I > can do to isolate this, and to help the NiFi team make this more robust, I'm > glad to dig. > > Its been impossible for me to exactly characterize the conditions that lead > to a non-responsive NiFi UI. However I see this fairly frequently. > > I've updated the following picture. Since it did not seem to attach before. > I've also added a view of the memory and CPU consumption. In this particular > case I waited for about 30 seconds and eventually the NiFi user interface > came to life. > !image-2019-08-28-08-15-51-702.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6488) NiFi web interface often non-responsive
[ https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6488: Attachment: image-2019-08-28-08-15-51-702.png Description: I have been using NiFi for close to a year. Currently most of my experience has been with building custom processors and prototyping a variety of flows. Often the NiFi web interface becomes non-responsive. Its typically during a flow integration phase, where I leave flowfiles sitting in queues, sometimes 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the filled queues is in the tens of megabytes. I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum allocated heap size. I'd think that NiFi protects against non-responsive UI's by shedding load, presenting a warning, or doing something to preserve its operational state. What is the best way for me to isolate this issue? I'd like to understand exactly what drives NiFi to be non-responsive. If there is anything that I can do to isolate this, and to help the NiFi team make this more robust, I'm glad to dig. Its been impossible for me to exactly characterize the conditions that lead to a non-responsive NiFi UI. However I see this fairly frequently. I've updated the following picture. Since it did not seem to attach before. I've also added a view of the memory and CPU consumption. In this particular case I waited for about 30 seconds and eventually the NiFi user interface came to life. !image-2019-08-28-08-15-51-702.png! was: I have been using NiFi for close to a year. Currently most of my experience has been with building custom processors and prototyping a variety of flows. Often the NiFi web interface becomes non-responsive. Its typically during a flow integration phase, where I leave flowfiles sitting in queues, sometimes 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the filled queues is in the tens of megabytes. I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum allocated heap size. I'd think that NiFi protects against non-responsive UI's by shedding load, presenting a warning, or doing something to preserve its operational state. What is the best way for me to isolate this issue? I'd like to understand exactly what drives NiFi to be non-responsive. If there is anything that I can do to isolate this, and to help the NiFi team make this more robust, I'm glad to dig. Its been impossible for me to exactly characterize the conditions that lead to a non-responsive NiFi UI. However I see this fairly frequently. !image-2019-07-25-08-23-46-031.png! > NiFi web interface often non-responsive > > > Key: NIFI-6488 > URL: https://issues.apache.org/jira/browse/NIFI-6488 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.9.2 > Environment: centos 7 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-08-28-08-15-51-702.png > > > I have been using NiFi for close to a year. Currently most of my experience > has been with building custom processors and prototyping a variety of flows. > > Often the NiFi web interface becomes non-responsive. Its typically during a > flow integration phase, where I leave flowfiles sitting in queues, sometimes > 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small > flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the > filled queues is in the tens of megabytes. > > I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum > allocated heap size. I'd think that NiFi protects against non-responsive UI's > by shedding load, presenting a warning, or doing something to preserve its > operational state. > > What is the best way for me to isolate this issue? I'd like to understand > exactly what drives NiFi to be non-responsive. If there is anything that I > can do to isolate this, and to help the NiFi team make this more robust, I'm > glad to dig. > > Its been impossible for me to exactly characterize the conditions that lead > to a non-responsive NiFi UI. However I see this fairly frequently. > > I've updated the following picture. Since it did not seem to attach before. > I've also added a view of the memory and CPU consumption. In this particular > case I waited for about 30 seconds and eventually the NiFi user interface > came to life. > !image-2019-08-28-08-15-51-702.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6590) NiFi Command & Control Framework
[ https://issues.apache.org/jira/browse/NIFI-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6590: Description: I've been using NiFi for about a year now. I've built a number of data ingest/egress flows with it. We've also built about 5 custom processors (in JAVA). I've not really used it as a command & control framework. I am considering using NiFi for a couple of mechanisms and I'd like the experts view as to whether or not this is an appropriate use of the NiFi application framework. Would you use NiFi for the following types of functions: * RESTful service - Expose and API, and respond to CRUD RESTful operations * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, etc), and replay data in a temporal fashion A data replay service, might, for example, be built as a custom NiFi processor that creates a thread, and creates one or more flowfiles periodically based on the configuration of that processor. The key is this service implements a timeline such that flowfiles are generated through time, based on the timing characteristics of the data in the database. It might run for days at a time. Currently we might build such a service as a background daemon, perhaps implemented using Node JS (or of course, more traditional languages like java, c/c++). A RESTful service might, for example, be built as a custom NiFi processor that exposes an API (e.g. an OPEN API compliant API), and responds to commands against that API. Currently we build and expose such service APIs using Node Express. Thoughts from the experts are appreciated. was: I've been using NiFi for about a year now. I've built a number of data ingest/egress flows with it. We've also built about 5 custom processors (in JAVA). I've not really used it as a command & control framework. I am considering using NiFi for a couple of mechanisms and I'd like the experts view as to whether or not this is an appropriate use of the NiFi application framework. Would you use NiFi for the following types of functions: * RESTful service - Expose and API, and respond to CRUD RESTful operations * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, etc), and replay data in a temporal fashion A data replay service, might, for example, be built as a custom NiFi processor that creates a thread, and creates one or more flowfiles periodically based on the configuration of that processor. Currently we might build such a service as a background daemon, perhaps implemented using Node JS (or of course, more traditional languages like java, c/c++). A RESTful service might, for example, be built as a custom NiFi processor that exposes an API (e.g. an OPEN API compliant API), and responds to commands against that API. Currently we build and expose such service APIs using Node Express. Thoughts from the experts are appreciated. > NiFi Command & Control Framework > > > Key: NIFI-6590 > URL: https://issues.apache.org/jira/browse/NIFI-6590 > Project: Apache NiFi > Issue Type: Wish > Environment: Centos 7 >Reporter: David Sargrad >Priority: Trivial > > I've been using NiFi for about a year now. I've built a number of data > ingest/egress flows with it. We've also built about 5 custom processors (in > JAVA). I've not really used it as a command & control framework. > > I am considering using NiFi for a couple of mechanisms and I'd like the > experts view as to whether or not this is an appropriate use of the NiFi > application framework. > > Would you use NiFi for the following types of functions: > > * RESTful service - Expose and API, and respond to CRUD RESTful operations > * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, > etc), and replay data in a temporal fashion > > A data replay service, might, for example, be built as a custom NiFi > processor that creates a thread, and creates one or more flowfiles > periodically based on the configuration of that processor. The key is this > service implements a timeline such that flowfiles are generated through time, > based on the timing characteristics of the data in the database. It might run > for days at a time. Currently we might build such a service as a background > daemon, perhaps implemented using Node JS (or of course, more traditional > languages like java, c/c++). > > A RESTful service might, for example, be built as a custom NiFi processor > that exposes an API (e.g. an OPEN API compliant API), and responds to > commands against that API. Currently we build and expose such service APIs > using Node Express. > > Thoughts from the experts are appreciated. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6590) NiFi Command & Control Framework
[ https://issues.apache.org/jira/browse/NIFI-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6590: Description: I've been using NiFi for about a year now. I've built a number of data ingest/egress flows with it. We've also built about 5 custom processors (in JAVA). I've not really used it as a command & control framework. I am considering using NiFi for a couple of mechanisms and I'd like the experts view as to whether or not this is an appropriate use of the NiFi application framework. Would you use NiFi for the following types of functions: * RESTful service - Expose and API, and respond to CRUD RESTful operations * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, etc), and replay data in a temporal fashion A data replay service, might, for example, be built as a custom NiFi processor that creates a thread, and creates one or more flowfiles periodically based on the configuration of that processor. Currently we might build such a service as a background daemon, perhaps implemented using Node JS (or of course, more traditional languages like java, c/c++). A RESTful service might, for example, be built as a custom NiFi processor that exposes an API (e.g. an OPEN API compliant API), and responds to commands against that API. Currently we build and expose such service APIs using Node Express. Thoughts from the experts are appreciated. was: I've been using NiFi for about a year now. I've built a number of data ingest/egress flows with it. We've also built about 5 custom processors (in JAVA). I am considering using NiFi for a couple of mechanisms and I'd like the experts view as to whether or not this is an appropriate use of the NiFi application framework. Would you use NiFi for the following types of functions: * RESTful service - Expose and API, and respond to CRUD RESTful operations * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, etc), and replay data in a temporal fashion A data replay service, might, for example, be built as a custom NiFi processor that creates a thread, and creates one or more flowfiles periodically based on the configuration of that processor. Currently we might build such a service as a background daemon, perhaps implemented using Node JS (or of course, more traditional languages like java, c/c++). A RESTful service might, for example, be built as a custom NiFi processor that exposes an API (e.g. an OPEN API compliant API), and responds to commands against that API. Currently we build and expose such service APIs using Node Express. Thoughts from the experts are appreciated. > NiFi Command & Control Framework > > > Key: NIFI-6590 > URL: https://issues.apache.org/jira/browse/NIFI-6590 > Project: Apache NiFi > Issue Type: Wish > Environment: Centos 7 >Reporter: David Sargrad >Priority: Trivial > > I've been using NiFi for about a year now. I've built a number of data > ingest/egress flows with it. We've also built about 5 custom processors (in > JAVA). I've not really used it as a command & control framework. > > I am considering using NiFi for a couple of mechanisms and I'd like the > experts view as to whether or not this is an appropriate use of the NiFi > application framework. > > Would you use NiFi for the following types of functions: > > * RESTful service - Expose and API, and respond to CRUD RESTful operations > * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, > etc), and replay data in a temporal fashion > > A data replay service, might, for example, be built as a custom NiFi > processor that creates a thread, and creates one or more flowfiles > periodically based on the configuration of that processor. Currently we might > build such a service as a background daemon, perhaps implemented using Node > JS (or of course, more traditional languages like java, c/c++). > > A RESTful service might, for example, be built as a custom NiFi processor > that exposes an API (e.g. an OPEN API compliant API), and responds to > commands against that API. Currently we build and expose such service APIs > using Node Express. > > Thoughts from the experts are appreciated. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6590) NiFi Command & Control Framework
[ https://issues.apache.org/jira/browse/NIFI-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6590: Summary: NiFi Command & Control Framework (was: NiFi Control Framework) > NiFi Command & Control Framework > > > Key: NIFI-6590 > URL: https://issues.apache.org/jira/browse/NIFI-6590 > Project: Apache NiFi > Issue Type: Wish > Environment: Centos 7 >Reporter: David Sargrad >Priority: Trivial > > I've been using NiFi for about a year now. I've built a number of data > ingest/egress flows with it. We've also built about 5 custom processors (in > JAVA). > > I am considering using NiFi for a couple of mechanisms and I'd like the > experts view as to whether or not this is an appropriate use of the NiFi > application framework. > > Would you use NiFi for the following types of functions: > > * RESTful service - Expose and API, and respond to CRUD RESTful operations > * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, > etc), and replay data in a temporal fashion > > A data replay service, might, for example, be built as a custom NiFi > processor that creates a thread, and creates one or more flowfiles > periodically based on the configuration of that processor. Currently we might > build such a service as a background daemon, perhaps implemented using Node > JS (or of course, more traditional languages like java, c/c++). > > A RESTful service might, for example, be built as a custom NiFi processor > that exposes an API (e.g. an OPEN API compliant API), and responds to > commands against that API. Currently we build and expose such service APIs > using Node Express. > > Thoughts from the experts are appreciated. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6590) NiFi Control Framework
David Sargrad created NIFI-6590: --- Summary: NiFi Control Framework Key: NIFI-6590 URL: https://issues.apache.org/jira/browse/NIFI-6590 Project: Apache NiFi Issue Type: Wish Environment: Centos 7 Reporter: David Sargrad I've been using NiFi for about a year now. I've built a number of data ingest/egress flows with it. We've also built about 5 custom processors (in JAVA). I am considering using NiFi for a couple of mechanisms and I'd like the experts view as to whether or not this is an appropriate use of the NiFi application framework. Would you use NiFi for the following types of functions: * RESTful service - Expose and API, and respond to CRUD RESTful operations * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, etc), and replay data in a temporal fashion A data replay service, might, for example, be built as a custom NiFi processor that creates a thread, and creates one or more flowfiles periodically based on the configuration of that processor. Currently we might build such a service as a background daemon, perhaps implemented using Node JS (or of course, more traditional languages like java, c/c++). A RESTful service might, for example, be built as a custom NiFi processor that exposes an API (e.g. an OPEN API compliant API), and responds to commands against that API. Currently we build and expose such service APIs using Node Express. Thoughts from the experts are appreciated. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6488) NiFi web interface often non-responsive
David Sargrad created NIFI-6488: --- Summary: NiFi web interface often non-responsive Key: NIFI-6488 URL: https://issues.apache.org/jira/browse/NIFI-6488 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.9.2 Environment: centos 7 Reporter: David Sargrad I have been using NiFi for close to a year. Currently most of my experience has been with building custom processors and prototyping a variety of flows. Often the NiFi web interface becomes non-responsive. Its typically during a flow integration phase, where I leave flowfiles sitting in queues, sometimes 3 or 4 queues may be maxed at 10,000 flow files. These are relatively small flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the filled queues is in the tens of megabytes. I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum allocated heap size. I'd think that NiFi protects against non-responsive UI's by shedding load, presenting a warning, or doing something to preserve its operational state. What is the best way for me to isolate this issue? I'd like to understand exactly what drives NiFi to be non-responsive. If there is anything that I can do to isolate this, and to help the NiFi team make this more robust, I'm glad to dig. Its been impossible for me to exactly characterize the conditions that lead to a non-responsive NiFi UI. However I see this fairly frequently. !image-2019-07-25-08-23-46-031.png! -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888239#comment-16888239
]
David Sargrad commented on NIFI-6439:
-
[~alopresto] [~patricker]
I've succesfully cloned, compiled, and run the latest master.
Thanks for the fix!
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
>Affects Versions: 1.10.0
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Assignee: Peter Wicks
>Priority: Critical
> Labels: build
> Fix For: 1.10.0
>
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Time Spent: 0.5h
> Remaining Estimate: 95.5h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888229#comment-16888229
]
David Sargrad commented on NIFI-6439:
-
[~alopresto]
Awesome. Ty Sir.
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
>Affects Versions: 1.10.0
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Assignee: Peter Wicks
>Priority: Blocker
> Labels: build
> Fix For: 1.10.0
>
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Time Spent: 0.5h
> Remaining Estimate: 95.5h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888209#comment-16888209
]
David Sargrad commented on NIFI-6439:
-
[~patricker] [~alopresto] when will this fix be in the NiFi master?
Thanks.
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
>Affects Versions: 1.10.0
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Assignee: Peter Wicks
>Priority: Blocker
> Labels: build
> Fix For: 1.10.0
>
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Time Spent: 10m
> Remaining Estimate: 95h 50m
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888129#comment-16888129
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 4:36 PM:
--
All i can say is you guys are on top of things.. Really a pleasure to work with
a development team that cares.
I could make a local mod.. but i'm guessing you guys will have this in the
master soon.. I'll wait for an ETA on that github update to the master.
was (Author: dsargrad):
All i can say is you guys are on top of things.. Really a pleasure to work with
a development team that cares. I could make a local mod.. but i'm guessing you
guys will have this in the master soon.. I'll wait for an ETA on that github
update to the master.
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Blocker
> Labels: build
> Fix For: 1.10.0
>
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888129#comment-16888129
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 4:35 PM:
--
All i can say is you guys are on top of things.. Really a pleasure to work with
a development team that cares. I could make a local mod.. but i'm guessing you
guys will have this in the master soon.. I'll wait for an ETA on that github
update to the master.
was (Author: dsargrad):
All i can say is you guys are on top of things.. Really a pleasure to work with
a development team that cares.
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Blocker
> Labels: build
> Fix For: 1.10.0
>
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888129#comment-16888129
]
David Sargrad commented on NIFI-6439:
-
All i can say is you guys are on top of things.. Really a pleasure to work with
a development team that cares.
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888110#comment-16888110
]
David Sargrad commented on NIFI-6439:
-
Ty [~alopresto]. I now understand your point. I do agree with [~patricker]. I
think that would solve things.
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888101#comment-16888101
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 4:06 PM:
--
[~alopresto] in our debug environment we are using HTTP.. ty for your
attention. This is absolutely NOT a network connectivity issue from my
perspective.. Its quite repeatable, and the pertinent networks seem to be quite
healthy. In fact we first encountered this a couple weeks ago.. we've
reattempted the process several times since then.. to no avail.
We've built nifi in the past.. without this problem. We did that for 1.9
was (Author: dsargrad):
[~alopresto] in our debug environment we are using HTTP.. ty for your
attention. This is absolutely NOT a network connectivity issue from my
perspective.. Its quite repeatable, and the pertinent networks seem to be quite
healthy. In fact we first encountered this a couple weeks ago.. we've
reattempted the process again and again.. to no avail.
We've built nifi in the past.. without this problem. We did that for 1.9
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888101#comment-16888101
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 4:05 PM:
--
[~alopresto] in our debug environment we are using HTTP.. ty for your
attention. This is absolutely NOT a network connectivity issue from my
perspective.. Its quite repeatable, and the pertinent networks seem to be quite
healthy. In fact we first encountered this a couple weeks ago.. we've
reattempted the process again and again.. to no avail.
We've built nifi in the past.. without this problem. We did that for 1.9
was (Author: dsargrad):
[~alopresto] in our debug environment we are using HTTP.. ty for your
attention. This is absolutely NOT a network connectivity issue from my
perspective.. Its quite repeatable, and the pertinent networks seem to be quite
healthy
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888101#comment-16888101
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 4:04 PM:
--
[~alopresto] in our debug environment we are using HTTP.. ty for your
attention. This is absolutely NOT a network connectivity issue from my
perspective.. Its quite repeatable, and the pertinent networks seem to be quite
healthy
was (Author: dsargrad):
[~alopresto] in our debug environment we are using HTTP.. ty for your attention
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888101#comment-16888101
]
David Sargrad commented on NIFI-6439:
-
[~alopresto] in our debug environment we are using HTTP.. ty for your attention
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888089#comment-16888089
]
David Sargrad commented on NIFI-6439:
-
Thanks [~joewitt]. This issue has been a blocker for some of our development.
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887997#comment-16887997
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 3:04 PM:
--
[https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/nifi-context.xml]
seems to have changed recently May 29 in github
[~alopresto]
This change was part of: https://issues.apache.org/jira/browse/NIFI-6323
was (Author: dsargrad):
[https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/nifi-context.xml]
seems to have changed recently May 29 in github
This change was part of: https://issues.apache.org/jira/browse/NIFI-6323
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888021#comment-16888021 ] David Sargrad commented on NIFI-6415: - Thanks [~andrewmlim] > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Assignee: Andrew Lim >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887997#comment-16887997
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 1:50 PM:
--
[https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/nifi-context.xml]
seems to have changed recently May 29 in github
This change was part of: https://issues.apache.org/jira/browse/NIFI-6323
was (Author: dsargrad):
[https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/nifi-context.xml]
seems to have changed recently May 29 in github
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887997#comment-16887997
]
David Sargrad commented on NIFI-6439:
-
[https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/nifi-context.xml]
seems to have changed recently May 29 in github
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887994#comment-16887994
]
David Sargrad commented on NIFI-6439:
-
Also interesting is that this points to nifi-context.xml.. which for nifi 1.10
is as follows:
{code:java}
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframework.org/schema/beans
https://www.springframework.org/schema/beans/spring-beans-3.1.xsd";>
{code}
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887989#comment-16887989
]
David Sargrad commented on NIFI-6439:
-
Interesting link(s) on STACK
[https://stackoverflow.com/questions/13814321/cannot-find-the-declaration-of-element-beans]
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887989#comment-16887989
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 1:43 PM:
--
Potentially interesting link(s) on STACK
[https://stackoverflow.com/questions/13814321/cannot-find-the-declaration-of-element-beans]
[https://stackoverflow.com/questions/27420395/cvc-elt-1-cannot-find-the-declaration-of-element-beans/27420570]
was (Author: dsargrad):
Interesting link(s) on STACK
[https://stackoverflow.com/questions/13814321/cannot-find-the-declaration-of-element-beans]
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887968#comment-16887968
]
David Sargrad edited comment on NIFI-6439 at 7/18/19 1:40 PM:
--
!image-2019-07-18-09-16-16-488.png!
I've compiled and run nifi in the past with this java. This was the 1.9 nifi
system. This problem seems to have arisen in 1.10. From my perspective this is
NOT an issue with network stability.
was (Author: dsargrad):
!image-2019-07-18-09-16-16-488.png!
I've compiled and run nifi in the past with this java. This was the 1.9 nifi
system. This problem seems to have arisen in 1.10
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: Linux,
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887968#comment-16887968
]
David Sargrad commented on NIFI-6439:
-
!image-2019-07-18-09-16-16-488.png!
I've compiled and run nifi in the past with this java. This was the 1.9 nifi
system. This problem seems to have arisen in 1.10
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: Linux,
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-6439) web.context.ContextLoader Context initialization failed
[
https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Sargrad updated NIFI-6439:
Attachment: image-2019-07-18-09-16-16-488.png
> web.context.ContextLoader Context initialization failed
> ---
>
> Key: NIFI-6439
> URL: https://issues.apache.org/jira/browse/NIFI-6439
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Tools and Build
> Environment: Linux,
>Reporter: Zinan Ma
>Priority: Major
> Labels: build
> Attachments: image-2019-07-15-08-21-51-633.png,
> image-2019-07-16-09-09-36-005.png, image-2019-07-18-09-16-16-488.png
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi NIFI team,
> I have been trying to run NIFI in a local debugging environment by following
> this [tutorial|[https://nifi.apache.org/quickstart.html]]
> When I do mvn -T C2.0 clean install, The test cases failed.(some spring
> context test case) I then did a mvn clean and
> mvn install -DskipTests
> I successfully build it but then when I run ./nifi.sh start, Nifi could not
> start so I check the nifi-app.log and here is the first error:
> {color:#d04437} 2019-07-12 09:37:53,881 INFO [main]
> o.e.j.s.handler.ContextHandler._nifi_api Initializing Spring root
> WebApplicationContext{color}
> {color:#d04437}2019-07-12 09:40:01,659 ERROR [main]
> o.s.web.context.ContextLoader Context initialization failed{color}
> {color:#d04437}org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
> Line 19 in XML document from class path resource [nifi-context.xml] is
> invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19;
> columnNumber: 139; cvc-elt.1: Cannot find the declaration of element
> 'beans'.{color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336){color}
> {color:#d04437} at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217){color}
> {color:#d04437} at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188){color}
> !image-2019-07-12-16-49-56-584.png!
>
> Now I am really stuck at this stage. Any help would be greatly appreciated!
> Please let me know if you need additional information!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6439) web.context.ContextLoader Context initialization failed
[ https://issues.apache.org/jira/browse/NIFI-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887967#comment-16887967 ] David Sargrad commented on NIFI-6439: - I am also having this problem. The full stack trace is provided below: 2019-07-18 08:37:08,606 ERROR [main] o.s.web.context.ContextLoader Context initialization failed org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 19 in XML document from class path resource [nifi-context.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 19; columnNumber: 139; cvc-elt.1: Cannot find the declaration of element 'beans'. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:399) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188) at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsFromImportedResources(ConfigurationClassBeanDefinitionReader.java:354) at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:143) at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116) at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320) at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:228) at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:272) at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:92) at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:687) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:525) at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:443) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:325) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:959) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:553) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:924) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:365) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:854) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:278) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:167) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:119) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:167) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.handler.gzip.GzipHandler.doStart(GzipHandler.java:406) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:167) at org.eclip
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884375#comment-16884375 ] David Sargrad edited comment on NIFI-6415 at 7/13/19 1:46 PM: -- As an aside, in yet another issue (https://issues.apache.org/jira/browse/NIFI-6327?filter=-2), I've documented (both within the body of the issue, and within the comments that I provided) some of the problems that I had in getting to a point where I could single-step debug. If you are going to drive updates to documentation, id recommend that you also incorporate some of those instructions... Specifically the instructions that relate to attaching to a running instance, in order to set breakpoints. These instructions could include some targeted breakpoints in the lifecycle of the NiFi system. This would go a along way to helping a NiFi developer understand where the application is in its lifecycle. [~mcgilman], [~bende] was (Author: dsargrad): As an aside, in yet another issue (https://issues.apache.org/jira/browse/NIFI-6327?filter=-2), I've documented (both within the body of the issue, and within the comments that I provided) some of the problems that I had in getting to a point where I could single-step debug. If you are going to drive updates to documentation, id recommend that you also incorporate some of those instructions. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884375#comment-16884375 ] David Sargrad commented on NIFI-6415: - As an aside, in yet another issue (https://issues.apache.org/jira/browse/NIFI-6327?filter=-2), I've documented (both within the body of the issue, and within the comments that I provided) some of the problems that I had in getting to a point where I could single-step debug. If you are going to drive updates to documentation, id recommend that you also incorporate some of those instructions. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884371#comment-16884371 ] David Sargrad edited comment on NIFI-6415 at 7/13/19 1:24 PM: -- Thanks so much [~mcgilman]. Your support is greatly appreciated. I will try -DskipTests I have written a separate issue (https://issues.apache.org/jira/browse/NIFI-6343?filter=-2) on the variety of problems I am having with getting past NiFi unit tests. I actually suggested in a comment within that issue that the Quick Start([https://nifi.apache.org/quickstart.html]) page be updated with instructions for how to properly skip tests. I love the NiFi system, and would like to see its use increase. I do think solving some of these ancillary problems would go a long way to hardening the system. Architects like me (who have been developing software systems for a long time), typically insist on a certain level of support in order to begin to advocate use of open source and closed source software in a complex mission critical system. Now that I see that you guys are indeed an active development team, I will do my best to continue to support by finding and reporting problems that I think are real, and that may stand in the way of adoption. By the way, the reason that I am building NiFi, is because I think the ability to singlestep debug is critical to the development of custom NiFi processors. We are doing exactly that as we begin to adopt NiFi. was (Author: dsargrad): Thanks so much [~mcgilman]. Your support is greatly appreciated. I will try -DskipTests I have written a separate issue on the variety of problems I am having with getting past NiFi unit tests. I actually suggested in a comment within that issue that the Quick Start([https://nifi.apache.org/quickstart.html]) page be updated with instructions for how to properly skip tests. I love the NiFi system, and would like to see its use increase. I do think solving some of these ancillary problems would go a long way to hardening the system. Architects like me (who have been developing software systems for a long time), typically insist on a certain level of support in order to begin to advocate use of open source and closed source software in a complex mission critical system. Now that I see that you guys are indeed an active development team, I will do my best to continue to support by finding and reporting problems that I think are real, and that may stand in the way of adoption. By the way, the reason that I am building NiFi, is because I think the ability to singlestep debug is critical to the development of custom NiFi processors. We are doing exactly that as we begin to adopt NiFi. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884371#comment-16884371 ] David Sargrad edited comment on NIFI-6415 at 7/13/19 1:23 PM: -- Thanks so much [~mcgilman]. Your support is greatly appreciated. I will try -DskipTests I have written a separate issue on the variety of problems I am having with getting past NiFi unit tests. I actually suggested in a comment within that issue that the Quick Start([https://nifi.apache.org/quickstart.html]) page be updated with instructions for how to properly skip tests. I love the NiFi system, and would like to see its use increase. I do think solving some of these ancillary problems would go a long way to hardening the system. Architects like me (who have been developing software systems for a long time), typically insist on a certain level of support in order to begin to advocate use of open source and closed source software in a complex mission critical system. Now that I see that you guys are indeed an active development team, I will do my best to continue to support by finding and reporting problems that I think are real, and that may stand in the way of adoption. By the way, the reason that I am building NiFi, is because I think the ability to singlestep debug is critical to the development of custom NiFi processors. We are doing exactly that as we begin to adopt NiFi. was (Author: dsargrad): Thanks so much [~mcgilman]. Your support is greatly appreciated. I will try -DskipTests I have written a separate issue on the variety of problems I am having with getting past NiFi unit tests. I actually suggested in a comment within that issue that the [Quick Start|[https://nifi.apache.org/quickstart.html]] page be updated with instructions for how to properly skip tests. I love the NiFi system, and would like to see its use increase. I do think solving some of these ancillary problems would go a long way to hardening the system. Architects like me (who have been developing software systems for a long time), typically insist on a certain level of support in order to begin to advocate use of open source and closed source software in a complex mission critical system. Now that I see that you guys are indeed an active development team, I will do my best to continue to support by finding and reporting problems that I think are real, and that may stand in the way of adoption. By the way, the reason that I am building NiFi, is because I think the ability to singlestep debug is critical to the development of custom NiFi processors. We are doing exactly that as we begin to adopt NiFi. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884371#comment-16884371 ] David Sargrad edited comment on NIFI-6415 at 7/13/19 1:23 PM: -- Thanks so much [~mcgilman]. Your support is greatly appreciated. I will try -DskipTests I have written a separate issue on the variety of problems I am having with getting past NiFi unit tests. I actually suggested in a comment within that issue that the [Quick Start|[https://nifi.apache.org/quickstart.html]] page be updated with instructions for how to properly skip tests. I love the NiFi system, and would like to see its use increase. I do think solving some of these ancillary problems would go a long way to hardening the system. Architects like me (who have been developing software systems for a long time), typically insist on a certain level of support in order to begin to advocate use of open source and closed source software in a complex mission critical system. Now that I see that you guys are indeed an active development team, I will do my best to continue to support by finding and reporting problems that I think are real, and that may stand in the way of adoption. By the way, the reason that I am building NiFi, is because I think the ability to singlestep debug is critical to the development of custom NiFi processors. We are doing exactly that as we begin to adopt NiFi. was (Author: dsargrad): Thanks so much [~mcgilman]. Your support is greatly appreciated. I will try -DskipTests I have written a separate issue on the variety of problems I am having with getting past NiFi unit tests. I actually suggested in a comment within that issue that the [Quick Start|[https://nifi.apache.org/quickstart.html]] page be updated with instructions for how to properly skip tests. I love the NiFi system, and would like to see its use increase. I do think solving some of these ancillary problems would go a long way to hardening the system. Architects like me (who have been developing software systems for a long time), typically insist on a certain level of support in order to begin to advocate use of open source and closed source software in a complex mission critical system. Now that I see that you guys are indeed an active development team, I will do my best to continue to support by finding and reporting problems that I think are real, and that may stand in the way of adoption. By the way, the reason that I am building NiFi, is because I think the ability to singlestep debug is critical to the development of custom NiFi processors. We are doing exactly that as we begin to adopt NiFi. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884371#comment-16884371 ] David Sargrad commented on NIFI-6415: - Thanks so much [~mcgilman]. Your support is greatly appreciated. I will try -DskipTests I have written a separate issue on the variety of problems I am having with getting past NiFi unit tests. I actually suggested in a comment within that issue that the [Quick Start|[https://nifi.apache.org/quickstart.html]] page be updated with instructions for how to properly skip tests. I love the NiFi system, and would like to see its use increase. I do think solving some of these ancillary problems would go a long way to hardening the system. Architects like me (who have been developing software systems for a long time), typically insist on a certain level of support in order to begin to advocate use of open source and closed source software in a complex mission critical system. Now that I see that you guys are indeed an active development team, I will do my best to continue to support by finding and reporting problems that I think are real, and that may stand in the way of adoption. By the way, the reason that I am building NiFi, is because I think the ability to singlestep debug is critical to the development of custom NiFi processors. We are doing exactly that as we begin to adopt NiFi. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883979#comment-16883979 ] David Sargrad edited comment on NIFI-6415 at 7/12/19 4:58 PM: -- Hi [~mcgilman] I still see this failure on nifi-web-api !image-2019-07-12-12-48-47-442.png! I see the following in my local .m2 repository: !image-2019-07-12-12-47-58-020.png! I've tried to clean my entire ~/.m2/repository/org/apache/nifi folder (to rebuild everything) It would seem that the build is trying to find a "tests" folder. Keep in mind that I am trying to disable all unit tests. The reason I am doing this is because inevitably when I try to build nifi unit tests will often fail (and not always consistently).. I'm trying to disable unit tests since right now they just get in the way of my building of nifi. I've also noticed that one of the files is named: nifi-web-security-1.10.0-SNAPSHOT-tests.jar.lastUpdated This is not a proper jar file.. I'm not sure why it has a lastUpdated extension [https://stackoverflow.com/questions/2529218/maven-downloads-have-lastupdated-as-extension/13149707] was (Author: dsargrad): Hi [~mcgilman] I still see this failure on nifi-web-api !image-2019-07-12-12-48-47-442.png! I see the following in my local .m2 repository: !image-2019-07-12-12-47-58-020.png! I've tried to clean my entire ~/.m2/repository/org/apache/nifi folder (to rebuild everything) It would seem that the build is trying to find a "tests" folder. Keep in mind that I am trying to disable all unit tests. The reason I am doing this is because inevitably when I try to build nifi unit tests will often fail (and not always consistently).. I'm trying to disable unit tests since right now they just get in the way of my building of nifi. I've also noticed that one of the files is named: nifi-web-security-1.10.0-SNAPSHOT-tests.jar.lastUpdated This is not a proper jar file.. I'm not sure why it has a lastUpdated extension > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883979#comment-16883979 ] David Sargrad edited comment on NIFI-6415 at 7/12/19 4:56 PM: -- Hi [~mcgilman] I still see this failure on nifi-web-api !image-2019-07-12-12-48-47-442.png! I see the following in my local .m2 repository: !image-2019-07-12-12-47-58-020.png! I've tried to clean my entire ~/.m2/repository/org/apache/nifi folder (to rebuild everything) It would seem that the build is trying to find a "tests" folder. Keep in mind that I am trying to disable all unit tests. The reason I am doing this is because inevitably when I try to build nifi unit tests will often fail (and not always consistently).. I'm trying to disable unit tests since right now they just get in the way of my building of nifi. I've also noticed that one of the files is named: nifi-web-security-1.10.0-SNAPSHOT-tests.jar.lastUpdated This is not a proper jar file.. I'm not sure why it has a lastUpdated extension was (Author: dsargrad): Hi [~mcgilman] I still see this failure on nifi-web-api !image-2019-07-12-12-48-47-442.png! I see the following in my local .m2 repository: !image-2019-07-12-12-47-58-020.png! I've tried to clean my entire ~/.m2/repository/org/apache/nifi folder (to rebuild everything) It would seem that the build is trying to find a "tests" folder. Keep in mind that I am trying to disable all unit tests. The reason I am doing this is because inevitably when I try to build nifi unit tests will often fail (and not always consistently).. I'm trying to disable unit tests since right now they just get in the way of my building of nifi. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883979#comment-16883979 ] David Sargrad edited comment on NIFI-6415 at 7/12/19 4:54 PM: -- Hi [~mcgilman] I still see this failure on nifi-web-api !image-2019-07-12-12-48-47-442.png! I see the following in my local .m2 repository: !image-2019-07-12-12-47-58-020.png! I've tried to clean my entire ~/.m2/repository/org/apache/nifi folder (to rebuild everything) It would seem that the build is trying to find a "tests" folder. Keep in mind that I am trying to disable all unit tests. The reason I am doing this is because inevitably when I try to build nifi unit tests will often fail (and not always consistently).. I'm trying to disable unit tests since right now they just get in the way of my building of nifi. was (Author: dsargrad): Hi [~mcgilman] I still see this failure on nifi-web-api !image-2019-07-12-12-48-47-442.png! I see the following in my local .m2 repository: !image-2019-07-12-12-47-58-020.png! I've tried to clean my entire ~/.m2/repository/org/apache/nifi folder (to rebuild everything) > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883979#comment-16883979 ] David Sargrad commented on NIFI-6415: - Hi [~mcgilman] I still see this failure on nifi-web-api !image-2019-07-12-12-48-47-442.png! I see the following in my local .m2 repository: !image-2019-07-12-12-47-58-020.png! I've tried to clean my entire ~/.m2/repository/org/apache/nifi folder (to rebuild everything) > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6415: Attachment: image-2019-07-12-12-48-47-442.png > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6415: Attachment: image-2019-07-12-12-47-58-020.png > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6415: Description: I am trying to build the latest nifi master from git. git clone [https://gitbox.apache.org/repos/asf/nifi.git] git checkout master I am using the command mvn install -Dmaven.test.skip=true The build consistently fails with the following message. !image-2019-07-02-14-11-15-318.png! I deleted my entire .m2 repository to force maven to download. I get the same results. Many other projects seem to build ok. was: I am trying to build the latest nifi master from git. git clone [https://gitbox.apache.org/repos/asf/nifi.git] git checkout master I am using the command mvn install -Dmaven.test.skip=true The build consistently fails with the following message. !image-2019-07-02-14-11-15-318.png! I deleted my entire .m2 repository to force maven to download. I get the same results. Many other projects seem to build ok. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6415: Description: I am trying to build the latest nifi master from git. git clone [https://gitbox.apache.org/repos/asf/nifi.git] git checkout master I am using the command mvn install -Dmaven.test.skip=true The build consistently fails with the following message. !image-2019-07-02-14-11-15-318.png! I deleted my entire .m2 repository to force maven to download. I get the same results. Many other projects seem to build ok. was: I am trying to build the latest nifi master from git. git clone [https://gitbox.apache.org/repos/asf/nifi.git] git checkout master I am using the command mvn install -Dmaven.test.skip=true The build consistently fails with the following message. !image-2019-07-02-14-11-15-318.png! I deleted my entire .m2 repository to force maven to download. I get the same results. Many other projects seem to build ok. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6415: Description: I am trying to build the latest nifi master from git. git clone [https://gitbox.apache.org/repos/asf/nifi.git] git checkout master I am using the command mvn install -Dmaven.test.skip=true The build consistently fails with the following message. !image-2019-07-02-14-11-15-318.png! I deleted my entire .m2 repository to force maven to download. I get the same results. Many other projects seem to build ok. was: I am trying to build the latest nifi master from git. I am using the command mvn install -Dmaven.test.skip=true The build consistently fails with the following message. !image-2019-07-02-14-11-15-318.png! I deleted my entire .m2 repository to force maven to download. I get the same results. Many other projects seem to build ok. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6415) Nifi Build Fails on nifi-web-api
David Sargrad created NIFI-6415: --- Summary: Nifi Build Fails on nifi-web-api Key: NIFI-6415 URL: https://issues.apache.org/jira/browse/NIFI-6415 Project: Apache NiFi Issue Type: Bug Environment: centos 7 mvn 3.6.0 java 1.8.0_212 openjdk Reporter: David Sargrad Attachments: image-2019-07-02-14-11-15-318.png I am trying to build the latest nifi master from git. I am using the command mvn install -Dmaven.test.skip=true The build consistently fails with the following message. !image-2019-07-02-14-11-15-318.png! I deleted my entire .m2 repository to force maven to download. I get the same results. Many other projects seem to build ok. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6343: Attachment: image-2019-07-02-07-30-53-042.png > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png, image-2019-07-01-12-18-36-113.png, > image-2019-07-02-07-30-53-042.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876883#comment-16876883 ] David Sargrad commented on NIFI-6343: - Builds fine when I turn off unit tests. Because of my commitment to support NIFI, I'm inclined to try again, and write issues for the failed unit tests. I will also try to isolate, and report, as best I can since I'm keen to better understand the unit test framework. !image-2019-07-02-07-30-53-042.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png, image-2019-07-01-12-18-36-113.png, > image-2019-07-02-07-30-53-042.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876324#comment-16876324 ] David Sargrad edited comment on NIFI-6343 at 7/1/19 4:27 PM: - I dont know if I should create an issue for this. This is the current failure we see: !image-2019-07-01-12-18-36-113.png! The project that fails to build in this fashion is (the ones before all passed): [INFO] nifi-spring-bundle . SUCCESS [ 0.020 s] [INFO] nifi-spring-processors . FAILURE [06:24 min] We built using mvn install (turned off threading) Now we will turn off unit tests, -Dmaven.test.skip=true was (Author: dsargrad): I dont know if I should create an issue for this. This is the current failure we see: !image-2019-07-01-12-18-36-113.png! The project that fails to build in this fashion is (the ones before all passed): [INFO] nifi-spring-bundle . SUCCESS [ 0.020 s] [INFO] nifi-spring-processors . FAILURE [06:24 min] We built using mvn install (turned off threading) > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png, image-2019-07-01-12-18-36-113.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876324#comment-16876324 ] David Sargrad edited comment on NIFI-6343 at 7/1/19 4:20 PM: - I dont know if I should create an issue for this. This is the current failure we see: !image-2019-07-01-12-18-36-113.png! The project that fails to build in this fashion is (the ones before all passed): [INFO] nifi-spring-bundle . SUCCESS [ 0.020 s] [INFO] nifi-spring-processors . FAILURE [06:24 min] We built using mvn install (turned off threading) was (Author: dsargrad): I dont know if I should create an issue for this. This is the current failure we see: !image-2019-07-01-12-18-36-113.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png, image-2019-07-01-12-18-36-113.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876324#comment-16876324 ] David Sargrad commented on NIFI-6343: - I dont know if I should create an issue for this. This is the current failure we see: !image-2019-07-01-12-18-36-113.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png, image-2019-07-01-12-18-36-113.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6343: Attachment: image-2019-07-01-12-18-36-113.png > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png, image-2019-07-01-12-18-36-113.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876275#comment-16876275 ] David Sargrad edited comment on NIFI-6343 at 7/1/19 3:43 PM: - Hi [~bende] We are trying to build nifi again. I've noticed an old post on nifi.rocks that indicates that nifi unit tests wont pass when building with openjdk.. Is this still the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] We continue to struggle building nifi. The unit tests are the things that fail again and again, often different ones. Though I'd love to run the unit tests, for now I am ok with simply disabling them. What is the best way to disable unit tests? Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! was (Author: dsargrad): Hi [~bende] We are trying to build nifi again. I've noticed an old post on nifi.rocks that indicates that nifi unit tests wont pass when running with openjdk.. Is this still the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] We continue to struggle building nifi. The unit tests are the things that fail again and again, often different ones. Though I'd love to run the unit tests, for now I am ok with simply disabling them. What is the best way to disable unit tests? Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876275#comment-16876275 ] David Sargrad edited comment on NIFI-6343 at 7/1/19 3:40 PM: - Hi [~bende] We are trying to build nifi again. I've noticed an old post on nifi.rocks that indicates that nifi unit tests wont pass when running with openjdk.. Is this till the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] We continue to struggle building nifi. The unit tests are the things that fail again and again, often different ones. Though I'd love to run the unit tests, for now I am ok with simply disabling them. What is the best way to disable unit tests? Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! was (Author: dsargrad): Hi [~bende] We are trying to build nifi again. I've noticed an old post on nifi.rocks that indicates that nifi unit tests wont pass when running with openjdk.. Is this till the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] We continue to struggle building nifi. The unit tests are the things that fail again and again, often different ones. Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876275#comment-16876275 ] David Sargrad edited comment on NIFI-6343 at 7/1/19 3:40 PM: - Hi [~bende] We are trying to build nifi again. I've noticed an old post on nifi.rocks that indicates that nifi unit tests wont pass when running with openjdk.. Is this still the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] We continue to struggle building nifi. The unit tests are the things that fail again and again, often different ones. Though I'd love to run the unit tests, for now I am ok with simply disabling them. What is the best way to disable unit tests? Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! was (Author: dsargrad): Hi [~bende] We are trying to build nifi again. I've noticed an old post on nifi.rocks that indicates that nifi unit tests wont pass when running with openjdk.. Is this till the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] We continue to struggle building nifi. The unit tests are the things that fail again and again, often different ones. Though I'd love to run the unit tests, for now I am ok with simply disabling them. What is the best way to disable unit tests? Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876275#comment-16876275 ] David Sargrad edited comment on NIFI-6343 at 7/1/19 3:38 PM: - Hi [~bende] We are trying to build nifi again. I've noticed an old post on nifi.rocks that indicates that nifi unit tests wont pass when running with openjdk.. Is this till the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] We continue to struggle building nifi. The unit tests are the things that fail again and again, often different ones. Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! was (Author: dsargrad): Hi [~bende] We are trying to build nifi again. I've noticed an old issue that indicates that nifi unit tests wont pass when running with openjdk.. Is this till the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876275#comment-16876275 ] David Sargrad commented on NIFI-6343: - Hi [~bende] We are trying to build nifi again. I've noticed an old issue that indicates that nifi unit tests wont pass when running with openjdk.. Is this till the case? [https://www.nifi.rocks/getting-started-with-apache-nifi/] Currently we are using openjdk. !image-2019-07-01-11-36-52-582.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6343: Attachment: image-2019-07-01-11-36-52-582.png > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png, > image-2019-07-01-11-36-52-582.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858559#comment-16858559 ] David Sargrad commented on NIFI-6343: - I really have a lot of problems building the NIFI system. I have run many build attempts, and each and every time it seems to fail in a different way, often on seemingly random packages. I've started to avoid building the unit tests, since they too are problematic. I have successfully built the whole system once or twice. I've attempted to build the whole system (on exactly the same code base), about 20 times. I've been trying to build as follows (per getting started documentation--- with the addition of the skip): mvn -T C2.0 install -Dmaven.test.skip=true > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858559#comment-16858559 ] David Sargrad edited comment on NIFI-6343 at 6/7/19 12:04 PM: -- I really have a lot of problems building the NIFI system. I have run many build attempts, and each and every time it seems to fail in a different way, often on seemingly random projects. I've started to avoid building the unit tests, since they too are problematic. I have successfully built the whole system once or twice. I've attempted to build the whole system (on exactly the same code base), about 20 times. I've been trying to build as follows (per getting started documentation--- with the addition of the skip): mvn -T C2.0 install -Dmaven.test.skip=true was (Author: dsargrad): I really have a lot of problems building the NIFI system. I have run many build attempts, and each and every time it seems to fail in a different way, often on seemingly random packages. I've started to avoid building the unit tests, since they too are problematic. I have successfully built the whole system once or twice. I've attempted to build the whole system (on exactly the same code base), about 20 times. I've been trying to build as follows (per getting started documentation--- with the addition of the skip): mvn -T C2.0 install -Dmaven.test.skip=true > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854819#comment-16854819 ] David Sargrad commented on NIFI-6327: - Ty [~bende]. We will give up on eclipse.. :) I think intellij seems like the way for us to go. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854812#comment-16854812 ] David Sargrad commented on NIFI-6343: - I'm also seeing a few more unexplained unit test failures.. such as this one from nifi-livy-processors !image-2019-06-03-12-47-07-720.png! > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6343: Attachment: image-2019-06-03-12-47-07-720.png > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png, image-2019-06-03-12-47-07-720.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
[ https://issues.apache.org/jira/browse/NIFI-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854779#comment-16854779 ] David Sargrad commented on NIFI-6343: - It looks like one or two other nifi projects fail in the same fashion (use of /tmp during unit test, and not cleaning the /tmp area afterwards) > nifi-ignite-processors fails to build because /tmp/ignite was owned by another > -- > > Key: NIFI-6343 > URL: https://issues.apache.org/jira/browse/NIFI-6343 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-06-03-11-57-12-907.png, > image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, > image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, > image-2019-06-03-12-04-06-699.png > > > The nifi build fails again and again on nifi-ignite-processors. It seems to > build everything else successfully. > > > !image-2019-06-03-12-04-06-699.png! > > > > It turns out that the test case attempts to write to /tmp/ignite. > > !image-2019-06-03-12-02-59-709.png! > > > > However if another user on the same computer ran a past build of nifi, then > that /tmp/ignite directory is not writable (nor is it cleaned up). It would > seem that such test cases should not write in a /tmp directory that is shared. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6343) nifi-ignite-processors fails to build because /tmp/ignite was owned by another
David Sargrad created NIFI-6343: --- Summary: nifi-ignite-processors fails to build because /tmp/ignite was owned by another Key: NIFI-6343 URL: https://issues.apache.org/jira/browse/NIFI-6343 Project: Apache NiFi Issue Type: Bug Environment: centos 7 java-1.8.0-openjdk-1.8.0.191.b12-1.el7_6.x86_64 Reporter: David Sargrad Attachments: image-2019-06-03-11-57-12-907.png, image-2019-06-03-11-58-15-523.png, image-2019-06-03-12-00-44-650.png, image-2019-06-03-12-01-35-030.png, image-2019-06-03-12-02-59-709.png, image-2019-06-03-12-04-06-699.png The nifi build fails again and again on nifi-ignite-processors. It seems to build everything else successfully. !image-2019-06-03-12-04-06-699.png! It turns out that the test case attempts to write to /tmp/ignite. !image-2019-06-03-12-02-59-709.png! However if another user on the same computer ran a past build of nifi, then that /tmp/ignite directory is not writable (nor is it cleaned up). It would seem that such test cases should not write in a /tmp directory that is shared. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854650#comment-16854650 ] David Sargrad commented on NIFI-6327: - I've now given up on eclipse.. and am starting to use intellij. Eclipse just gave us too many problems. If any of the NiFi developers could recommend an IDE that they've used with success... with NiFi.. I'd consider using that. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853699#comment-16853699 ] David Sargrad edited comment on NIFI-6327 at 6/1/19 2:33 PM: - My last problem seems to be the source lookup path. The debugger is currently only finding the source code for my main NiFi project. I attempted to follow the instructions [here|http://h22208.www2.hpe.com/eginfolib/networking/docs/sdn/sdnc2_7/5200-0910prog/content/s_sdnc-eclipse-AttachingSource.html], and selected all NiFi projects. However this does not seem to work !image-2019-06-01-09-40-38-299.png! As you see in the following, my current source lookup path, seems to have every last NiFi project. !image-2019-06-01-09-42-13-371.png! was (Author: dsargrad): My last problem seems to be the source lookup path. The debugger is currently only finding the source code for my main NiFi project. I attempted to follow the instructions [here|[http://h22208.www2.hpe.com/eginfolib/networking/docs/sdn/sdnc2_7/5200-0910prog/content/s_sdnc-eclipse-AttachingSource.html]], and selected all NiFi projects. However this does not seem to work !image-2019-06-01-09-40-38-299.png! As you see in the following, my current source lookup path, seems to have every last NiFi project. !image-2019-06-01-09-42-13-371.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-10-20-04-869.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853716#comment-16853716 ] David Sargrad commented on NIFI-6327: - Partial Success. I now have a break point in the Compress Provenance Logs thread. Notice eclipse even finds my source code. !image-2019-06-01-10-19-30-506.png! To get here, I changed the debug project as follows (note project nifi-framework-core): !image-2019-06-01-10-20-04-869.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853716#comment-16853716 ] David Sargrad edited comment on NIFI-6327 at 6/1/19 2:20 PM: - Partial Success. I now have a break point in the Compress Provenance Logs thread. Notice eclipse even finds my source code. !image-2019-06-01-10-19-30-506.png! To get here, I changed the debug configuration as follows (note project nifi-framework-core): !image-2019-06-01-10-20-04-869.png! was (Author: dsargrad): Partial Success. I now have a break point in the Compress Provenance Logs thread. Notice eclipse even finds my source code. !image-2019-06-01-10-19-30-506.png! To get here, I changed the debug project as follows (note project nifi-framework-core): !image-2019-06-01-10-20-04-869.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png, > image-2019-06-01-10-20-04-869.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-10-19-30-506.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png, image-2019-06-01-10-19-30-506.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853711#comment-16853711 ] David Sargrad commented on NIFI-6327: - Ok. I found a clue [here|https://stackoverflow.com/a/15788009/2025407]. I believe this will work. I was not sure what project to setup when i first created a debug configuration. Indeed the project I had selected was nifi-bootstrap, and as we saw above, eclipse actually found that source code. !image-2019-06-01-10-08-35-334.png! I will try to create another debug configuration for a different NiFi project. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-10-08-35-334.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png, > image-2019-06-01-10-08-35-334.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853702#comment-16853702 ] David Sargrad commented on NIFI-6327: - As an aside, I've also tried to provide the source base directory (and all of its subcontent) as the source lookup path.. still no go. !image-2019-06-01-09-50-46-652.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-09-50-46-652.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png, image-2019-06-01-09-50-46-652.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853699#comment-16853699 ] David Sargrad commented on NIFI-6327: - My last problem seems to be the source lookup path. The debugger is currently only finding the source code for my main NiFi project. I attempted to follow the instructions [here|[http://h22208.www2.hpe.com/eginfolib/networking/docs/sdn/sdnc2_7/5200-0910prog/content/s_sdnc-eclipse-AttachingSource.html]], and selected all NiFi projects. However this does not seem to work !image-2019-06-01-09-40-38-299.png! As you see in the following, my current source lookup path, seems to have every last NiFi project. !image-2019-06-01-09-42-13-371.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-09-42-13-371.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png, > image-2019-06-01-09-42-13-371.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-09-40-38-299.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png, image-2019-06-01-09-40-38-299.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-09-35-28-483.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853698#comment-16853698 ] David Sargrad commented on NIFI-6327: - Yay.. I was able to suspend the main thread while it was waiting for an attach. In the following, you will see the callstack displayed in the "Debug" window. The entry point for NiFi is in NiFi.java. !image-2019-06-01-09-32-35-143.png! NNote since I have suspended main, only the Daemon Thread is running. None of the other threads that we saw in my above comment are running yet. !image-2019-06-01-09-34-28-359.png! As an aside, in order to suspend a thread in eclipse. Right click on the thread name in the "Debug" window, and then click Suspend. !image-2019-06-01-09-35-28-483.png! > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png, > image-2019-06-01-09-35-28-483.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-09-34-28-359.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png, image-2019-06-01-09-34-28-359.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-09-32-35-143.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png, > image-2019-06-01-09-32-35-143.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853694#comment-16853694 ] David Sargrad edited comment on NIFI-6327 at 6/1/19 1:31 PM: - I've made some additional progress with this. I found the eclipse "Debug" view, under Window/Show View/Debug. This showed me a running view of all the NIFI threads.. In the following, I've suspended the NiFi Web Server-24 thread. Now all I need to do is to edit the source lookup path. I hope there is a way to do this for the entire project. !image-2019-06-01-09-19-46-853.png! Anyways I'm close. Once I tie this up, I will post in a summary comment that I hope helps other prospective NiFi developers. was (Author: dsargrad): I've made some additional progress with this. I found the eclipse "Debug" view, under Window/Show View/Debug. This showed me a running view of all the NIFI threads.. In the following, I've suspended the NiFi Web Server-24 thread. Now all I need to do is to edit the source lookup path. I hope there is a way to do this for the entire project. !image-2019-06-01-09-19-46-853.png! Here again, I'd love some help from any NiFi developer that uses eclipse. Please keep in mind its not eclipse specifically that I am looking for help with.. Its how to properly setup a NiFi development environment in eclipse.. perhaps a subtle distinction, but critical in my mind for any open source community that is looking to encourage use of their platform. Anyways I'm close. Once I tie this up, I will post in a summary comment that I hope helps other prospective NiFi developers. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853694#comment-16853694 ] David Sargrad edited comment on NIFI-6327 at 6/1/19 1:22 PM: - I've made some additional progress with this. I found the eclipse "Debug" view, under Window/Show View/Debug. This showed me a running view of all the NIFI threads.. In the following, I've suspended the NiFi Web Server-24 thread. Now all I need to do is to edit the source lookup path. I hope there is a way to do this for the entire project. !image-2019-06-01-09-19-46-853.png! Here again, I'd love some help from any NiFi developer that uses eclipse. Please keep in mind its not eclipse specifically that I am looking for help with.. Its how to properly setup a NiFi development environment in eclipse.. perhaps a subtle distinction, but critical in my mind for any open source community that is looking to encourage use of their platform. Anyways I'm close. Once I tie this up, I will post in a summary comment that I hope helps other prospective NiFi developers. was (Author: dsargrad): I've made some additional progress with this. I found the eclipse "Debug" view, under Window/Show View/Debug. This showed me a running view of all the NIFI threads.. In the following, I've suspended the NiFi Web Server-24 thread. Now all I need to do is to edit the source lookup path. I hope there is a way to do this for the entire project. !image-2019-06-01-09-19-46-853.png! Here again, I'd love some help from any NiFi developer that uses eclipse. Anyways I'm close. Once I tie this up, I will post in a summary comment that I hope helps other prospective NiFi developers. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853694#comment-16853694 ] David Sargrad commented on NIFI-6327: - I've made some additional progress with this. I found the eclipse "Debug" view, under Window/Show View/Debug. This showed me a running view of all the NIFI threads.. In the following, I've suspended the NiFi Web Server-24 thread. Now all I need to do is to edit the source lookup path. I hope there is a way to do this for the entire project. !image-2019-06-01-09-19-46-853.png! Here again, I'd love some help from any NiFi developer that uses eclipse. Anyways I'm close. Once I tie this up, I will post in a summary comment that I hope helps other prospective NiFi developers. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Sargrad updated NIFI-6327: Attachment: image-2019-06-01-09-19-46-853.png > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png, image-2019-06-01-09-19-46-853.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853106#comment-16853106 ] David Sargrad edited comment on NIFI-6327 at 5/31/19 3:42 PM: -- So.. I've tried to start nifi with remote debugging enabled... I do see that port 8000 is now bound.. !image-2019-05-31-11-14-01-380.png! However its not clear to me how to attach... properly. Eclipse asked me for a project. I tried "nifi-bootstrap". I've attached.. as seen here: !image-2019-05-31-11-33-50-040.png! However I cant seem to hit any breakpoints.. I've littered RunNiFI with breakpoints that are never hit, even when i query nifi for status (line 221 breakpoint), or shut it down (line 224 breakpoint). !image-2019-05-31-11-34-48-219.png! I've also tried to suspend startup.. to wait for an attach. !image-2019-05-31-11-36-08-343.png! However i still cant seem to find and set an appropriate breakpoint. Please provide guidance/help. was (Author: dsargrad): So.. I've tried to start nifi with remote debugging enabled... I do see that port 8000 is now bound.. !image-2019-05-31-11-14-01-380.png! However its not clear to me how to attach... properly. Eclipse asked me for a project. I tried "nifi-bootstrap". I've attached.. as seen here: !image-2019-05-31-11-33-50-040.png! However I cant seem to hit any breakpoints.. I've littered RunNiFI with breakpoints that are never hit, even when i query nifi for status, or shut it down. !image-2019-05-31-11-34-48-219.png! I've also tried to suspend startup.. to wait for an attach. !image-2019-05-31-11-36-08-343.png! However i still cant seem to find and set an appropriate breakpoint. Please provide guidance/help. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (NIFI-6327) Enhance NIFI Developer documentation to assist in developing NIFI in IDE
[ https://issues.apache.org/jira/browse/NIFI-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853106#comment-16853106 ] David Sargrad edited comment on NIFI-6327 at 5/31/19 3:41 PM: -- So.. I've tried to start nifi with remote debugging enabled... I do see that port 8000 is now bound.. !image-2019-05-31-11-14-01-380.png! However its not clear to me how to attach... properly. Eclipse asked me for a project. I tried "nifi-bootstrap". I've attached.. as seen here: !image-2019-05-31-11-33-50-040.png! However I cant seem to hit any breakpoints.. I've litted RunNiFI with breakpoints that are never hit, even when i query nifi for status, or shut it down. !image-2019-05-31-11-34-48-219.png! I've also tried to suspend startup.. to wait for an attach. !image-2019-05-31-11-36-08-343.png! However i still cant seem to find and set an appropriate breakpoint. Please provide guidance/help. was (Author: dsargrad): So.. I've tried to start nifi with remote debugging enabled... I do see that port 8000 is now bound.. !image-2019-05-31-11-14-01-380.png! However its not clear to me how to attach. Eclipse asked me for a project. I tried "nifi-bootstrap". I've attached.. as seen here: !image-2019-05-31-11-33-50-040.png! However I cant seem to hit any breakpoints.. I've litted RunNiFI with breakpoints that are never hit, even when i query nifi for status, or shut it down. !image-2019-05-31-11-34-48-219.png! I've also tried to suspend startup.. to wait for an attach. !image-2019-05-31-11-36-08-343.png! However i still cant seem to find and set an appropriate breakpoint. Please provide guidance/help. > Enhance NIFI Developer documentation to assist in developing NIFI in IDE > > > Key: NIFI-6327 > URL: https://issues.apache.org/jira/browse/NIFI-6327 > Project: Apache NiFi > Issue Type: Wish > Components: Core Framework >Affects Versions: 1.9.2 > Environment: LINUX: Centos 7 > ECLIPSE: Oxygen >Reporter: David Sargrad >Priority: Major > Attachments: image-2019-05-29-08-59-30-173.png, > image-2019-05-29-08-59-59-849.png, image-2019-05-29-09-00-39-263.png, > image-2019-05-29-09-01-47-311.png, image-2019-05-29-09-04-24-313.png, > image-2019-05-29-09-06-00-609.png, image-2019-05-31-07-29-48-733.png, > image-2019-05-31-07-30-09-097.png, image-2019-05-31-07-32-03-067.png, > image-2019-05-31-11-13-01-963.png, image-2019-05-31-11-14-01-380.png, > image-2019-05-31-11-33-50-040.png, image-2019-05-31-11-34-48-219.png, > image-2019-05-31-11-36-08-343.png > > > I followed the following instructions to clone and build NIFI: > [https://nifi.apache.org/quickstart.html] > I've successfully built the system, using maven. > > !image-2019-05-29-09-01-47-311.png! > > However its not at all clear how to develop and run the system in an IDE such > as eclipse, or a "recommended IDE". > Currently I'm trying to get the system up and running in eclipse. > > However I'm seeing many problems (see image below). I'm guessing all of these > can be solved with a simple set of configuration commands. > Ultimately adding such details to the documentation would be useful. For now, > I'd appreciate if someone can help with the configuration I am missing. > > !image-2019-05-29-09-00-39-263.png! > > If I click on one of the failed projects, I see the following error. > > !image-2019-05-29-09-04-24-313.png! > > !image-2019-05-29-09-06-00-609.png! > > I've also noticed that many of the pom files show up with an error. The error > is seen below: > !image-2019-05-31-07-29-48-733.png! > > !image-2019-05-31-07-30-09-097.png! > This error shows up on the "parent" tag > !image-2019-05-31-07-32-03-067.png! > > I am using the following version of eclipse, and maven > > !image-2019-05-29-08-59-59-849.png! > > !image-2019-05-29-08-59-30-173.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
