Hi all,
I've spent some time extending the PutCassandraRecord processor so that it can
also generate UPDATE statements. This is especially
useful in the context of Counter types, which can only be updated using these
statements.
I've had a quite a bit of back-and-forth with reviewers and hope t
Glenn,
Thanks for your comments. The canvas you've experienced unfortunately has
not landed in the Flow Design System yet. It is ultimately destined for
there but currently, only the NiFi Registry uses FDS. In time, NiFi will be
updated to also use it. At that time, the NiFi canvas should be a com
ran this over the weekend but forgot to respond.
I saw the other chain, which reminded me to respond. Sorry about that...
Ran my typical release build following the helper guide. Used my typical
test flow.
+1 if we can extend the vote, otherwise I'll jump on RC2.
On Fri, Feb 14, 2020 at 10:15
The release vote remains open for Rc1 as of now.
On Tue, Feb 18, 2020 at 9:45 AM Marc Parisi wrote:
> ran this over the weekend but forgot to respond.
>
> I saw the other chain, which reminded me to respond. Sorry about that...
>
> Ran my typical release build following the helper guide. Used
Ran over the release document and checked everything off. Looks good, ran a
few basic flows to test normal functionality.
+1 non-binding
Chad
On Tue, Feb 18, 2020 at 11:02 AM Joe Witt wrote:
> The release vote remains open for Rc1 as of now.
>
> On Tue, Feb 18, 2020 at 9:45 AM Marc Parisi wro
I was going through the guide over the weekend and hit the step about
verifying the RC was branched off the correct git commit. Is this done just
via looking in git at the commit for the tag and that the release vote
email has the same commit hash in it , or is the commit hash put somewhere
in the
Chad,
You basically want to ensure that a given release tag matches what we'd
expect. In this case we're doing a 1.11.2 release so you'd want it to be
1.11.1 plus updates.
https://gitbox.apache.org/repos/asf?p=nifi.git;a=log;h=6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
That link and the resulting
If you want to compare the actual content of the source, you could do
something like:
git clone https://git-wip-us.apache.org/repos/asf/nifi.git
git -C nifi checkout
diff --brief -r nifi-rc-source nifi
On Tue, Feb 18, 2020 at 11:18 AM Joe Witt wrote:
>
> Chad,
>
> You basically want to ensure t
Ok, Thank you Joe and Bryan for the clarification and options.
On Tue, Feb 18, 2020 at 11:27 AM Bryan Bende wrote:
> If you want to compare the actual content of the source, you could do
> something like:
>
> git clone https://git-wip-us.apache.org/repos/asf/nifi.git
> git -C nifi checkout
> d
+1, binding
Verified signatures, built and deployed a secured cluster on GCP, ran some
flows to verify the load balanced connections. LGTM.
Thanks Joe for taking care of this!
Le mar. 18 févr. 2020 à 08:09, Chad Zobrisky a écrit :
> Ran over the release document and checked everything off. Loo
Verified signatures, built and deployed a complex flow running over the
weekend with no issues.
+1 non-binding
Henry
On 2020/02/15 03:15:18, Joe Witt wrote:
> Hello,>
>
> I am pleased to be calling this vote for the source release of Apache
NiFi>
> 1.11.2.>
>
> The source zip, including signatu
+1 (binding)
- Verified signatures/hashes & LICENSES/NOTICES
- Ran full build
- Ran secure cluster with load balanced connections
Looks good, thanks!
On Tue, Feb 18, 2020 at 11:56 AM Pierre Villard
wrote:
>
> +1, binding
>
> Verified signatures, built and deployed a secured cluster on GCP, ran
Hiya!
LarsF brought this up in the apache-hbase slack account and it caught my
eye. Sending a note here since the PR is closed where this was being
discussed before[1].
I understand Bryan's concerns that misconfiguration of an HBase
processor with a high number of retries and back-off can cr
+1 (non-binding)
-Ran full build
-Created 10-node cluster on Azure, deployed flow.
-Verified basic functionality
Looks good. Thanks!
On Tue, Feb 18, 2020 at 10:02 AM Bryan Bende wrote:
> +1 (binding)
>
> - Verified signatures/hashes & LICENSES/NOTICES
> - Ran full build
> - Ran secure cluster
Hi Josh,
The problem isn't so much about the retries within the flow, its more
about setting up the service for the first time.
A common scenario for users was the following:
- Create a new HBase client service
- Enter some config that wasn't quite correct, possibly hostnames that
weren't reacha
Bryan,
I didn't follow the whole discussion so I apologize if I'm saying something
stupid here. Now that we have the possibility to terminate threads in a
processor, would that solve the issue?
Pierre
Le mar. 18 févr. 2020 à 10:52, Bryan Bende a écrit :
> Hi Josh,
>
> The problem isn't so much
+1 (binding) ran through release helper and various flows. Thanks Joe
for RM'ing!
On Fri, Feb 14, 2020 at 10:15 PM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.11.2.
>
> The source zip, including signatures, digests, etc. can be fou
That could make it a little better, but I can't remember, can we
terminate on a controller service?
The issue here would be on first time enabling the the HBase client
service, so before even getting to a processor.
On Tue, Feb 18, 2020 at 2:00 PM Pierre Villard
wrote:
>
> Bryan,
>
> I didn't fo
Good point, I don't think we can do that on a controller service.
Le mar. 18 févr. 2020 à 11:06, Bryan Bende a écrit :
> That could make it a little better, but I can't remember, can we
> terminate on a controller service?
>
> The issue here would be on first time enabling the the HBase client
>
Hi Team,
I'm working with NiFi Registry, NiFi 1.9.2. I have connected the registry
to my github repository. I am able to push the changes into the repo but
I'm not able to change the version of the flow and see local changes. I
receive Internal 500 error whenever performing these operations.
I'm
+1 (binding)
- Check signatures and hashes
- Full build
- Verified some of the JIRAs addressed in this release
Thanks for RMing Joe!
On Tue, Feb 18, 2020 at 2:01 PM Matt Burgess wrote:
> +1 (binding) ran through release helper and various flows. Thanks Joe
> for RM'ing!
>
> On Fri, Feb 14, 202
There is a good chance it is related to Windows which is not currently
supported [1].
Can you trying running on a unix-based environment?
[1]
https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#system-requirements
On Tue, Feb 18, 2020 at 2:28 PM Ashutosh Vaish
wrote:
+1 (non-binding)
* verified sigs and hashes
* full build on java 11
* tested a few processors, basic functionality.
Thanks for RM'ing, Joe!
On Tue, Feb 18, 2020 at 2:31 PM Matt Gilman wrote:
> +1 (binding)
>
> - Check signatures and hashes
> - Full build
> - Verified some of the JIRAs addres
Hi,
Josh, thanks for bringing it up here again.
I'm happy to revive the PR with whatever the outcome of this thread is.
It came up today because another client complained about how "unstable"
HBase is on NiFi.
@Josh: As the whole issue is only the initial connect can we have a
different timeout s
Second email
-- Forwarded message -
From: Glenn Barnard
Date: Sat, Feb 15, 2020 at 7:17 AM
Subject: NIFI Flow Design System
To:
Hi, I recently had the pleasure of using NIFI at DXC Technology and was
wondering if the FDS component was available to use in my own applications
I will email glenn directly as i dont think he is on the list...
On Tue, Feb 18, 2020 at 4:27 PM Glenn Barnard
wrote:
> Second email
>
> -- Forwarded message -
> From: Glenn Barnard
> Date: Sat, Feb 15, 2020 at 7:17 AM
> Subject: NIFI Flow Design System
> To:
>
>
> Hi, I re
+1 (non-binding)
Verified checksums, signatures, and commit hash
Ran build and all tests on OpenJDK 1.8.0_242 on Linux and OS X
Created small cluster and ran some flows including load balancing
On Feb 18, 2020, 12:28 PM -0800, Robert Fellows , wrote:
+1 (non-binding)
* verified sigs and hashes
* f
+1 (non-binding)
Verified signature, checksum
Built, started.
Created a flow, sent and processed flowfiles via S2S.
On Tue, Feb 18, 2020 at 11:47 PM Joey Frazee
wrote:
> +1 (non-binding)
> Verified checksums, signatures, and commit hash
> Ran build and all tests on OpenJDK 1.8.0_242 on Linux and
We could certainly implement some kind of "sanity check" via HBase code,
but I think the thing that is missing is the logical way to validate
this in NiFi itself.
Something like...
```
Configuration conf = HBaseConfiguration.create();
conf.setInt("hbase.rpc.timeout", 5000);
try (Connection con
29 matches
Mail list logo
