Hi,
HandleHttpResponse is designed to be used in conjunction with
HandleHttpRequest. Based on the description,
it seems like InvokeHTTP’s Response connection has been connected to
HandleHttpResponse, which is not needed
because the output FlowFile on the Response connection already contains the
Hi Sagar,
Can you share more about how your flow is setup?
It sounds like the flow is maybe attempting to send a response to the same
message multiple times,
or the request is timing out while the data is flowing through NiFi.
Thanks
-Mark
> On Aug 10, 2023, at 3:18 PM, Sagar Reddy Poreddy
>
Dear NiFi Team,
Hope you are doing well, I would like report and issue that I am facing
with NiFi HandleHttpResponse. I have an SAP API, I am consuming it via
invokeHttp and connected the response to HandleHttpResponse. When I call
the api for the first time it is giving the correct response (via
Thanks @YolandaMDavis.
Yes. It's fine to apply.
Sarah Olson
m: 415-298-5573
Sent from my iPhone
> On May 3, 2017, at 6:07 AM, YolandaMDavis wrote:
>
> Github user YolandaMDavis commented on the issue:
>
>https://github.com/apache/nifi/pull/1736
>
>@thesolson did the merge but corre
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
This currently has conflicts with master and needs to be rebased before it
can be merged (sorry for taking so long to review the PR).
---
If your project is set up for it, you can reply to this em
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/611
This was merged to `0.x`. I will open a new PR with the changes for
`master`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
@ijokarumawak I believe you're right about it only being Kafka. I looked
through them as well and couldn't find an instance of external state.
While surprised I am definitely happy because
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/608
Looks good @bbende! This has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this f
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/612
+1
Reviewed code, did a contrib check build, created a cluster to demonstrated
the problem and then recreated with the fix and the issue was resolved. Thanks
Mark will merge it in to 0.x a
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/611
Thanks @alopresto! The changes look good. I have verified the changes
locally in a secured cluster.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user moranr commented on the issue:
https://github.com/apache/nifi/pull/604
â**NIFI-2031** looks good
For **NIFI-2036,** NiFi logo seems to sit a little low after the other
toolbar changes. Please *change* `margin:0 20px 0 15px;` *to* `margin:0 20px
3px 15px;`
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/610
Looks good @markap14! This has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/611
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user moranr commented on the issue:
https://github.com/apache/nifi/pull/604
**NIFI-2144** looks good â seeing the correct icons in place.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not h
Github user moranr commented on the issue:
https://github.com/apache/nifi/pull/604
For **NIFI-2038**
* For #header .component-button, height and width properties are declared
twice at 40px and 56px. Should only be 56px
* Icons (#header .icon and #header .fa) should be 32px (â
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/610
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/591
Closing this and resubmitting against master since 0.7 is frozen.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does no
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/576
+1
Did a contrib check build, reviewed the code and comments were addressed,
and did a functional test using vanilla ES as well as one secured with Shield.
Thanks for the contribution @matt
Github user olegz commented on the issue:
https://github.com/apache/nifi/pull/578
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/608
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
Gents,
any further comments? Keen to revisit code if necessary
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/547
thanks @pvillard31
this is indeed unfortunate but I assume it is the only way of getting
around the breaking changes introduced as part of 2.7...
---
If your project is set up for it, you ca
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/594
Thanks @scottyaslan! This has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/475
Noticed that Apache Zeppelin also use similar profiles:
https://github.com/apache/zeppelin/blob/e0f77d68e813c61d083988e3e167693016418bda/spark-dependencies/pom.xml#L709
---
If your project i
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/502
Hey @mans2singh, I'm really busy this week and I won't be able to have a
look before next week :(
In the meantime, you can fix the conflicts against master. And maybe @apiri
will have a chance t
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/563
@JPercivall Thanks for your time to review.
I've looked at every existing Processors, Reporting tasks, and Controller
services, but couldn't find other component needing external state man
Github user mans2singh commented on the issue:
https://github.com/apache/nifi/pull/502
Hey @pvillard31 @aldrin - Just wanted to check if you have any
suggestions/recommendations for this pull request.
Thanks
---
If your project is set up for it, you can reply to this email and ha
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/601
+1 LGTM, ran all tests and manually verified error messages, etc. Merging
into master, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/601
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if th
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
+1 LGTM, merging to master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishe
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/563
Starting to review.
Unless if I'm missing something, why is external state only added for
GetKafka and ConsumeKafka? Aren't there many other processors that manage state
externally?
---
I
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
Ok sounds good. I gave the Integration Test thing (and the QueryCassandra
-- actually in AbstractCassandraProcessor) fix a try, the ITs don't work (yet)
but feel free to take a look:
https://github.
Github user jeffoxenberg commented on the issue:
https://github.com/apache/nifi/pull/602
Squashed my commits. I'll look into integration testing as well. I'll try
to handle the QueryCassandra one separately as I'll be busy for the next fewof
days with other things.
---
If your pro
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
@jeffoxenberg After your fix is applied, I tried a QueryCassandra to get
the values out of the table, and I'm getting a similar codec error then. Should
we edit the Jira to fix both cases, or do you
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
@jeffoxenberg mind squashing your commits into one? Please and thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
You're right, we'd need some integration tests (possibly using
CassandraUnit) to show this. I will verify your change then merge as-is, we can
add an improvement Jira or something to add integration
Github user jeffoxenberg commented on the issue:
https://github.com/apache/nifi/pull/602
Is the test suite actually creating a cassandra instance, creating a table,
and executing the generated cql against it? I did some testing and was able to
get the original code to insert by chang
Github user jeffoxenberg commented on the issue:
https://github.com/apache/nifi/pull/602
Thanks for working with me on this.
The real flow's value was double quoted, it was parsed from JSON.
[Here's](https://gist.github.com/jeffoxenberg/6f12bb11b7359e10180712500cb528e7)
the
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
Can you put your template in a Gist? I'll give it a try too
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not ha
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
Were there quotes (single or double) in the real flow's value?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
I cherry-picked in the commits that added unit tests, to show that they
would fail without your fix, however they pass. Any idea how the tests differ
from the error that spawned the Jira?
---
If yo
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
I also added Apache Commons Email to NOTICE
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
en
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
@joewitt According to to
https://mvnrepository.com/artifact/org.subethamail/subethasmtp/3.1.7
The only dependencies should be
 subethasmtp
The following NOTICE information applies:
Github user jeffoxenberg commented on the issue:
https://github.com/apache/nifi/pull/602
Thanks. I think I got it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wi
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
An example could be another test just like that one with cql.args.10.value
set to "I'm not a timestamp" or a timestamp not in ISO-8601 format like
"07.01.2016". Not saying the operation should succee
Github user jeffoxenberg commented on the issue:
https://github.com/apache/nifi/pull/602
No problem. I think I added a test for a good value here:
`https://github.com/jeffoxenberg/nifi/commit/335e4f08a60989909d2d152f426fa5d46dec9a1b`.
Could you give me an example of writing a
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/603
@mcgilman excellent - all looks good, as far as I can tell. This PR
addresses several issues that existed in the application. I've pushed to master.
---
If your project is set up for it, you can repl
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/602
Looks good, mind adding unit test(s) to try various good and bad values?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your projec
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/593
@mcgilman good call. Looks good to me!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enable
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/593
@markap14 Looks great! I made one additional change to populate snippet
results off of the actual components instead of just the snippet contents
(since the contents are now pruned).
https:/
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/576
It would be nice to have integration tests similar to those in the original
Fetch/PutElasticSearch processors.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
@ijokarumawak thanks for the gist.
Interesting that junit missed that and I incorrectly assumed the change in
structure had not lead to side effects. Feedback was much appreciated and
unless
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/483
@trixpan Thanks for addressing comments promptly! I confirmed that all of
my comments are addressed. However the modification on ExtractEmailHeader.java
didn't work with following error:
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/593
@mcgilman good call! I also found a few more things for these components
that we don't need. I have pushed a new commit so that you can look at it and
make sure that the changes all make sense to you,
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/595
This PR appears to be a collection of merge commits, were you trying to
issue a PR with new code against the master branch? If so can you point me at
the commit, I can help get the PR into the correc
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/593
Just glancing through an old template and looks like we should also be
scrubbing the following...
- Process Group
-- activeRemotePortCount, disabledCount, inactiveRemotePortCount,
inputPo
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/592
Looks great @markap14! This has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have thi
Github user atilcock commented on the issue:
https://github.com/apache/nifi/pull/500
Have rebuilt on base master branch - currently running tests - hope to
resubmit in the next day or so.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/525
+1
Did a contrib check build, reviewed the code and any comments were
addressed. To test I ran three ConsumeWindowsEventLog processors following
multiple Windows channels and did a query to
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/593
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/592
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/591
@mattyb149 I think for that it has to be part of the stylesheet and not the
processor, so we'd end up just changing that aspect of the test then.
---
If your project is set up for it, you can reply to
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/591
I found this, could it be a property of the dialog?
http://www.saxonica.com/documentation9.5/extensions/output-extras/indent-spaces.html
---
If your project is set up for it, you can reply to this
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/590
Thanks @bbende! This has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/589
This has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and w
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/589
@jtstorck looks good. However, I noticed that the revision version was
being necessarily checked. Those are already verified in the Tenant and
AccessPolicy resource. Also, I updated the error message
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/590
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/588
Looks good @bbende! This has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this f
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/588
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/577
Thanks @scottyaslan! This has been merged into master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have thi
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/502
Hi @mans2singh, I didn't find time to give it a new try, but I hope I will
this week.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/564
@davetorok here is the first phase of custom transform support (supporting
the transform interface)
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/500
Also it looks like like you've got a merge commit in your chain here. Can
you start with a fresh master branch, apply your patch, then push the pull
request? If you have two commits, perhaps you coul
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/500
The file "NIFI-1922-patch" is included in this commit and should not be,
just the changes it implies (which have been applied). Can you remove this file
from the commit? Please and thanks!
---
If y
Github user mans2singh commented on the issue:
https://github.com/apache/nifi/pull/502
Hi @pvillard31 @apiri - Just wanted to see if you have any
thoughts/recommendations for me.
Also, @pvillard31 were you able to run the integration tests and validate
that the entries were save
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/576
Per an offline discussion with @JPercivall, Multi-Get and/or Search
capabilities are not really right for the FetchXYZ processor idiom. A better
solution may be a List/Search/Execute processor for El
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/576
Yep will do!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if th
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/576
There have already been comments asking for a multi-get function for
ElasticSearch[1] could this be added to FetchElasticSearchHTTP now and be added
as a new feature to PutElasticSearch later (Creat
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/483
@trixpan Thanks for your effort to creating these Processors! I was able to
setup a data flow that can receive emails using Listen SMTP easily and extract
headers and attachments. All unit tests p
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/586
+1 LGTM, merged to 0.x and master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled an
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/582
I've merged this to master. Looks good @jtstorck!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fea
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/582
Looks good so far. Though I think we should probably fail faster when
receiving an unsecure web request. I've filed another JIRA for this work [1].
[1] https://issues.apache.org/jira/browse/NI
Github user vcharmcaster commented on the issue:
https://github.com/apache/nifi/pull/584
HI Joe,
I am newbie, made some changes which will improve performance. There is no
PR associated with NiFi, Let me know how to create one?
usually it is good practice to close input st
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
@joewitt no worries. Hard to be a high-tech celebrity! :-)
@bbende @mattyb149 - would one of you gentlemen be able to review? Keen to
get this sorted so I can continue my list (yeah, I am sort
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/581
Looks good @bbende! Merged into master. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/582
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/584
Hello
Is this PR associated with an Apache NiFi JIRA? If not can you please
create one. Also, we'll want to update the commit message to reference that
JIRA as well. You can see some of the
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/483
@trixpan i haven't been able to dive into the details of the pr to have
more comments just yet. Hopefully others can engage as well.
---
If your project is set up for it, you can reply to this email
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/483
ListenSMTP has been added to package. PR now includes the full suite:
* ListenSMTP (self explanatory)
* ExtractEmailHeaders (convert an eml into attributes)
* ExtractEmailAttachments (co
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/583
Here's what the result looks like while the details section is expanded. I
plead guilty to being a bad UI designer, any tips would be appreciated.
to setup te
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/573
+1
Fixes errors seen on Windows, code looks good and passes contrib-check.
Thanks Mark
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
1 - 100 of 528 matches
Mail list logo
