I suppose I was a bit remiss in not unwinding and/or summarizing some of
what was in that yetus thread to prime the discussion, but a some of what
Andy is mentioning is expanded on a bit in this ietf document [1], which is
linked in one of the articles.
1. https://tools.ietf.org/id/draft-knodel-te
Hi Edward, thanks for sharing your thoughts. I’ll reply inline.
> - Some of the terms proposed are not industry standard and may potentially
> cause significant issue for non-english speakers.
I actually believe making these changes will _improve_ the clarity for
non-english speakers. “Whitelis
Edward
Im not aware of any changes we need to make which move from standard to non
standard. And as far as I know it is pretty straightforward. If we come
up with equally useful or slightly better terms and somehow make the
community more approachable for even a single person then I think it is
This is a difficult issue and causes no small amount of friction every
time. I'm personally against this for the following reassons:
- Some of the terms proposed are not industry standard and may potentially
cause significant issue for non-english speakers.
- For each change that is made can we g
+1 for making this change to NiFi and all NiFi sub-projects. Let me know how I
can assist.
Kevin
> On Jun 17, 2020, at 9:23 PM, Aldrin Piri wrote:
>
> +1 for making the changes.
>
> On Wed, Jun 17, 2020 at 8:11 PM Andy LoPresto wrote:
>
>> I am a proponent of making this change and also usi
+1 for making the changes.
On Wed, Jun 17, 2020 at 8:11 PM Andy LoPresto wrote:
> I am a proponent of making this change and also using allow/deny list,
> meddler-in-the-middle, etc.
>
> Here is a blog [1] with easy instructions for executing the change in git,
> although I don’t know if there i
I am a proponent of making this change and also using allow/deny list,
meddler-in-the-middle, etc.
Here is a blog [1] with easy instructions for executing the change in git,
although I don’t know if there is any Apache-integration specific changes we
would also need.
[1]
https://www.hanselm
I suspect it would be fairly easy to make this change. We do, I think,
have whitelist/blacklist in there somewhere but im not sure how involved.
On Wed, Jun 17, 2020 at 3:04 PM Tony Kurc wrote:
> All,
> I've seen the discussion started on other projects [1][2], so I wanted to
> kick off a discu
All,
I've seen the discussion started on other projects [1][2], so I wanted to
kick off a discussion to determine whether this is something nifi could
look at too. Allen Wittenauer's post to yetus captures the why and some of
the how, so rather than copy and pasting, you can take a look at what he'
Hello,
It is supported and working for a long time.
The Ranger NAR is not included by default so you will need to get it from
Maven central [1] and add to your NiFi lib directory.
This blog post should still be fairly accurate [2].
Thanks,
Bryan
[1] https://repo1.maven.org/maven2/org/apache/n
Hi Nifi Team,
I am using the latest version of Nifi and was looking to integrate with
latest apache ranger. I dont see any documentation on ranger integration
both on nifi or ranger other than old documentation from a few years back.
Wanted to check the roadmap on the support with Nifi integration
Hi Team,
Me & my team has an urgent requirement of preserving the timestamp of the
files that are present on remote ftp server while we are writing to HDFS.
We are able to write files on to HDFS using Nifi but the timestamp is
getting modified.
Is there some way I can prevent the timestamps of fi
12 matches
Mail list logo
