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

Requesting a courtesy extra day please :-) On Sat, Jun 25, 2016 at 11:12 AM, Joe Witt <joe.w...@gmail.com> wrote: > Timing these is not easy. But requesting a courtesy weekend extra day is > totally reasonable and has been done in the past. > On Jun 25, 2016 8:09 AM, "Rya

0.6.1 & 0.7.0 chkconfig (start on boot) bug centos 7

I'm trying to get the 0.7.0 NiFi to start on boot on linux/centos 7. During all this, I've noticed 0.6.1 doesn't quite work either, left some notes at the bottom about that. *For 0.7.0:* *I followed the modified install commands for the nifi.sh script:* I untar'd it in: #/opt/nifi/current ->

0.7.0 install bug centos 7

Looks like 0.7.0 doesn't install as a service quite right on linux/centos 7. I untar'd it in: #/opt/nifi/current -> nifi-0.7.0-SNAPSHOT I followed these steps: #/opt/nifi/current/bin/nifi.sh install #chkconfig nifi on #service nifi start That copies the nifi.sh script into /etc/init.d

Re: [DISCUSS] release line management

Sorry, put this in the wrong thread... In another thread, I put forth the recommendation of a 0.7.1 release, for features that don't make it in 0.7.0, but were intended to (to speed along the 0.7.0 release). As a consumer of NIFI, I still like that idea. Not being part of the dev team, but

Re: [DISCUSS] Closing in on the Apache NiFi 0.7.0 Release

In another thread, I put forth the recommendation of a 0.7.1 release, for features that don't make it in 0.7.0, but were intended to (to speed along the 0.7.0 release). As a consumer of NIFI, I still like that idea. Not being part of the dev team, but assuming based on their track record, I'm

Re: Apache NiFi 0.7.0 Release date ?

we really should be diligent about making JIRA as accurate as > >> possible. I fix these tickets as I find them, but it would help if > others > >> can also be on the lookout for these. > >> > >> Thanks, > >> -- Mike > >> > >> > >>

Re: Apache NiFi 0.7.0 Release date ?

ersion and move > things over to it which seem feasible. Then send another note. If > folks need things shuffled we can address them. > > Good call > > Joe > > On Tue, Jun 7, 2016 at 9:14 AM, Ryan H <rhendrickson.w...@gmail.com> > wrote: > > Any me

Re: Apache NiFi 0.7.0 Release date ?

e: > > PR #305 was merged into 0.x and master branches, so I updated NIFI-1686 > to > > reflect its Fix Version as 1.0.0, 0.7.0 > > > > -- Mike > > > > > > On Mon, Jun 6, 2016 at 5:08 PM, Ryan H <rhendrickson.w...@gmail.com> > wrote: > &g

Re: [DISCUSS] Apache NiFi 0.7.0 and 1.0.0

transformers for that now. Ryan On Fri, May 27, 2016 at 11:21 AM, Ryan H <rhendrickson.w...@gmail.com> wrote: > I'm looking forward to 0.7.. Plenty of awesome features, like SSL with the > AMQP processors (https://issues.apache.org/jira/browse/NIFI-1521) > > Thanks! > > O

Re: [DISCUSS] Apache NiFi 0.7.0 and 1.0.0

I'm looking forward to 0.7.. Plenty of awesome features, like SSL with the AMQP processors (https://issues.apache.org/jira/browse/NIFI-1521) Thanks! On Thu, May 26, 2016 at 7:52 AM, Joe Witt wrote: > Ok just to wrap up this thread. Will push a couple efforts > 1) Will start

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"

Re: Auto-Organize Layout

it is common to put labels over processor(s). Any relationships pointing > up > > would pass through these labels making both the relationship box and the > > label hard to read. It is often coomon to see flows designed with a > > combination of left to right and top to bottom

Re: Content Repo Large.. Archive in there?

[StandardContentClaim [resourceClaim=StandardResourceClaim[id=144559441-74079, container=default, section=351], offset=0, length=-1]] On Fri, Oct 23, 2015 at 2:59 PM, Ryan H <rhendrickson.w...@gmail.com> wrote: > Here's our provenance settings: > > # Persistent Provenance Reposi

Re: Content Repo Large.. Archive in there?

tional information so we can dig into why this may have arisen. > > Thanks! > > On Fri, Oct 23, 2015 at 10:25 AM, Ryan H <rhendrickson.w...@gmail.com> > wrote: > > > I've got the following set: > > > > nifi.content.repository.archive.max.retention.period=12

Re: Content Repo Large.. Archive in there?

usage > reached 100%. However, restarting nifi apparently enabled it to perform the > clearing of the archive. So apparently the max usage setting doesn't work > under some conditions, but we don't know what conditions occurred overnight > to cause this problem. > > > &

Re: Content Repo Large.. Archive in there?

nt repository and > provenance repository > both pointing to the same partition? What do you have the > "nifi.provenance.repository.max.storage.size" > property set to? How large is the actual disk? > > Thanks > -Mark > > > > On Oct 23, 2015, at 2:

Content Repo Large.. Archive in there?

Hi, I'm noticing my Content Repo growing large. There's a number of files... content_repo/837/archive/144...-837 Is this new in 3.0? My conf file says any archiving should be going into ./conf/archive, but i don't see anything in there. Thanks, Ryan

Re: Content Repo Large.. Archive in there?

t; > >Andrew > > > > > > > > > >On 10/23/15, 12:47 PM, "ryan.andrew.hendrick...@gmail.com on behalf of > Ryan H" <ryan.andrew.hendrick...@gmail.com on behalf of > rhendrickson.w...@gmail.com> wrote: > > > >>Hi, > >> I'm

Re: Content Repo Large.. Archive in there?

detail is available in the system properties of our > Administration Guide [1] > > Let us know if you have additional questions. > > --aldrin > > [1] > > https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#system_properties > > On Fri, Oct 23, 201

Re: Content Repo Large.. Archive in there?

lp indicate when the disk started filling up to > narrow down the timeframe to > look at in the logs. > > > > > > On Oct 23, 2015, at 3:27 PM, Ryan H <rhendrickson.w...@gmail.com> wrote: > > > > Yea.. they're all on the same partition. (We know.. not good