The only other thing I can think of off the top of my head is that the userID
specification may have changed with the BouncyCastle upgrade and the provided
userID of just an email may be incomplete? In my testing, I had to specify the
"name", "description", and "email" fields from the key in the
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/308
NIFI-1684-B fixed ZKClient connection leak
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi tmp
Alternatively you can review and apply th
Forgot to mention you’ll want to change the input/output directories in the
GetFile and PutFile processors, as well as the paths to the public and secret
keyring, the user ID, and the password for the EncryptContent processors.
Andy LoPresto
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5
Hi Alan,
I have created a template [1] which should be able to test the issue you are
encountering. It works for me (Mac OS X 10.11, NiFi 0.6.0-SNAPSHOT, gpg
2.0.28), so I am hoping you can run it on your installation and verify. I
understand you are running NiFi 0.5.1, but to my knowledge, not
Github user steveyh25 commented on the pull request:
https://github.com/apache/nifi/pull/305#issuecomment-202630454
@olegz,
Please see latest commit. The try-catch block has been removed and I've
changed the validation slightly like was spoken about. It appears as though we
d
Hi Alan,
I am investigating this issue (spinning up an instance, setting up a flow that
involves PGP encryption and decryption, etc.) to verify.
As an aside, the setting for “Key Derivation Function” is irrelevant if
“Encryption Algorithm” is set to “PGP” or “PGP_ASCII_ARMOR”. The KDF is
requi
Oleg, I’m almost positive that this is a concurrency issue. When I dialed the
number of concurrent tasks in PutKafka up from 1 to 5 is when it started. I
didn’t realize this until I dialed it back to 1 to make debugging with the IDE
easier. When I did that the problem went away. When I crank
Hello,
I had an EncryptContent processor running with PGP public key encryption
when we were running NiFi 0.4.x.
We recently went up to a 0.5.x, which includes NIFI-1257 and NIFI-1259. Now
my EncryptContent processors are failing to validate my key with an error
message:
'Public Keyring File' is
Also, keep in mind that our RoundRobin will calculate the partition based on
how many partitions available using the following code:
int partSize = this.producer.partitionsFor(topicName).size(); //(this.producer
being KafkaProducer)
However, inside of Kafka internal Partitioner there is this co
Need more information. It’s quite unfortunate that it all manifests itself
through NiFi, but the real issue is with Kafka API and specifically this line
in KafkaProducer
int partition = partitioner.partition(serializedRecord, metadata.fetch());
It uses some internal partitioner
if (record.p
I’m running off of the HEAD of master (or at least close to it - e4b7e4.) It
looks like the processor has lost its mind with the respect to the number of
partitions.
Granted my cluster has been in rough shape mostly through my own abuse and I
probably caused the problem myself.
Has anyone seen
Github user mans2singh commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r57593798
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/PutDynamoDB.java
---
@@ -0,0 +1,182 @@
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/307
NIFI-1691: Add Fetch Size property to QueryDatabaseTable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi querydb-fetchsize
Alter
It was shown that the PMC vote thread in the original email was incorrectly
applied above was to the prior RC1 vote process and not the RC2 vote which
is available at:
http://mail-archives.apache.org/mod_mbox/nifi-dev/201603.mbox/%3CCADT6bVsrP+EYBdSpn2LhR=+zo9h3jvy7haukts5zy0cysos...@mail.gmail.com
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/306#issuecomment-202419168
@ToivoAdams very cool that you're tackling this! Thanks for jumping in! The
only concern that I have with this patch is that if we end up with a buggy
processor that star
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/305#issuecomment-202407396
@trkurc yep, that's the plan once we figure it out
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pr
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/305#issuecomment-202406795
@olegz - if you work out the intellij problems, try to ensure what the fix
was is memorialized on the wiki or dev list
---
If your project is set up for it, you can reply
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/305#discussion_r57563219
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/PublishAMQP.java
---
@@ -195,29 +193,85 @@ public
18 matches
Mail list logo
