davyam edited a comment on pull request #3887:
URL: https://github.com/apache/nifi/pull/3887#issuecomment-710739387
Hi @rkarthik29
I am getting the following error:
`org.apache.nifi.processor.exception.ProcessException: cannot attach to
outbound server: nfxout`
Steps that
davyam edited a comment on pull request #3887:
URL: https://github.com/apache/nifi/pull/3887#issuecomment-710739387
Hi @rkarthik29
I am getting the following error:
`org.apache.nifi.processor.exception.ProcessException: cannot attach to
outbound server: nfxout`
Steps that
davyam commented on pull request #3887:
URL: https://github.com/apache/nifi/pull/3887#issuecomment-710739387
Hi @rkarthik29
I am getting the following error:
`org.apache.nifi.processor.exception.ProcessException: cannot attach to
outbound server: nfxout`
Steps that I did:
[
https://issues.apache.org/jira/browse/NIFI-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-7935.
Fix Version/s: 1.13.0
Resolution: Fixed
> Add error reason to failed flowfiles of PutElastics
[
https://issues.apache.org/jira/browse/NIFI-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215683#comment-17215683
]
ASF subversion and git services commented on NIFI-7935:
---
Commit b442
asfgit closed pull request #4608:
URL: https://github.com/apache/nifi/pull/4608
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
MikeThomsen commented on pull request #4570:
URL: https://github.com/apache/nifi/pull/4570#issuecomment-710678688
@jfrazee do you have any time to take another look?
This is an automated message from the Apache Git Service.
T
Adam Turley created NIFI-7936:
-
Summary: PutElasticsearchRecord is unable to write to
elasticsearch over SSL when using nifi with JDK11
Key: NIFI-7936
URL: https://issues.apache.org/jira/browse/NIFI-7936
NissimShiman commented on pull request #4130:
URL: https://github.com/apache/nifi/pull/4130#issuecomment-710258557
Regarding the point @mcgilman makes about what the use case is here that
would make deterministic behavior desirable here, I reached out to @anaylor to
drill down on this. He
[
https://issues.apache.org/jira/browse/NIFI-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215494#comment-17215494
]
Sebastian Valle edited comment on NIFI-7246 at 10/16/20, 4:58 PM:
--
[
https://issues.apache.org/jira/browse/NIFI-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215494#comment-17215494
]
Sebastian Valle commented on NIFI-7246:
---
Hi. This change would greatly benefit my pa
pvillard31 commented on pull request #4605:
URL: https://github.com/apache/nifi/pull/4605#issuecomment-710165518
Hi @kevinbsilva - thanks for this pull request. The use of parameters is
highly recommended over the use of variables going forward. Any reason for not
using the parameters in t
[
https://issues.apache.org/jira/browse/NIFI-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-7933:
-
Component/s: Extensions
> CSV Escape does not work for SelectHiveQL processor
> -
[
https://issues.apache.org/jira/browse/NIFI-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-7933.
--
Fix Version/s: 1.13.0
Resolution: Fixed
> CSV Escape does not work for SelectHiveQL proce
pvillard31 commented on pull request #4606:
URL: https://github.com/apache/nifi/pull/4606#issuecomment-710158699
Thanks @indrajeetgour - merged to main
This is an automated message from the Apache Git Service.
To respond to t
asfgit closed pull request #4606:
URL: https://github.com/apache/nifi/pull/4606
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
[
https://issues.apache.org/jira/browse/NIFI-7933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215479#comment-17215479
]
ASF subversion and git services commented on NIFI-7933:
---
Commit 4a37
andrewmlim opened a new pull request #307:
URL: https://github.com/apache/nifi-registry/pull/307
Also updated CreateMultipleBuckets test with proper css selectors.
Confirmed that "mvn install -Pselenium_tests" runs successfully under
conditions described in https://issues.apache.org/
[
https://issues.apache.org/jira/browse/NIFIREG-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew M. Lim updated NIFIREG-425:
--
Description:
The automated UI tests were failing because the "#" in the URL is now required.
[
https://issues.apache.org/jira/browse/NIFIREG-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew M. Lim reassigned NIFIREG-425:
-
Assignee: Andrew M. Lim
> Automated UI tests fail due to incorrect URLs
> -
Andrew M. Lim created NIFIREG-425:
-
Summary: Automated UI tests fail due to incorrect URLs
Key: NIFIREG-425
URL: https://issues.apache.org/jira/browse/NIFIREG-425
Project: NiFi Registry
Issue
NissimShiman commented on pull request #4130:
URL: https://github.com/apache/nifi/pull/4130#issuecomment-710127234
@anaylor I see this rebase is turning out to be more complex then it should
be...
I think the challenge is that apache nifi's primary branch moved from master
to main
pkelly-nifi commented on a change in pull request #4576:
URL: https://github.com/apache/nifi/pull/4576#discussion_r506560739
##
File path:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/FetchS3Object.java
##
@@ -147,6 +171,
[
https://issues.apache.org/jira/browse/NIFI-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215441#comment-17215441
]
Lucas Moten commented on NIFI-7934:
---
Determined to be a duplicate of NIFI-7886
> FetchS
[
https://issues.apache.org/jira/browse/NIFI-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Moten resolved NIFI-7934.
---
Resolution: Duplicate
> FetchS3Object processor should support range requesting
>
lucasmoten commented on a change in pull request #4576:
URL: https://github.com/apache/nifi/pull/4576#discussion_r506507839
##
File path:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/s3/FetchS3Object.java
##
@@ -147,6 +171,1
lucasmoten commented on pull request #4607:
URL: https://github.com/apache/nifi/pull/4607#issuecomment-710089800
> Hi @lucasmoten, thanks for the contribution but I believe this is already
covered by #4576, no?
Aha! Yes. I will close this issue.
lucasmoten closed pull request #4607:
URL: https://github.com/apache/nifi/pull/4607
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
eylonronen opened a new pull request #4608:
URL: https://github.com/apache/nifi/pull/4608
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
It adds the error reason supplied by elasticsearch
Eylon Ronen created NIFI-7935:
-
Summary: Add error reason to failed flowfiles of
PutElasticsearchHttp
Key: NIFI-7935
URL: https://issues.apache.org/jira/browse/NIFI-7935
Project: Apache NiFi
Iss
pvillard31 commented on pull request #4607:
URL: https://github.com/apache/nifi/pull/4607#issuecomment-709873880
Hi @lucasmoten, thanks for the contribution but I believe this is already
covered by #4576, no?
This is an auto
31 matches
Mail list logo