Re: [VOTE] Release Apache NiFi 0.2.1

, I only see it on Ubuntu 15.04 and the Bash version is GNU bash, version 4.3.30(1)-release (x86_64-pc-linux-gnu). Let me know if I can help with further tests. Joe On Sun, Jul 26, 2015 at 4:59 PM, Aldrin Piri aldrinp...@gmail.com wrote: Joe, These issues are captured in NIFI-758 [1

Re: [VOTE] Release Apache NiFi 0.2.1

Signatures good Hashes good LICENSE, NOTICE, and README present and well-formed On CentOS release 6.6 (Final) Build passes Contrib passes Assembly runs +1 to release this package [Binding] On Fri, Jul 24, 2015 at 12:07 PM, Mark Payne marka...@hotmail.com wrote: +1 Release this package as

Re: Content Repo Large.. Archive in there?

Ryan, Those archive folders map to the nifi.content.repository.archive.enabled property. What this property provides is a retention of files no longer in the system for historical context of your flow's processing and the ability for viewing this in conjunction with provenance events as well as

Re: Content Repo Large.. Archive in there?

.enabled=true > > Yet, the content repo filled my disk last night... > > > On Fri, Oct 23, 2015 at 1:16 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: > > > Ryan, > > > > Those archive folders map to the nifi.content.repository.archive.enabled > > property.

Re: nifi fails build on CentOS 7

Seems there is in fact an issue with the test cited prior. I received the following on my Travis CI build on a branch which has the latest of master merged into it. Unfortunately, it seems that the environment is not the same as before. In this case, Travis CI is running with Ubuntu 12.04 LTS

Re: Release wrangling: 1 week until our hopeful 0.4.0 release

Scanned through and removed the 0.4.0 tagging for State Management. Thanks for the suggestion. On Fri, Nov 13, 2015 at 10:10 AM, Sean Busbey wrote: > Has anyone had a chance to do a pass through Feature Proposals to move out > any that aren't going to make 0.4.0? > >

Re: EvaluateJsonPath error: Unable to return a scalar value for the expression

orks after I changed Return Type to JSON. > > > On Nov 16, 2015, at 12:47 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: > > > > Sumo, > > > > The scalar option has the processor looking for the resultant value of > the > > expression to provide

Re: Release wrangling: 1 week until our hopeful 0.4.0 release

not > > > sure how to attack this one > > > NIFI-1108 > > > > > > * NEW * > > > LogAttribute processor fix (Oleg Zhurakousky) - trivial fix? but > breaking > > > change? I recommend moving to 0.5.0 > > > NIFI-1139 > > &

Re: NiFI Custom Plugin - Yield Duration Ignored

I appreciate the use of patterns, but given that non-devs will often be interepeting these types of issues, I think the name is a miss in recognizability. Regardless, we can and should do better about clarifying the language in the logs and docs. On Tue, Nov 17, 2015 at 11:46 AM, Oleg

Re: informations

Hi Samuel, The content of the FlowFile is returned as part of the response. As a result, you could pass the file through various processors to formulate an ad hoc web service and receive the associated content. As a quick example, you can take the request, pass it through a ReplaceText with a

Re: LogAttribute - Sending that output to a custom logger?

We greatly appreciate contributions. Your prescribed approach sounds great and if you are willing to give us a few cycles pointing out, and optionally correcting, the items that are in need of improvement, we will certainly incorporate. Thanks! On Mon, Nov 2, 2015 at 1:28 PM, Mark Petronic

Re: Next release?

- git push > > It may be as simple as clicking the merge button in github, but I haven't > tried :) > > > On Tue, Nov 3, 2015 at 10:37 AM, Aldrin Piri <aldrinp...@gmail.com> wrote: > > > We certainly follow the RTC process with NiFi. As Joe mentioned, as lon

Incorporation of other Maven repositories

I am writing to see what the general guidance and posture is on incorporating additional repositories into the build process. Obviously, Maven Central provides a very known quantity. Are there other repositories that are viewed with the same level of trust? If so, is there a listing? If not, do

Re: Next release?

few projects > within the coming months. I can't find a cite for this at the moment, but > it's something they're working on. > > On Tue, Nov 3, 2015 at 9:48 AM, Aldrin Piri <aldrinp...@gmail.com> wrote: > > > Unfortunately, at least for the NiFi world (not sure i

Re: Fulfilling a pull request

That way seems reasonable and should work. The only negative, and I use the term loosely, is the continuous addition of remotes as new contributors provide submissions (certainly a nice problem to have!). There are a few other ways you can tackle this to combat adding a remote for each user that

Re: help with adding a process

Pat, As a quick check, did you add the fully qualified package name of your processor (org.mitre.nitfimages.Processor Classname) to the org.apache.nifi.processor.Processor file within the nifi-image-processors src/main/resources/META-INF/services directory? The overall structure provided seems

Re: Setting Isolated Processors

Edgardo, Can definitely see how this could be confusing and I think we can do a better job of making it more straightforward. I have created an issue to get the documentation a bit more tightly integrated with the UI a user works against. [1] [1] https://issues.apache.org/jira/browse/NIFI-897

Re: 0.3.0 In-depth Testing

to this let me know. Thanks, Bryan [1] https://issues.apache.org/jira/browse/NIFI-895 On Wed, Aug 26, 2015 at 10:08 AM, Aldrin Piri aldrinp...@gmail.com wrote: Folks, I will be acting as the Release Manager for the upcoming 0.3.0 release. I am pleased to announce the tickets that were

0.3.0 In-depth Testing

Folks, I will be acting as the Release Manager for the upcoming 0.3.0 release. I am pleased to announce the tickets that were originally assigned with a fix version of 0.3.0 have been completed and many great features and improvements have been incorporated. Over the past couple of days, some

Re: Facing problem from ExecuteSQL processor

Shubham, ExecuteSQL requires an input flowfile to cause processing to occur. Based off your message, it sounds like this is the only instance and thus there is no action occurring. This is certainly unclear on our behalf in terms of documentation on the processor. By design, this processor

Re: Facing problem from ExecuteSQL processor

Shubham, One more note. While I was typing up the last email, it appears a ticket was created to alter ExecuteSQL to carry out the functionality I think you are looking for. It can be located here: https://issues.apache.org/jira/browse/NIFI-932 On Fri, Sep 4, 2015 at 1:25 PM, Aldrin Piri

Re: [jira] [Created] (NIFI-921) Create a processor to promote character delimited data to attributes

depending on expression needed. On Thu, Sep 3, 2015 at 7:57 AM, Joe Skora <jsk...@gmail.com> wrote: > Is the (very) general idea sort of a combination of the functionality > ExtractText and UpdateAttributes? > > On Thu, Sep 3, 2015 at 12:37 AM, Aldrin Piri (JIRA) <j...@apache.org&g

Re: [VOTE] Release Apache NiFi 0.3.0

* signatures and hashes good * code matches specified commit hash * necessary files present * assembly builds as anticipated and passes all tests and contrib-check * convenience binary starts up and runs flows +1 - Release this package as nifi-0.3.0 [binding] On Wed, Sep 16, 2015 at 12:18 PM,

Re: Using output relationships for user-selection and dynamic property change of another processor

Rick, At first read, my particular instinct feels that heading down the attribute path may better serve you than connections. What I am interested in hearing is the next step of these flowfiles with associated opcodes. To another processor? To many processors? As to 1, there should not be an

Re: need help with Async code

Sumo, I did some digging around on your Github Repo and see that you've migrated your ControllerService lookup to your @OnScheduled method, making use of the ProcessContext. This approach is certainly more preferred in terms of allowing configuration of the Processor than the prior method you

Re: need help with Async code

ishEventBus.java#L102 > < > https://github.com/xmlking/nifi-websocket/blob/master/src/main/java/com/crossbusiness/nifi/processors/PublishEventBus.java#L102 > > > > Thanks > Sumo > > > On Sep 30, 2015, at 2:52 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: >

Re: Dynamic Properties for Processor

You certainly are on the right path and have the right ideas, but there are some details to work out. The biggest item here is that GetTwitter does not support dynamic properties for the credentials, largely because it does not take FlowFiles in as input to the processor. GetTwitter falls into

Re: Dynamic Properties for Processor

In terms of why there are restrictions, it is about intended usage and how given exposed properties are . Dynamic properties on those processors that have certain resources they are relying upon may not be as friendly as the framework is to these dynamic changes. Accordingly, the power of

Re: At what stage data become's NiFi's "problem"

I think Joe's perspective maps more closely to what Andre was searching for in terms of a knowing when a consumer can be notified/guaranteed of successful handoff of data in the overall flow process. Primarily, the key factor is that this mechanism provides at least once delivery in that the unit

Re: Release wrangling: 1 week until our hopeful 0.4.0 release

ov 16, 2015 at 11:47 AM, Joe Percivall > > >> >> <joeperciv...@yahoo.com.invalid> wrote: > > >> >> > Per NiFi-1165: a discussion is occurring on the ticket: > > >> >> https://issues.apache.org/jira/browse/NIFI-1165 > > >> &

Re: Streaming large result set - ExecuteSQL

Hi Vinay, Seems like this could be a nice addition. Do you have specific database systems in mind where you may have been experiencing issues? This would aid us in establishing a test scenario to evaluate against. >From the NiFi side, we try to be quite good about handling data of all volumes

Re: Long running processors, stopping and timeouts.

Toivo, Joe, Started a draft of this yesterday and glad to see Joe chime in with some additional input. I think now that 0.4.0 is on the cusp of getting wrapped up and put through its paces, now is a good time to consider something like this that is a big win for our users and helps iron out some

Re: WebAppContext Failed startup of context

As another data point, I had success with a very similar environment as Andre. Details below: [apiri@brick nifi-0.4.0-SNAPSHOT]$ cat /etc/centos-release CentOS Linux release 7.1.1503 (Core) [apiri@brick nifi-0.4.0-SNAPSHOT]$ uname -a Linux brick 3.18.17-13.el7.x86_64 #1 SMP Wed Jul 22 14:20:15

Re: WebAppContext Failed startup of context

@Tony I do have the OpenJDK installed (just from yum install) [apiri@brick nifi-0.4.0-SNAPSHOT]$ stat /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91-2.6.2.1.el7_1.x86_64/bin/javac File: ‘/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91-2.6.2.1.el7_1.x86_64/bin/javac’ Size: 7360 Blocks: 16 IO

Re: [UI Bug] delete route of RouteOnAttribute processor

Bob, The error indicates that there were files in the queue. This is as expected in terms of how connections are handled as these connections are the queues that hold the actual FlowFiles as they progress through their flow. A FlowFIle "passes through" a processor as it moves from one

Re: [VOTE] Release Apache NiFi 0.4.0 (rc2)

untu 14.04 (all x86_64) and > Windows > > 10 (64 bit) build all going simultaneously now. Should cover the problem > > children from last RC. So happy TestJdbcHugeStream is faster. > > > > > > > > On Tue, Dec 8, 2015 at 8:43 PM, Aldrin Piri <aldrinp...@gmail.com>

Re: Questions on Apache NiFi

Manoj, 1. In terms of functionality to support this, there are mechanisms that provide the capability of accomplishing this type of functionality in components via ControllerServices like the [DistributedMapCacheServer][1]/Client or [DistributedSetCacheServer][2]/Client. There are processors

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

this path. > Mans > > On Saturday, January 9, 2016 1:16 PM, Aldrin Piri < > aldrinp...@gmail.com> wrote: > > > Mans, > > In the way I specified via the linked snippet, we could potentially just > have it implement the AWSCredentialsProvider signature, and in

Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

how would the subclass of AbstractAWSProcessor > call createClient allow the two arguments (creds and creds provider) to > work seemlessly. Let me know if you have any other thoughts/paths I can > investigate. > Thanks for the feedback and I am learning a lot with this experience. &

Re: [VOTE] Release Apache NiFi 0.4.1 (rc1)

Just a heads up for anyone playing along at home. The GitHub mirror seems to be lagging behind our core, ASF repository and the associated tag with the specified commit is not currently mirrored. When verifying source if you default to GitHub and are unable to checkout that revision, please try

Re: PRs

No qualms here. If they look good to go while the work and testing surrounding NIFI-655 wraps up, they might as well be included. Would not want to delay the release should any of these become protracted in terms of iterations. On Tue, Nov 24, 2015 at 4:05 PM, Tony Kurc wrote:

Re: Provenance tuning

Ian, Could you provide information as to how your repositories are configured? Specifically, what the layout is to physical volume(s)/disks? On Monday, November 30, 2015, ianwork wrote: > I am also experiencing a slowdown with the provenance reporter and would > like >

Re: Patch Submitted - Re: Nifi-1325 - Enhancing Nifi AWS S3 for cross account access - Refactoring Nifi-AWS Processor credentials to use credentials provider

ward for your feedback. > Mans > > On Saturday, January 9, 2016 1:43 PM, Aldrin Piri < > aldrinp...@gmail.com> wrote: > > > Mans, > > Sounds great. Feel free to let us know if you have any issues and we are > happy to work through it with you. Thanks ag

Re: Integrate with Microsoft Azure

Brig, Nothing is currently on the roadmap for a specific release, but there are two issues that have some activity on JIRA and a working PR. https://issues.apache.org/jira/browse/NIFI-1922 Please feel free to add on with any additional details or cases that are not included. On Wed, May 25,

Re: Nifi behind AWS ELB

InvokeHTTP may be the better option if the user is not interested in transmitting content _packaged as_ FlowFiles. Someone with a bit more history than myself can provide some additional context if I have strayed off the path, but PostHTTP and ListenHTTP were precursors to Site to Site. While

Re: Suggestion of processors

Andre, The proposed processors all sound like nice functionality. I did have a couple of questions. Concerning the ParseKV, are you aware of the getDelimitedField[1] function in Expression Language? I think this may take care of this case for handling these items. With the QueryBulkWhois API,

Re: Suggestion of processors

lized arrays, I suspect replacing content with JSON downstream would > be a handy choice but I am open to different suggestions. > > Cheers. > > > > > On Wed, Jun 22, 2016 at 10:35 AM, Andre <andre-li...@fucs.org> wrote: > > > > > Aldrin, >

Re: question regarding input stream from reddit.com

Shahzad, Joe is correct in that we do not have anything that maps directly to this data stream source. As a means of getting the data into a NiFi flow, you could also consider https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ExecuteProcess/index.html

Re: ApacheCon presence?

Sean, I have been tossing a couple of ideas around in my head for a proposal. Hoping to be able to tie a few of them together in a cohesive manner and compose an abstract. On Tue, Feb 9, 2016 at 11:49 AM, Sean Busbey wrote: > Hi folks! > > CFPs for ApacheCon NA Core and

Re: planning for apache nifi 0.5.0

RC during our release evaluation and voting process. Thanks! --aldrin On Thu, Feb 4, 2016 at 10:33 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: > All, > > Just as an update on some of the remaining items. I have been doing some > review work to help close out some of

Re: Provenance reporting

Richard, In terms of capturing and recording these items about are things that make the State Management [1] coming up in the 0.5.0 release for interfacing with a StateManager to record these items in a framework provided mechanism. This would be the preferred approach moving forward. Until

Re: [DISCUSS] git branching model

On board with Tony's points. I think the realities of merging in practice when that "breaking point" of sorts occurs will make the complexity and overhead quite difficult and maybe even more error prone than the cherry picking approach with some additional guidelines. When the codebase

Re: FlowFiles missing (MissingFlowFileException)

Lars, Are you able to share your flow or a template of it so we can try to recreate? If not, could you give some information as to what it is doing and what processors/components are involved. Are there any custom components? Thanks! On Tue, Feb 16, 2016 at 10:18 PM, Joe Witt

Re: Mutiple dataflow jobs management(lots of jobs)

Hi Yan, We can get more into details and particulars if needed, but have you experimented with expression language? I could see a Cron driven approach which covers your periodic efforts that feeds some number of ExecuteSQL processors (perhaps one for each database you are communicating with)

Re: Establishment of MiNiFi repo and supporting tools

lt;marka...@hotmail.com> wrote: > > +1 from me as well > > On Mar 11, 2016, at 8:36 AM, Matt Burgess <mattyb...@gmail.com> wrote: > > I'm a +1 as well. > > On Mar 11, 2016, at 8:26 AM, Tony Kurc <trk...@gmail.com> wrote: > > Should this be marked as a [

Re: Closing in on the Apache NiFi 0.6.0 release

In an effort to avoid me missing helpers and spamming the list, I will throw my hat into the ring to do this one. On Tue, Mar 15, 2016 at 11:28 AM, Joe Witt wrote: > Team, > > Seeing good progress today. Great! > > I know I volunteered to do the RM for the release but now I

Re: Closing in on the Apache NiFi 0.6.0 release

Sounds great. Will scope those out in the process. Thanks, Tony. On Tue, Mar 15, 2016 at 11:37 AM, Tony Kurc <trk...@gmail.com> wrote: > Aldrin, > I did some crappy shell scripts to help, I'll try to put those up on the > wiki. > > Tony > > On Tue, Mar 15, 20

Establishment of MiNiFi repo and supporting tools

NiFi Community, Originally discussed in January [1], the MiNiFi agent model was met with positive feedback. I would like to propose a concerted effort toward the execution on the ideas presented and establish a basis for incorporation of the feedback received from, and collaboration with, the

Re: Establishment of MiNiFi repo and supporting tools

9, 2016 at 3:28 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: > NiFi Community, > > Originally discussed in January [1], the MiNiFi agent model was met with > positive feedback. I would like to propose a concerted effort toward the > execution on the ideas presented

Re: [VOTE] Release Apache NiFi 0.6.1 (RC1)

+1, binding Build and tests worked on OS X and Windows 7. Branch looked good on our Travis build and ran some flow templates from reviews from some of the associated issues with anticipated results. Verified hashes and signatures. On Wed, Apr 6, 2016 at 5:33 PM, Joe Witt

Re: [DRAFT][REPORT] Apache NiFi - April 2016

Joe, looks great overall. Minor point is that the vote for 0.6.0 wrapped up Saturday, 26 March. Awesome growth for the community. Certainly felt like that was the case, nice to see actual numbers. On Wed, Apr 6, 2016 at 10:55 PM, Joe Witt wrote: > NiFi Community, > >

Re: [VOTE] Establish Apache MiNiFi, a subproject of Apache NIFi

+1 I think it the effort shall provide a lot of value On Sat, Apr 9, 2016 at 1:13 AM, Joe Witt wrote: > Team, > > Following a solid discussion [1] in early January regarding > establishment of MiNiFi as a subproject of NiFi I'd like to call a > formal vote to record this

Re: [VOTE] Release Apache NiFi 0.6.1 (RC1)

; > > The source start point is the "nifi-0.6.1-source-release.zip" file, after > > checksum validation and unzipping. > > > > I let you know if network makes a difference. > > > > Joe > > > > > > > > On Sat, Apr 9, 2016 at

Re: [VOTE] Release Apache NiFi 0.6.1 (RC1)

Joe, Are these all running on the same network? If so, anything novel or different about it? Also, a I assume these are remnants of debugging, but noticed some differences in terms of the source at the tagged RC and your stacktraces. TestGetHTTP, for instance, only has 431 lines and the test

Re: patch and pull request reviewing question

Sounds good to here as well. Given the increasing number of contributions, which predominantly seem to arrive via GitHub PR, I also created NIFI-1615 [1] a little while ago to make a GitHub PR template [1]. Would like to distill the contributor guide down into a few easy steps for folks to check

[VOTE] Release Apache NiFi 0.6.0 (RC1)

Hello, I am pleased to be calling this vote for the source release of Apache NiFi nifi-0.6.0. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1077 The Git tag is NIFI-1634-RC1 The Git commit hash is

Re: [VOTE] Release Apache NiFi 0.6.0 (RC1)

ng RSA key ID 4CFE5D00 > gpg: Good signature from "Aldrin Piri (Code Signing Key) < > ald...@apache.org>" I receive similar errors on another system I did not perform/verify the release process on. For now, I ask that folks likely hold up until I can resolve the issue and

Re: NiFi-1660

Chris, Awesome that you are ready to dive in and get this fixed up. The functionality is certainly one that would be helpful. I do find myself a bit torn on whether the inclusion of this as EL is preferred instead of the extension of EvaluateJsonPath as suggested in NIFI-1567 [1]. Are there use

[VOTE] Release Apache NiFi 0.6.0 (RC2)

Hello Apache NiFi Community, I am pleased to be calling this vote for the source release of Apache NiFi, nifi-0.6.0. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1079/ The Git tag is nifi-0.6.0-RC2 The Git

Apache NiFi 0.6.0 RC2 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/dev/nifi/KEYS # Import keys file: gpg --import KEYS # [optional] Clear out local

Re: Closing in on the Apache NiFi 0.6.0 release

; > >> > > > >> > - Add support for Spring Context loaded processors (Spring > > >> > Integrations, Camel, ...) [4] > > >> > [status] Appears ready. Getting review feedback. > > >> > > > >> > - Support based dat

[ANNOUNCE] Apache NiFi 0.6.0 release

Hello, The Apache NiFi team would like to announce the release of Apache NiFi 0.6.0. Apache NiFi is an easy to use, powerful, and reliable system to process and distribute data. Apache NiFi was made for dataflow. It supports highly configurable directed graphs of data routing,

Re: [VOTE] Release Apache NiFi 0.6.0 (RC1)

at 8:00 AM, Aldrin Piri <aldrinp...@gmail.com> wrote: > Drat, the announce email was wrong (likely glossed over it copying and > pasting), but the md5sum provided to the repository is correct > ( nifi-0.6.0-source-release.zip.md5). I did an md5 against the artifact as > pro

Re: Closing in on the Apache NiFi 0.6.0 release

?p=nifi.git;a=commit;h=e4b7e47836edf47042973e604005058c28eed23b [2] https://github.com/apache/nifi/commit/e4b7e47836edf47042973e604005058c28eed23b Thanks! On Tue, Mar 22, 2016 at 2:11 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: > Bryan, Matt, > > Both of these seem pretty

[RESULT][VOTE] Release Apache NiFi 0.6.0

Hello Apache NiFi Community, The release of Apache NiFi 0.6.0 passes with 5 +1 (binding) votes 4 +1 (non-binding) votes 1 +0 (binding) votes Thanks to all who helped make this release possible. Here is the PMC vote thread:

Re: [ANNOUNCE] Apache NiFi 0.5.1 release

Dropping announce off the list. Ryan, The information from the vote with associated hashes and tags can be found at: http://mail-archives.apache.org/mod_mbox/nifi-dev/201602.mbox/%3CCA%2BLyY55tjmjKrX05tnjPC_%3DjJ8QL0N53o%3Djq68XCJEpywB58sQ%40mail.gmail.com%3E >From that conversation, the

Re: OnStopped annotation

Pierre, I did a build of the specified branch, enabled the remote debugging and added a breakpoint within the AbstractSNMPProcessor#close method which was successfully triggered on stopping. I additionally added a breakpoint within ReflectionUtils and was able to trace that path to the same

Re: OnStopped annotation

2016-03-03 17:46 GMT+01:00 Aldrin Piri <aldrinp...@gmail.com>: > > > Thanks for the info. Are you doing all of this debugging local to that > > instance (via tunnel/VNC/etc) or connecting remotely across the network > to > > that instance? Also, what IDE are you usin

Re: OnStopped annotation

never got > triggered. > > Do you think I should try with another version of Java? > > > > > 2016-03-02 22:58 GMT+01:00 Aldrin Piri <aldrinp...@gmail.com>: > > > Pierre, > > > > I did a build of the specified branch, enabled the remote debu

Re: [DISCUSS] create apache nifi 0.6.1

Will take care of it. On Thu, Mar 31, 2016 at 11:20 AM, Joe Witt wrote: > We should also update the downloads page to ensure folks are aware of > this issue. > > I recommend phrasing such as: > "Before downloading this version please see the release notes [link]. > There is

Re: [DISCUSS] create apache nifi 0.6.1

Updated the downloads page and pushed out changes with the language you provided above. On Thu, Mar 31, 2016 at 11:27 AM, Aldrin Piri <aldrinp...@gmail.com> wrote: > Will take care of it. > > On Thu, Mar 31, 2016 at 11:20 AM, Joe Witt <joe.w...@gmail.com> wrote: >

Re: [RESULT][VOTE] Release Apache NiFi 0.6.0

...@mail.gmail.com%3E Apologies for the confusion. Thanks! On Sat, Mar 26, 2016 at 8:08 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: > Hello Apache NiFi Community, > > The release of Apache NiFi 0.6.0 passes with > > 5 +1 (binding) votes > 4 +1 (non-binding) votes > 1 +0 (binding)

Re: [DISCUSS] git branching model

th places as > applicable. > > >> > > > >> > Thanks. > > >> > > > >> > Matt > > >> > > > >> > [1] > > >> > > > >> > > > >> > > > http://mail-archives.apach

Re: [VOTE] Incorporate SHA256 part of release process

he preferred form > of assuring an artifact was not "bad". However, it looks like it isn't in > our checklist to confirm that SHA-1 wasn't used to make the digital > signature, and it looks like 0.6.1 is using SHA1. > > > 1. http://www.apache.org/dev/openpgp.htm

Removal of ProcessorLog

Hey folks, As a heads up, PR #403 [1]/NIFI-1811 is to be merged in imminently. This is part of cleaning up some of our code debt as we move toward 1.0 and removing of the ProcessorLog which was deprecated/supplanted by ComponentLog. For contributors, if possible, it would be desirable to make

AppVeyor integration merged

Hey folks, Just a note to let you know that AppVeyor has been incorporated for our 0.x and master branches. Not much will change in terms of the normal contribution process but we will receive indications for those PRs/branches that have the appveyor.yml (you may wish to rebase off your source

[DISCUSS] Extraction of Extension API

All, I would like to propose a refactoring of the nifi-api for our master/1.0 branch. In summary, a lightweight and concise view of this module allows for reduced footprint of the NIFI API for components and minimizes the creep of those items that authoring components do not need to use. In a

Re: [DISCUSS] Removal of FlowFilePrioritizer as first-class extension point

+1 for this. It also occurred to me that these are currently not shown in the generated docs and only in the user guide. Mike, As far as sorting by size, do you think there is merit beyond the PriorityAttributePrioritizer for this case? An update attribute "copying" fileSize to "priority"

Re: [ANNOUNCE] Apache NiFi 0.6.1 release

The "rel" prefix is a bit of a deviation from what we have been doing. Up to this point, it had been x.y.z-RC# up until a final release occurred resulting in just an x.y.z tag. On Mon, Apr 18, 2016 at 1:19 PM, James Wing wrote: > Found it, thank you. Is "rel/nifi-0.6.1" the

Re: [DISCUSS] From Contributor to Committer

Looks like a good set of information and listing of capacities in which the community can contribute for progression. On Wed, Apr 20, 2016 at 6:23 PM, Joe Witt wrote: > Bryan, > > That is a good point and I do think we should avoid putting such a > rule/requirement in place.

[VOTE] Incorporate SHA256 part of release process

This was mentioned in the vote thread for the RC2 release and wanted to separate it out to keep the release messaging streamlined. As mentioned by Andy, the MD5 and SHA1 are subject to collisions. From another viewpoint, I like having this as part of the official release process as I typically

Re: [ANNOUNCE] New Apache NiFi Committer Yolanda Davis

Congrats! On Sat, Jul 30, 2016 at 08:40 Mark Payne wrote: > Welcome, Yolanda! Excited to have you join us. Thanks for all of the > awesome contributions you've already provided! > > Sent from my iPhone > > > On Jul 30, 2016, at 8:16 AM, Tony Kurc wrote: >

Re: [VOTE] Release Apache NiFi 0.7.0 (RC2)

+1 Release this package as nifi-0.7.0 (binding) Hashes and signatures looked good. Build and contrib were clean. Cache of templates all seem to run as anticipated. Generated assemblies looked good on OS X, Debian 7, and CentOS 7. On Tue, Jul 12, 2016 at 7:23 AM, Pierre Villard

[DISCUSS] MiNiFi's Initial Release, 0.0.1

Hey folks, We've had some nice work done on the MiNiFi Java implementation but would love to start putting things through their paces and extend the community. To that end, I would like to tackle our first release and volunteer to take the RM duties. MiNiFi has benefitted from the extensive body

Re: [VOTE] Release Apache NiFi MiNiFi 0.0.1 (RC1)

installed, so this may be a 0.0.2 fix. > Is BouncyCastle not enabled by default?* Question about how processors and > connectors reference each other — it appears connectors reference source > processors by name but destination processors or ports by ID? Is this > consistent or just demon

Apache NiFi - MiNiFi 0.0.1 RC1 Release Helper Guide

Hello Apache NiFi community, Please find the associated guidance to help those interested in validating/verifying the release so they can vote. # Download latest KEYS file: https://dist.apache.org/repos/dist/dev/nifi/KEYS # Import keys file: gpg --import KEYS # [optional] Clear out local

[VOTE] Release Apache NiFi MiNiFi 0.0.1 (RC1)

Hello Apache NiFi Community, I am pleased to be calling this vote for the source release of Apache NiFi - MiNiFi, minifi-0.0.1. The source zip, including signatures, digests, etc. can be found at: https://repository.apache.org/content/repositories/orgapachenifi-1087 The Git tag is

Re: [DISCUSS] MiNiFi's Initial Release, 0.0.1

+Roadmap On Tue, Jul 5, 2016 at 10:43 PM, Andre <andre-li...@fucs.org> wrote: > Aldrin, > > This is great news! > > Are there plans of releasing minifi-cpp anytime soon? > > > > On Wed, Jul 6, 2016 at 6:53 AM, Aldrin Piri <aldrinp...@gmail.com> wrote: > >

[ANNOUNCE] Apache NiFi MiNiFi 0.0.1 release

Hello! The Apache NiFi team would like to announce the release of Apache NiFi - MiNiFi 0.0.1. MiNiFi is a subproject of Apache NiFi. MiNiFi provides a complementary data collection approach that supplements the core tenets of NiFi in dataflow management, focusing on the collection of data at

[DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1

Hey folks, There's been great efforts to get an initial working implementation of MiNiFi in C++. This currently provides a great start on the core functionalities that the Java equivalent provides. Perhaps the neatest of all these items is the C++ implementation of the Site to Site protocol

  1   2   3   4   >