Re: [DISCUSS] Bringing MiNiFi into NiFi

Apologies if this has been discussed previously. I've not kept up on the Mi/NiFi progress as much lately. When I think of two projects being combined I usually consider the connection between the lifecycles of the two projects. One thing I always liked about MiNiFi being separate was its ability

Re: [VOTE] Release Apache NiFi 1.10.0 (rc3)

+1 (non-binding) Built and ran successfully and built custom processor with 1.10.0 dependency and successfully uploaded NAR to NiFi Registry 0.5.0. On Wed, Oct 30, 2019 at 4:06 PM Mark Payne wrote: > +1 (binding) > > Was able to build and verify that all of the Jiras that I raised last time >

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0 RC2

+1 non-binding Built and ran MiNiFi and C2 without issues. On Thu, Jun 28, 2018 at 3:59 PM Aldrin Piri wrote: > +1, binding > > comments: > My vote is on the assumption there there was a slight mix up with tagging > and it can be easily remedied. The > 05f516d3da33a0547ccfad342414504cdacd4a68

Re: [DISCUSS] Tar + Gzip vs. Zip

As a user I always download the zip file. Echoing Mike's reply, I work across Linux, Windows, and OSX and my mouse always goes toward the zip. I've never run into any file permission/attribute issues with the zip distribution. Everything that should be executable always has been. So if you axed

Re: [VOTE] Release Apache NiFi 1.7.0

+1 non-binding Went through the guide without any problems. Ran some simple flows with no issues. After the first build I did see a Maven-generated directory called something like "${project.parent.directory}" in the source root. I deleted the entire thing, unzipped the source release again,

Re: [VOTE] Release Apache NiFi Registry 0.2.0

+1 non-binding Ran through the release helper guide with no issues. Good stuff! On Sat, Jun 16, 2018 at 5:47 PM Andy LoPresto wrote: > Sorry everyone, > > Committers can provide binding votes on technical discussions (such as to > call for a release), but only PMC members can provide binding

Re: Dependency versions in processors in 1.6.0

gt; versions now need to be specified? We could at least update the > processor bundle archetype to have these versions specified to make it > easier for new bundles, and maybe add something to the migration notes > for existing bundles. > > Thanks, > > Bryan > > > On T

Dependency versions in processors in 1.6.0

Hi, In <=1.5.0 processors I used nifi-nar-bundles as the parent project and dependency management was handled for me. Changing to 1.6.0 resulted in a few "missing dependency version" errors. I think this is expected due to NIFI-4936 ("NiFi parent pom dependency management forcing versions to

Re: MiNiFi PeriodicStatusReporter and AWS CloudWatch

needed via the context exposed to the reporting task. > --aldrin > On Wed, May 23, 2018 at 8:41 AM, Jeff Zemerick <jzemer...@apache.org> wrote: > > Hi everyone, > > > > I'm looking for ways to monitor a distributed fleet of MiNiFi (Java) > > installations. I'd li

Re: Read processor property in init()

indicates > that the method that is marked with this annotation will run when a > processor is started every time. So basically the setup() will be called > and executed everytime the processor is started from the UI. > > On Wed, 28 Mar 2018 at 6:34 PM, Jeff Zemerick <jzemer...@apache.org&

Re: Read processor property in init()

I will give that a go. Thanks for the quick answer, Mike! On Wed, Mar 28, 2018 at 9:01 AM, Mike Thomsen <mikerthom...@gmail.com> wrote: > Just do... > > @OnScheduled > public void setup(ProcessContext context) { > //Read properties and do setup. > } > > On Wed,

Read processor property in init()

Hi everyone, Is there a recommended method for making user-configurable property values available to a processor's init()? I would like to load a large index file but allow the user to specify the index's path. I am guessing that init() is executed too early to read user properties. Thanks for

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

+1 non-binding Built successfully and tests pass. Ran some simple flows -- worked as expected. On Tue, Mar 27, 2018 at 9:59 AM, Matt Burgess wrote: > +1 (binding) Release this package as nifi-1.6.0 > > Verified checksums, commit, L, etc. Ran full build with unit tests >

Re: [DISCUSS] MiNiFi Flow Designer

I think it sounds like a good idea. The majority of the MiNiFi flows I have made are all fairly simple and I have not found the YAML authoring to be overly burdensome. The more complex flows were done in NiFi and converted. So as long as the option to make the flows by hand remains (and I don't

Re: [VOTE] Release Apache NiFi MiNiFi 0.4.0 RC2

+1 non-binding Built and ran fine. As mentioned in hipchat I didn't see the git tag nifi-minifi-0.4.0-RC2 but verified the commit. On Sat, Jan 20, 2018 at 3:00 PM, Ben Qiu wrote: > +1 > > On 2018-01-18 12:55, Aldrin Piri wrote: > > Hello,> > > > > I am

Re: [VOTE] Release Apache NiFi MiNiFi 0.4.0

Verified keys, hashes, and built fine with contrib-check. However it fails to start. (I did not modify the config prior to starting.) >From the log: 2018-01-18 11:31:40,743 WARN [main] org.apache.nifi.minifi.MiNiFiServer Failed to start minifi server... shutting down. java.lang.Exception: Unable

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

+1 non-binding Built with contrib-check. Stepped through release guide. Ran into a minor issue with the TestListenSMTP unit tests on OSX but it might be pretty specific to my computer. https://issues.apache.org/jira/browse/NIFI-4760 On Wed, Jan 10, 2018 at 10:26 AM, Pierre Villard <

Re: Apache NiFi 1.5.0 (RC1) Release Helper Guide

Hi Joe, I'm getting a 404 on those download links. Thanks On Tue, Jan 9, 2018 at 5:19 AM, Joe Witt wrote: > Hello Apache NiFi community, > > Please find the associated guidance to help those interested in > validating/verifying the release so they can vote. > > # Download

Re: [VOTE] Release Apache NiFi MiNiFi 0.3.0 - RC3

+1 non-binding verified hashes verified signature verified git commit verified RC branch commit successful build with contrib-check verified the three sets of README, LICENSE, NOTICE files verified windows service operation Thanks for putting these RCs together! Jeff On Tue, Dec 19, 2017 at

MiNiFi (Java) 0.3.0

I'm curious what the community thinks about a Java MiNiFi 0.3.0 release. Looks like 18 tasks [1] have been closed in 0.3.0 and there are no open pull requests. Is there anything outstanding that is waiting to be addressed and should go into a 0.3.0? Thanks, Jeff [1]

MINIFI-403 and JsonParseException

Hi all, While working on Java MiNiFi in the master branch I ran into a NoClassDefFoundError for org.codehaus.jackson.JsonParseException (stack trace at the bottom) when MiNiFi starts. Thinking I had not seen this before I reverted MINIFI-403 since it dealt with dependencies, rebuilt, and the

Re: Separate MiNiFi projects in JIRA

t; wrote: > >> > >> Clones can cross projects. I'm a +1 for the suggestion of separate > >> projects so as to keep a 1-to-1 between projects and repos. Related > tickets > >> can be linked or cloned to provide context when applicable. > >> >

Re: Separate MiNiFi projects in JIRA

aking the > existing Component field required. As to feasibility, I leave that up to > someone that has more experience working with ASF infra to administer these > ASF JIRA projects (Aldrin?). > > > > -Kevin > > > > On 8/21/17, 15:00, "Jeff Zemerick" <jzemer...@apac

Re: Separate MiNiFi projects in JIRA

such > as 'minificpp' but I'd like to avoid that until we're really sure we > want to bug em. > > Thanks > > On Mon, Aug 21, 2017 at 11:03 AM, Andy Christianson > <achristian...@hortonworks.com> wrote: > > Agree 100%. I have been bitten by this

Separate MiNiFi projects in JIRA

The MINIFI project in JIRA is currently a combination of issues for both the C++ and Java implementations. Some issues for the C++ project do have the C++ component set but some don't and it can sometimes be hard to easily differentiate the issues by their titles. (There isn't a "Java" component

Processor for Apache Rya

I have a processor that ingests triples to Apache Rya. Would it be ok to work on a pull request to include this processor in NiFi? (I guess what I am asking more broadly is if there is any selection criteria that determines what processors are included in NiFi?) Thanks, Jeff

Re: [DISCUSS] Apache Gitbox

Also from OpenNLP -- yes, the workflow is much simpler and faster. I highly recommend it. On Fri, Jul 28, 2017 at 3:00 PM, Suneel Marthi wrote: > We migrated Apache OpenNLP to gitbox (beginning of July) and even had a > release immediately. > > Yes, the PR commit workflow is

Re: MiNiFi Java as Windows Service

with a profile I added to the minifi-assembly project (assuming InnoSetup is on your computer). If you think there might be a broad appeal for this I'll be happy to make a pull request for it. Thanks, Jeff On Mon, Jun 26, 2017 at 6:13 PM, Jeff Zemerick <jzemer...@apache.org> wrote: > Thanks ev

Re: MiNiFi Java as Windows Service

PR would most certainly be welcomed and (likely could be an easy win > > for > > > NiFi as well). The only caveat to be mindful of is that any > > > frameworks/tools/utilities should be friendly with ALv2 terms as per > > > http://www.apache.org/legal/resolved.html. I

MiNiFi Java as Windows Service

Hi, I see a ticket to make the C++ version run as a Windows service (MINIFI-89). Is there a recommended method of running the Java version as a Windows service? If not, would there be any interest in a pull request to add that functionality? Thanks, Jeff

Re: [VOTE] Release Apache NiFi MiNiFi 0.2.0

+1 (non-binding) Build/tests with contrib-check Ran and successfully tested a simple flow On Tue, May 16, 2017 at 12:54 PM, Marc wrote: > +1 non-binding > > Verified sigs && hashes. > >Built and ran test flows that I used for MiNiFi-C++ to include Site to > Site, and

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

+1 non-binding Full contrib-check build on clean Ubuntu 16.04 image. Tested with some simple flows. A few sparse, intermittent unit test failures were added to JIRA. Jeff On Sun, May 7, 2017 at 8:27 AM, Matt Gilman wrote: > +1 binding > > Verified hashes,

Re: seemingly random junit test errors in 1.2.0-source-release

ome tests and on different > systems. Happily this release I find far better than previous ones but we > still have work to do for sure. > > Thanks > Joe > > > On May 5, 2017 10:14 AM, "Jeff Zemerick" <jzemer...@apache.org> wrote: > > I'm getting a

seemingly random junit test errors in 1.2.0-source-release

I'm getting a few random test errors when building the 1.2.0 source release. The failures seem to be completely random. I have built many times per the steps below and most times everything is ok but every now and then one of the tests fails. I can't reproduce any of them in Maven or Eclipse.