Hi Andy,
I have tested it with NIFI 1.8.0
I get the a diferent error.
Unable to get the state for the specified component
afc9148c-0167-1000--a97bf4b6: java.io.IOException: Failed to obtain
value from ZooKeeper for component with ID afc9148c-0167-1000--a97bf4b6
with exception
Ah, thanks for clarifying.
I am also not aware of such functionality on GitHub. For me, the most
valuable feature is being able to better curate our old/stale issues
without empty commits and, if so desired, obviate the need for the "This
closes" phrasing.
In terms of my personal review
Aldrin,
Your comments have left me confused. Yes, in the past, I would always `-s` to
sign the commits and push them. But isn't the idea behind the improved GitHub
integration is that now I can just go to the PR and tell GitHub to accept the
PR after I've reviewed it. Thus the manual act of
Hello Phil,
When supporting an I/O intensive application such as NiFi at the enterprise
level, you have to plan for failures in your storage layer. Disks are
going to fail and you only get to choose how that failure will affect your
system. Here are some things to think about.
+ Use RAID for
That level of interoperability is not there and, from some quick searching,
do not believe it to be something that is supported. [1]
Not sure what is meant by sign-off being automated. Personally, I use the
-s flag when amending/pushing reviewed commits.
[1]
In this case I'd just update the behavior and docs to state that if a
value of '0 secs' is supplied then minimum age checks are bypassed
altogether.
Thanks
On Fri, Dec 14, 2018 at 3:38 PM Peter Wicks (pwicks) wrote:
>
> I'm working on a ticket that tweaks the way the Minimum File Age property
>
I'm working on a ticket that tweaks the way the Minimum File Age property works
in GetFile and ListFile (NIFI-5897). Right now users see "0 sec" and assumes
that means the minimum age check does not happen, when in fact it does; and in
some timezone scenarios you have future dated files, and
Does closing a PR through GitHub close the JIRA ticket correctly? I'm assuming
sign-off is automated this way, but wasn't sure about this step.
Thanks,
Peter
-Original Message-
From: Aldrin Piri [mailto:aldrinp...@gmail.com]
Sent: Friday, December 14, 2018 6:23 AM
To: dev
Subject:
(quick note: a markdown formatted version of this content is available at
[3])
All,
There was a flurry of messages as we sought to get some quick details out
about our migration to the ASF Gitbox system and I wanted to take this
message to consolidate those items into a comprehensive and less
Hi Raymond,
Thanks for sharing.
Currently we don't really have a great way to keep track of custom
NARs that live outside of the main distribution. However, the
community is working on adding extension bundles to NiFi Registry, and
eventually there would likely be a publicly available NiFi
Hi all,
I made a DocConverter to convert between different data formats
(XML,JSON,CSV,YAML). For those interested there is also a NiFi Processor:
https://github.com/assimbly/convertdataformat
https://github.com/assimbly/docconverter
I also wondered if there is a repository or list where to
Hi Raymond,
Thanks for calling that out. I am in the process of updating/deploying the
site as well as a final email with all the details but will be sure to
cover those links.
Thanks!
--aldrin
On Fri, Dec 14, 2018 at 10:37 AM ski n wrote:
> Maybe good to check the link on the NiFi website
Maybe good to check the link on the NiFi website (Development --> Source).
It still points out to "https://git-wip-us.apache.org/repos/asf?p=nifi.git;
Raymond
Op vr 14 dec. 2018 om 15:13 schreef Aldrin Piri :
> And in my frenzied typing, I made use of nifi-site's locations instead of
> NiFi.
>
And in my frenzied typing, I made use of nifi-site's locations instead of
NiFi.
NiFi is available at Gitbox for checkout at
https://gitbox.apache.org/repos/asf/nifi.git with its web view at
https://gitbox.apache.org/repos/asf?p=nifi.git
On Fri, Dec 14, 2018 at 8:23 AM Aldrin Piri wrote:
> Some
Aldrin,
Thanks for coordinating and sharing details.
For others,
Here is the experience I had this AM with this. You only have to do
the following if you want to be able to work natively in github. If
you dont care about that part then you can just change from git-wip
urls to gitbox in your
Some clarifying notes until I can get all the updates into place and
generate a new email.
There are now two locations that are writable by committers for each of our
repositories. The updated repository locations can be seen in the Apache
NiFi section of https://gitbox.apache.org/repos/asf.
16 matches
Mail list logo
