[GitHub] nifi pull request: NIFI-1409: Fix missing transfer on error in Exe...

Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/178#discussion_r50171832 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteSQL.java --- @@ -164,17

[GitHub] nifi pull request: NIFI-1409: Fix missing transfer on error in Exe...

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/178#discussion_r50174170 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteSQL.java --- @@ -164,17

Re: Auto-Organize Layout

Maybe not exactly "auto-layout" but I would back a notion of having the components snap to a coarser grain grid than what we currently have. Sometimes I care a lot about having everything line up in the graph horizontally and vertically, and it always takes a long time to achieve this. I could

Re: Auto-Organize Layout

+1 to adding capabilities that will allow users to build the desired layout more efficiently. Allowing them to more easily align components, snap-to-grid, lock, and bend connections would all fall into this category. I'm a little indifferent to supporting an auto-layout feature. I've tried a

Stop a Processor with a spam notification to start it again

How about this.. Add another "stop" state that includes a notification to a distro every 5 minutes a processor is stopped. That way if you stop a production processor, leave for the day, and forget to turn it back on, it's at least spamming a distro to remind you or your group to click "start"

[GitHub] nifi pull request: NIFI-1273 Adding ListenRELP Processor

GitHub user bbende opened a pull request: https://github.com/apache/nifi/pull/179 NIFI-1273 Adding ListenRELP Processor This pull request adds a ListenRELP processor which includes refactoring code that was previously part of ListenSyslog into a reusable framework for implementing

Re: Auto-Organize Layout

I like your idea Rob, that would help with lining up relationships too (straight lines). On Matt's note, I don't think there should be a "standard" either, although best practices are always out there. On Matt's note of putting failures up above processes, we do that too. Totally depends on who

[GitHub] nifi pull request: NIFI-1409: Fix missing transfer on error in Exe...

Github user mattyb149 commented on a diff in the pull request: https://github.com/apache/nifi/pull/178#discussion_r50170753 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteSQL.java --- @@ -164,17

Re: Auto-Organize Layout

+1 for "snap to grid" feature Sent from my iPhone > On Jan 19, 2016, at 4:20 PM, dan bress wrote: > > Maybe not exactly "auto-layout" but I would back a notion of having the > components snap to a coarser grain grid than what we currently have. > Sometimes I care a lot

Re: Auto-Organize Layout

Elli "it is sometimes too easy to mis-align processors by dragging them accidentally" Great point I must admit I too do that. Often in really important demos. I've gotten good at making jokes about it. Probably should have gotten good at submitting a JIRA :-) I'd like to understand more

Re: Auto-Organize Layout

I also think that some way to help layout the flow would be very useful. One of the hardest parts of creating an easy to read workflow is the designing a good layout, and in many cases I simply want to be able to select a few processors and line them up (horizontally or vertically). Also, it is

[GitHub] nifi pull request: NIFI-1409: Fix missing transfer on error in Exe...

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/178#discussion_r50158533 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteSQL.java --- @@ -164,17

Re: Auto-Organize Layout

I agree with Matt's points. I was just replying with something similar basically saying I think trying to set a standard would not be well-received. I believe what could be more useful are layout tools that would help users place components to help achieve their preferred layouts. For example,

Re: [DISCUSS] roadmap for the next 6-12 months

Team, I had a lengthy conversation today with Matt Gilman to talk through specifics of the Authorizer API concept. The ideas are captured here https://cwiki.apache.org/confluence/display/NIFI/Support+Authorizer+API. Definitely would like to hear ideas from people experienced in working with

[GitHub] nifi pull request: NIFI-1273 Adding ListenRELP Processor

Github user trkurc commented on the pull request: https://github.com/apache/nifi/pull/179#issuecomment-173044611 I like the docs to help with reviewing! I good amount here to review and test! --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] nifi pull request: NIFI-1378 fixed JMS URI validation

Github user trkurc commented on the pull request: https://github.com/apache/nifi/pull/167#issuecomment-173043643 reviewing now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

Re: Stop a Processor with a spam notification to start it again

Ryan, I've considered implementing something like this before but just never had the cycles. I do think it's a good idea, though. The approach that I would take is to write a Reporting Task, though. It would not be any change to the framework. Rather, the reporting task would just run, say

[GitHub] nifi pull request: NIFI-1409: Fix missing transfer on error in Exe...

Github user JPercivall commented on a diff in the pull request: https://github.com/apache/nifi/pull/178#discussion_r50213360 --- Diff: nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ExecuteSQL.java --- @@ -164,17

Re: Javadoc

What is the best way to do this? mvn site? On Tue, Jan 19, 2016 at 8:41 AM, Sean Busbey wrote: > Hi Devin! > > Sorry for the gap. We're tracking the need for a web accessible copy > of our API javadocs in NIFI-943. I don't believe anyone has taken up > the task yet, so if

Re: Javadoc

Hi Devin! Sorry for the gap. We're tracking the need for a web accessible copy of our API javadocs in NIFI-943. I don't believe anyone has taken up the task yet, so if you're looking to get more involved in the project we'd love the help! On Sun, Jan 17, 2016 at 1:38 PM, Devin Fisher

[GitHub] nifi pull request: NIFI-569 Creating basis for integration-tests i...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/173 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request: NIFI-569 Creating basis for integration-tests i...

Github user mcgilman commented on the pull request: https://github.com/apache/nifi/pull/173#issuecomment-172864860 +1 Went ahead and merged the proposed changes for the build infrastructure. Specifics for this integration test can be updated as needed. --- If your project is set up

[GitHub] nifi pull request: [NIFI-1394] - Unit test creates resources in HO...

Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/174 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[GitHub] nifi pull request: [NIFI-1394] - Unit test creates resources in HO...

Github user mcgilman commented on the pull request: https://github.com/apache/nifi/pull/174#issuecomment-172874349 Build looks good. No more artifacts showing up in user home directory. Thanks! --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] nifi pull request: [NIFI-1394] - Unit test creates resources in HO...

Github user smarthi commented on the pull request: https://github.com/apache/nifi/pull/174#issuecomment-172875249 Thanks for merging this PR. Do we similarly modify all of the other TestJdbc* to take a TemporaryFolder ? --- If your project is set up for it, you can reply to this

[GitHub] nifi pull request: [NIFI-1394] - Unit test creates resources in HO...

Github user mcgilman commented on the pull request: https://github.com/apache/nifi/pull/174#issuecomment-172880667 I wasn't aware of any issues with the other JDBC tests. This JIRA was created to specifically address the tests resources being created in the user's HOME directory. If

[GitHub] nifi pull request: [NIFI-1411] - TestJdbcTypesDerby: java.sql.SQLS...

GitHub user smarthi opened a pull request: https://github.com/apache/nifi/pull/177 [NIFI-1411] - TestJdbcTypesDerby: java.sql.SQLSyntaxErrorException: TYPE 'DATETIME' does not exist ... also fixed the other TestJdbcXXX.java classes to use @Rule TemporaryFolder You can merge this

[GitHub] nifi pull request: NIFI-1409: Fix missing transfer on error in Exe...

GitHub user mattyb149 opened a pull request: https://github.com/apache/nifi/pull/178 NIFI-1409: Fix missing transfer on error in ExecuteSql This change keeps track of the "working flowfile", either the incoming flowfile if one exists, or the one created if no incoming flowfile