Raman,
I created a ticket for this issue:
https://issues.apache.org/jira/browse/NIFI-5355.
I read through the links you provided, thanks for researching the problem so
thoroughly.
Found some others as well, such as
https://stackoverflow.com/questions/4391814/why-would-java-awt-image-bufferedim
Hello Everyone,
I am facing another issue. I am fetching some images from source and store
them to destination and just before destination processor I have
ResizeImage Processor.
Now my images can be JPEG or PNG. Processor documentation mentioned that it
can handle both but it is failing for PNG
FYI, JIRA ticket created at
https://issues.apache.org/jira/browse/NIFIREG-182
// Fredrik
On Fri, Jun 29, 2018 at 1:41 PM Bryan Bende wrote:
> I think we need to implement what you described in option #2 which is
> basically like a force push in git terminology.
>
> If you want to create a JIRA
Thanks Andy, my end resolution was to use HAProxy to terminate the SSL
connection. Thanks!
--
Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
I think we need to implement what you described in option #2 which is basically
like a force push in git terminology.
If you want to create a JIRA for that I think it is a good request.
> On Jun 29, 2018, at 6:40 AM, Fredrik Skolmli wrote:
>
> Hi everyone.
>
> I'm not sure if my workflow need
Hi everyone.
I'm not sure if my workflow needs to change using NiFi + NiFi Registry, or
if this is a bug or corner-case.
I do the following:
1) Create a new process group, make the initial flow and start version
control (ver 1)
2) Modify the workflow and commit (ver 2)
3) Realize the most recent
Hi Mark,
I see what you’re saying, but conceptually, it doesn’t seem like a good idea to
me.
From what I can gather, the purpose of Controller Services is to have a shared
component that deals with external special cases (like DB connections).
From my point of view (which is admittedly that of
