Thank you, Aldrin, that seems to have worked.
On Thu, Oct 26, 2017 at 9:12 PM, Aldrin Piri wrote:
> Hi James,
>
> You should be good to go now. Please let me know if that is not the case.
>
> On Thu, Oct 26, 2017 at 11:51 PM, James Wing wrote:
>
> > May
Hi James,
You should be good to go now. Please let me know if that is not the case.
On Thu, Oct 26, 2017 at 11:51 PM, James Wing wrote:
> May I please have edit access to the Confluence Wiki?
>
> Thanks,
>
> James
>
May I please have edit access to the Confluence Wiki?
Thanks,
James
Oops, my bad. In fact, it is the same (ugly, serif) font for the most
part as my usage description.
Thanks; please disregard the question.
On 10/26/2017 10:34 AM, Russell Bateman wrote:
I am experimenting providing "additional details" for my custom
processor. This works as advertised,
I am experimenting providing "additional details" for my custom
processor. This works as advertised, however, the font in which my
details are displayed is manifestly not that of the rest of my usage
which is the same as what NiFi UI uses elsewhere.
What must I add to /additionalDetails.html/
Hi Nifi Dev Team,
We are using Evaluate Json Path Processor to parse an input json and store the
value in a Flow Attribute.
As per the below Nifi Documentation it should work but we are not seeing the
same behavior. The processor returns empty string if its return type is json or
it gives an
Peter,
That was by design. The permissions that are granted were primarily driven
by the existing roles in the 0.x baseline. Provenance permissions were
something that was granted in addition to other roles. However, I do see
that whenever there is an existing flow.xml.gz the initial admin is
Hi Andre,
I don't see any issue but if something goes wrong with a file, this file
won't be listed anymore by ListSFTP. So I guess the "move" strategy is
better suited to remove files already listed by the ListSFTP processor. But
I agree that someone might want to delete the file in the "move"