when i use replace text i want to use :jsonPath('') funciton for Regular
Expression capturing group; the Replacement Value i set is
"$1:jsonPath('$.data.orgcode')", but it didn't work.
i didn't want to use EvaluateJsonPath , because it couldn't evalue
mulit-line json sting,
+1 (binding)
Build environment: Mac OS X 10.11.6, Java 1.8.0_101, Maven 3.3.9, JCE Unlimited
Strength Cryptographic Jurisdiction Policies installed
* verified GPG signature is valid and SHA512 digest
* verified all checksums
* verified all tests
* verified checkstyle
* verified Knox properties
ben
I think you're right that we should switch and don't think anyone is
actively working it.
Thanks
On Fri, Sep 29, 2017 at 5:58 PM, Benjamin Wood wrote:
> Has anyone looked into this?
> https://issues.apache.org/jira/browse/NIFI-3423
>
> I found a lot of stuff
Has anyone looked into this?
https://issues.apache.org/jira/browse/NIFI-3423
I found a lot of stuff suggesting to replace java.io.File with java.nio.file
Seems like "newDirectoryStream" could achieve what this JIRA is asking.
Here is an example from SO:
+1 (non-binding)
-Ran full clean install on OS X (10.11.4)
-Tested UI changes including Variable Registry UI
-Tested flows using Record reader/writer processors and controller services,
working as expected
> On Sep 29, 2017, at 4:50 PM, Michael Moser wrote:
>
> +1
+1 (non-binding)
Verified source package per release helper.
Built on Ubuntu 14.04, all unit tests and contrib-check pass.
Built on Windows 10, some unit tests fail and contrib-check fails on
"nifi-poi-processors: Too many files with unapproved license" but I
think this was expected. The build
+1 (non-binding) Release this package as nifi-1.4.0
On Fri, Sep 29, 2017 at 11:52 AM, Mark Payne wrote:
> +1 (binding)
>
> Verified hashes and checksum. Built with all unit tests and contrib-check
> on OSX.
>
> Was able to startup and test simple flows worked as expected.
+1 non-binding
-- verified contrib-check
-- ran simple flows with MiNiFi
-- sigs and hashes look good.
Thanks for sending this out Jeff!
On Fri, Sep 29, 2017 at 11:18 AM, Matt Gilman
wrote:
> +1 (binding) Release this package as nifi-1.4.0
>
> On Fri, Sep 29,
+1 (binding) Release this package as nifi-1.4.0
On Fri, Sep 29, 2017 at 11:07 AM, Bryan Bende wrote:
> +1 (binding)
>
> - Ran through the release helper and everything checked out.
> - Ran a couple of sample flows with no issues
>
>
> On Fri, Sep 29, 2017 at 9:46 AM, James
+1 (binding)
- Ran through the release helper and everything checked out.
- Ran a couple of sample flows with no issues
On Fri, Sep 29, 2017 at 9:46 AM, James Wing wrote:
> Jeff, I agree the updated KEYS file has been published. Thanks.
>
> On Fri, Sep 29, 2017 at 6:00 AM,
Jeff, I agree the updated KEYS file has been published. Thanks.
On Fri, Sep 29, 2017 at 6:00 AM, Jeff wrote:
> James,
>
> I had to do a hard reload of the page in Chrome, since the browser kept
> showing me a cached version without my key. After the hard reload, I can
> see
+1, binding
Notes:
* Hashes and signature looked good
* No binaries
* Release matches source commit
* Build with contrib check passes
* Running some simple flows looks good
On Fri, Sep 29, 2017 at 9:00 AM, Jeff wrote:
> James,
>
> I had to do a hard reload of the page in
James,
I had to do a hard reload of the page in Chrome, since the browser kept
showing me a cached version without my key. After the hard reload, I can
see my key at https://dist.apache.org/repos/dist/dev/nifi/KEYS. Could you
try opening the KEYS link in incognito mode and verify that my key is
13 matches
Mail list logo