thanks Mark, but it did not help. other 3 consumer IDs are still not
pulling messages from topics, only the very first one.
But if I set up 9 different NiFi Kafka Consumer processor and each of them
listen to a single topic, all 9 work in parallel, initiating 9 different
consumer IDs (but the
Running 1.8 so I see MergeRecord. I think I need to use JSONTreeReader as the
reader, but it requires a schema. I don't have a schema for the JSON;
wondering why I can't just take the JSON I'm already receiving and not pretty
print it - squash it to one line? I'm new to NiFI so please pardon
Boris,
On the Settings tab, have you changed the value of the "Yield Duration"? The
default, I believe, is 1 second.
I would recommend that you change that to "0 sec" and that may do the trick.
Thanks
-Mark
On Jan 24, 2019, at 3:30 PM, Boris Tyukin
mailto:bo...@boristyukin.com>> wrote:
any
Mike,
We are using MongoDB 3.4.7 and Apache NiFi 1.8.0
Regards,
Dnyaneshwar Pawar
From: Mike Thomsen
Sent: Thursday, January 24, 2019 8:44 PM
To: users@nifi.apache.org
Subject: Re: GetMongo failure routing issue.
What version are you using?
On Thu, Jan 24, 2019 at 8:23 AM Dnyaneshwar
Hi All,
We are currently in the process of upgrading from NiFi 1.5 to 1.8. After
making the binary changes and restarting the cluster (a secure cluster
setup), we are getting the following error:
ERROR [main] org.apache.nifi.encrypt.StringEncryptor * A blank sensitive
properties key was
What version are you using?
On Thu, Jan 24, 2019 at 8:23 AM Dnyaneshwar Pawar <
dnyaneshwar_pa...@persistent.com> wrote:
> Hi All,
>
> We are working with MongoDB integration with NiFi (Version 1.8). And we
> observed one issue related to failure case. Whenever, GetMongo processes
> the
Hi All,
We are working with MongoDB integration with NiFi (Version 1.8). And we
observed one issue related to failure case. Whenever, GetMongo processes the
incorrect query (for example. Invalid json), the bulletin gets updated with
appropriate error message, however, the flow stuck, instead
Hi Joe,
Thanks for the reply. Agreed on the secure setup and we will definitely
look to add value(s) for these properties. The issue we hit was that we
weren't able to access the UI, and I was thinking that this error was
preventing this. You think that this error shouldn't block accessing the
Ryan,
That block of text that shows up in the log could arguably said "WARN"
because the flow will continue to function as it did before.
However, the reason it is an error is that you really should follow its
advice and specifically follow the secure nifi configuration guidance.
By not
ryan
right...i think you are facing something else. We have locked down on some
headers, etc.. They are mentioned in the migration guide.
Can you share the logs from a full startup run?
thanks
On Thu, Jan 24, 2019, 11:21 AM Ryan H Hi Joe,
>
> Thanks for the reply. Agreed on the secure setup
Hi guys
We need your advice,… we use the ListSFTP processor to read files on a remote
folder. The files gets written like that:
* File1
* File2
* File3 (at the time of “ls” command this file is growing, we don’t know
how big it gets or when writing is finished)
So the application
hey josef. yeah we need to add a min file age property to ListSftp.
please file a jira.
thanks
On Thu, Jan 24, 2019, 11:13 AM Hi guys
>
>
>
> We need your advice,… we use the ListSFTP processor to read files on a
> remote folder. The files gets written like that:
>
>
>
>- File1
>-
Ryan,
I added that warning [1], and Joe’s right, it should have been at a WARN
severity. However, it definitely isn’t blocking the access to the canvas
(intentionally). Like Joe said, if you can provide a full stacktrace, and
possibly your config files (redacting sensitive information as
Hi Joe,
Yes here are the only logs that I am seeing here as of now (I will probably
turn on DEBUG levels to get more):
***nifi-app.log***
2019-01-24 17:32:51,583 ERROR [main]
org.apache.nifi.encrypt.StringEncryptor
Ryan,
Got ya ... so bootstrap log seems to indicate badness. Can you please
share more of the nifi-app.log as there will almost certainly be a smoking
gun in there. You shouldn't have to enable to any special logging to see
what keeps it from starting.
Thanks
On Thu, Jan 24, 2019 at 12:38 PM
I'm ingesting Windows Event logs with ConsumeWIndowsEventLog and then using
TransformXML according to:
https://community.hortonworks.com/articles/29474/nifi-converting-xml-to-json.html
To make them JSON. The flow continues to MergeContent, CompressContent and
then PutS3Object.
The issue I'm
Michael,
As of NiFi 1.7.0, if you use MergeRecord instead of MergeContent, you
can choose a JsonRecordSetWriter with "Pretty Print JSON" set to false
and "Output Grouping" set to "One Line Per Object", that should output
one JSON per line (as well as merge individual flow files/records
together).
Hi Andy,
Thanks for the response. We had our log levels set to ERROR, so the real
issue was flushed out once I brought the log levels down to INFO instead to
debug. One thing that kind of puzzles me is that the item that caused the
web server to not start came thru as WARN messages instead of
18 matches
Mail list logo
