I was thinking about that, but is that generally safe? Are there are any
known gotchas with mixing the two in the same field?
On Fri, Jul 26, 2019 at 6:52 PM Bryan Bende wrote:
> I know this doesn’t really answer the question, but in most cases couldn’t
> you use EL ${now()} in the record path
I know this doesn’t really answer the question, but in most cases couldn’t
you use EL ${now()} in the record path statement and it would get evaluated
before the record path?
On Fri, Jul 26, 2019 at 6:42 PM Mike Thomsen wrote:
> I tried to creating a simple now() timestamp function and got
I tried to creating a simple now() timestamp function and got this:
org.apache.nifi.record.path.exception.RecordPathException:
org.antlr.runtime.tree.RewriteEmptyStreamException: rule optionalArgument
at org.apache.nifi.record.path.RecordPath.compile(RecordPath.java:105)
at
Please send the instructions to be removed from this alias.
Zaminah D Williams
Onyx Consulting Services, LLC
President/CEO
(410) 814-7651 (o)
(301) 467-6680 (c)
From: scottyas...@apache.org
Sent: Friday, July 26, 2019 4:22:04 PM
To: comm...@nifi.apache.org
Apache NiFi Community,
I am pleased to announce that including my +1 (binding) vote the 0.2.0
release of Apache NiFi Flow Design System passes with
4 +1 (binding) votes
4 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the
Thanks for sharing your thoughts, Raymond.
Some of the items you call out have tickets already or there may be
similar/related ones. I will plan to go through each and reply back with my
findings.
Thanks again!
On Fri, Jul 26, 2019 at 9:46 AM ski n wrote:
> I was creating a flow and I noticed
+1 Release this package as nifi-fds-0.2.0
Thanks for putting this together, Scott!
On Fri, Jul 26, 2019 at 2:10 PM Joe Witt wrote:
> +1 (binding)
>
> Full clean build following readme and testapp check out. L looks good.
> Sigs/Commit checks out.
>
> I would recommend ditching the sha1 entry.
+1 (binding)
Full clean build following readme and testapp check out. L looks good.
Sigs/Commit checks out.
I would recommend ditching the sha1 entry. 256 and 512 are good.
Thanks
On Fri, Jul 26, 2019 at 1:33 PM Marc Parisi wrote:
> +1 (binding). I built and tested according to the release
+1 (binding). I built and tested according to the release helper guide.
Demo app, hashes, readmes, and notices all look good.
Thanks Scott!
On Fri, Jul 26, 2019 at 10:09 AM Matt Gilman
wrote:
> +1 (binding) Release this package as nifi-fds-0.2.0
>
> Ran through release helper. Checked out demo
I was creating a flow and I noticed some things of the GUI that were
missing. Don’t know if there already plans/tickets for these items, but I
would like your opinion first.
If you think it’s a good idea and there is no ticket yet than I will create
one:
1) It’s already possible to align
10 matches
Mail list logo
