[
https://issues.apache.org/jira/browse/NIFI-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-3988:
Resolution: Fixed
Fix Version/s: 1.9.0
Status: Resolved (was: Patch Available)
>
asfgit closed pull request #3217: NIFI-3988: Add fragment attributes to
SplitRecord
URL: https://github.com/apache/nifi/pull/3217
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a
[
https://issues.apache.org/jira/browse/NIFI-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723741#comment-16723741
]
ASF subversion and git services commented on NIFI-3988:
---
Commit
ijokarumawak commented on issue #3217: NIFI-3988: Add fragment attributes to
SplitRecord
URL: https://github.com/apache/nifi/pull/3217#issuecomment-448107698
LGTM +1, merging. Thanks @mattyb149!
This is an automated message
[
https://issues.apache.org/jira/browse/NIFI-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-5905:
Status: Patch Available (was: In Progress)
> Secure S2S fails with NullPointerException
>
[
https://issues.apache.org/jira/browse/NIFI-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723732#comment-16723732
]
Koji Kawamura commented on NIFI-5892:
-
I think all Wait related attributes should be cleared to
ijokarumawak opened a new pull request #3225: NIFI-5905 Secure S2S fails with
NullPointerException
URL: https://github.com/apache/nifi/pull/3225
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the
[
https://issues.apache.org/jira/browse/NIFI-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto reassigned NIFI-5462:
---
Assignee: Andy LoPresto
> Refactor TLS Toolkit
>
>
>
[
https://issues.apache.org/jira/browse/NIFI-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto reassigned NIFI-5459:
---
Assignee: Andy LoPresto
> Integrate TLS Toolkit with external CA / certificate providers
>
Koji Kawamura created NIFI-5905:
---
Summary: Secure S2S fails with NullPointerException
Key: NIFI-5905
URL: https://issues.apache.org/jira/browse/NIFI-5905
Project: Apache NiFi
Issue Type: Bug
[
https://issues.apache.org/jira/browse/NIFI-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723433#comment-16723433
]
ASF subversion and git services commented on NIFI-5748:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-5748:
--
Resolution: Done
Fix Version/s: 1.9.0
Status: Resolved (was: Patch Available)
>
kevdoran closed pull request #3129: NIFI-5748 Fixed proxy header support to use
X-Forwarded-Host instead …
URL: https://github.com/apache/nifi/pull/3129
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
kevdoran commented on issue #3129: NIFI-5748 Fixed proxy header support to use
X-Forwarded-Host instead …
URL: https://github.com/apache/nifi/pull/3129#issuecomment-448018035
Thanks for the help reviewing, @thenatog. Merging to master shortly,
@jtstorck.
thenatog edited a comment on issue #3129: NIFI-5748 Fixed proxy header support
to use X-Forwarded-Host instead …
URL: https://github.com/apache/nifi/pull/3129#issuecomment-447981679
Thanks for the docker setup for the proxies, made things easy. I reviewed
this from a security perspective
thenatog commented on issue #3129: NIFI-5748 Fixed proxy header support to use
X-Forwarded-Host instead …
URL: https://github.com/apache/nifi/pull/3129#issuecomment-447981679
Thanks for the docker setup for the proxies, made things easy. I reviewed
this from a security perspective and it
[
https://issues.apache.org/jira/browse/NIFI-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723296#comment-16723296
]
ASF subversion and git services commented on NIFI-5898:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723298#comment-16723298
]
ASF subversion and git services commented on NIFI-5898:
---
Commit
[
https://issues.apache.org/jira/browse/NIFI-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto resolved NIFI-5898.
-
Resolution: Fixed
Fix Version/s: 1.9.0
> Update the display name of AWS bundle's
[
https://issues.apache.org/jira/browse/NIFI-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723297#comment-16723297
]
ASF subversion and git services commented on NIFI-5898:
---
Commit
alopresto closed pull request #3220: NIFI-5898: Updated the display name for
ACCESS_KEY & SECRET_KEY
URL: https://github.com/apache/nifi/pull/3220
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
alopresto commented on issue #3220: NIFI-5898: Updated the display name for
ACCESS_KEY & SECRET_KEY
URL: https://github.com/apache/nifi/pull/3220#issuecomment-447971672
+1, merging.
This is an automated message from the
alopresto commented on issue #3220: NIFI-5898: Updated the display name for
ACCESS_KEY & SECRET_KEY
URL: https://github.com/apache/nifi/pull/3220#issuecomment-447971302
Reviewing...
This is an automated message from the
[
https://issues.apache.org/jira/browse/NIFI-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-5904:
---
Status: Patch Available (was: In Progress)
> PutHive3Streaming incorrectly handles
mattyb149 opened a new pull request #3224: NIFI-5904: Fix PutHive3Streaming
handling of RecordReaderFactoryException
URL: https://github.com/apache/nifi/pull/3224
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
Matt Burgess created NIFI-5904:
--
Summary: PutHive3Streaming incorrectly handles
RecordReaderFactoryException
Key: NIFI-5904
URL: https://issues.apache.org/jira/browse/NIFI-5904
Project: Apache NiFi
[
https://issues.apache.org/jira/browse/NIFI-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess reassigned NIFI-5904:
--
Assignee: Matt Burgess
> PutHive3Streaming incorrectly handles RecordReaderFactoryException
>
ottobackwards commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447954938
I mean can the JsonSurfer replace the Jayway in that class?
This is an
Mr TheSegfault created MINIFICPP-697:
Summary: Same named AST levels are collapse in c2 response
Key: MINIFICPP-697
URL: https://issues.apache.org/jira/browse/MINIFICPP-697
Project: NiFi MiNiFi
MikeThomsen commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447923122
I don't think there is because the Jayway jsonpath library reads the entire
InputStream into memory before doing anything with it. JsonSurfer uses
ottobackwards commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447903523
Have you looked at changing the jsonpath record reader to use jsonSurfer?
is there a backwards compatible way to switch to the iterator?
MikeThomsen commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447902019
@markap14 I can rename it to `StreamingJsonPathReader`. Does that work?
This is
[
https://issues.apache.org/jira/browse/NIFI-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-5903:
-
Status: Patch Available (was: Open)
> Allow RecordPath to be used in order to access nested fields
markap14 opened a new pull request #3223: NIFI-5903: Allow RecordPath to be
used in QueryRecord processor. Also…
URL: https://github.com/apache/nifi/pull/3223
… some code cleanup and improvements to the docs
Thank you for submitting a contribution to Apache NiFi.
In order to
Mark Payne created NIFI-5903:
Summary: Allow RecordPath to be used in order to access nested
fields within QueryRecord
Key: NIFI-5903
URL: https://issues.apache.org/jira/browse/NIFI-5903
Project: Apache
[
https://issues.apache.org/jira/browse/NIFI-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-5903:
-
Description:
QueryRecord is an immensely powerful tool when evaluating "flat" data such as
CSV or
ottobackwards commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447894213
@markap14 agreed, also, this reader, as @MikeThomsen points out has a
somewhat specialized use case, and cases where you wouldn't want to use
markap14 commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447893564
I do agree that we should refactor such that we don't have so much
duplication in the conversion from JsonNode to Record. I also think that we
need
MikeThomsen commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447891669
I was vaguely tracking the SplitJson issue, so I knew about the issue before
even starting on the work.
ottobackwards commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447890661
Maybe you can open a ticket for the Jackson upgrade
This is an automated
ottobackwards commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447890460
@MikeThomsen what reader were you using when you had the issue?
This is an
MikeThomsen commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447889903
@ottobackwards we definitely should refactor the readers at some point to
use common code. Problem I ran into is that the existing ones are using
ottobackwards commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447889274
This also feels like we are sticking our fingers in the dyke a little.
The SplitJSON processor -> has this issue
The JsonPathReader ->
ottobackwards edited a comment on issue #3222: NIFI-5900 Added
StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447888589
So, the issue is the jsonPath, not the tree node reader. As we have
discussed in NIFI-3126. I didn't do the POC on jsonSurfer because
ottobackwards commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447888589
So, the issue is the jsonPath, not the tree node reader. As we have
discussed in NIFI-3126. I didn't do the POC on jsonSurfer because the work
bbende commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447880006
Thanks for clarifying, I originally missed how json path was being used here
and I can now see how this is different. Both of the existing json readers
MikeThomsen commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447879070
> @MikeThomsen are you saying that your 25GB JSON file got an OOM (or some
error) when using ConvertRecord with JsonTreeReader?
Yeah, in
MikeThomsen edited a comment on issue #3222: NIFI-5900 Added
StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447875162
> I don't see how you avoid reading that all into memory because you have to
return a Record instance from the reader with all that data
MikeThomsen commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447875162
> I don't see how you avoid reading that all into memory because you have to
return a Record instance from the reader with all that data in it.
[
https://issues.apache.org/jira/browse/NIFIREG-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran resolved NIFIREG-215.
-
Resolution: Done
> Extension Bundle Improvements
> -
>
>
[
https://issues.apache.org/jira/browse/NIFIREG-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723034#comment-16723034
]
Bryan Bende commented on NIFIREG-218:
-
Meant to say that the only thing I can really think of that
[
https://issues.apache.org/jira/browse/NIFI-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723028#comment-16723028
]
Mike Thomsen commented on NIFI-5901:
Whoever decides to take this on should refer to this conversation
[
https://issues.apache.org/jira/browse/NIFIREG-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723030#comment-16723030
]
Bryan Bende commented on NIFIREG-218:
-
[~jgondron] thanks for the thorough explanation of the issue!
Mike Thomsen created NIFI-5902:
--
Summary: Create record-aware geo enrichment processor
Key: NIFI-5902
URL: https://issues.apache.org/jira/browse/NIFI-5902
Project: Apache NiFi
Issue Type: New
Flo Rance created NIFI-5901:
---
Summary: Write JSON record in database
Key: NIFI-5901
URL: https://issues.apache.org/jira/browse/NIFI-5901
Project: Apache NiFi
Issue Type: Improvement
Affects
bbende commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447864722
@MikeThomsen are you saying that your 25GB JSON file got an OOM (or some
error) when using ConvertRecord with JsonTreeReader?
I'm curious since
[
https://issues.apache.org/jira/browse/NIFI-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flo Rance updated NIFI-5901:
Description:
It would be good to be able to store a whole json record in databases that
implement it (e.g.
[
https://issues.apache.org/jira/browse/NIFI-5876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan-Henrik Preuss updated NIFI-5876:
Status: Reopened (was: Closed)
> PutHDFS executes with SUCESS, although exception in logs
[
https://issues.apache.org/jira/browse/MINIFICPP-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mr TheSegfault reopened MINIFICPP-695:
--
I pre-maturely closed the ticket.
> NanoFi Examples appear to be broken
>
MikeThomsen commented on issue #3222: NIFI-5900 Added StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222#issuecomment-447833164
@markap14 @mattyb149 @ijokarumawak @zenfenan @ottobackwards
We got a file format that looks roughly like this:
```
{
MikeThomsen opened a new pull request #3222: NIFI-5900 Added
StreamingJsonReader.
URL: https://github.com/apache/nifi/pull/3222
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps
Mike Thomsen created NIFI-5900:
--
Summary: Add Streaming JsonPath Record Reader
Key: NIFI-5900
URL: https://issues.apache.org/jira/browse/NIFI-5900
Project: Apache NiFi
Issue Type: New Feature
pvillard31 commented on issue #3218: NIFI-5895 - Add a processor to start an
Oozie workflow
URL: https://github.com/apache/nifi/pull/3218#issuecomment-447792110
Thanks for the review @zenfenan - just pushed a commit to address your
comments.
63 matches
Mail list logo
