[jira] [Commented] (NIFI-7588) InvokeHTTP ignoring custom parameters when stop+finalize+start

[ https://issues.apache.org/jira/browse/NIFI-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17393745#comment-17393745 ] Firenz commented on NIFI-7588: -- I think i had the same issue with my old NIFI 1.8.0 here :  N

[jira] [Created] (NIFI-9011) Tags Processor Kafka 2.6 / 2.5

Firenz created NIFI-9011: Summary: Tags Processor Kafka 2.6 / 2.5 Key: NIFI-9011 URL: https://issues.apache.org/jira/browse/NIFI-9011 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.13.2

[jira] [Created] (NIFI-8992) KafkaRecordSink_2_* - Unable to use PLAIN auth mecanism

Firenz created NIFI-8992: Summary: KafkaRecordSink_2_* - Unable to use PLAIN auth mecanism Key: NIFI-8992 URL: https://issues.apache.org/jira/browse/NIFI-8992 Project: Apache NiFi Issue Type: Bug

[jira] [Created] (NIFI-7840) ExecuteScript - Groovy 3.0

Firenz created NIFI-7840: Summary: ExecuteScript - Groovy 3.0 Key: NIFI-7840 URL: https://issues.apache.org/jira/browse/NIFI-7840 Project: Apache NiFi Issue Type: Wish Components: Extension

[jira] [Commented] (NIFI-7749) listSFTP - Failed "Should not reach here"

[ https://issues.apache.org/jira/browse/NIFI-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180595#comment-17180595 ] Firenz commented on NIFI-7749: -- After investigation it would be a side effect of a HTTP proxy

[jira] [Created] (NIFI-7749) listSFTP - Failed "Should not reach here"

Firenz created NIFI-7749: Summary: listSFTP - Failed "Should not reach here" Key: NIFI-7749 URL: https://issues.apache.org/jira/browse/NIFI-7749 Project: Apache NiFi Issue Type: Improvement

[jira] [Updated] (NIFI-7596) InvokeHTTP - Get Request Body From Attribute

[ https://issues.apache.org/jira/browse/NIFI-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-7596: - Description: *Use case :* the flow file contains 1 big data (ex : PDF or pictures), but you want to lookup metada

[jira] [Created] (NIFI-7596) InvokeHTTP - Get Request Body From Attribute

Firenz created NIFI-7596: Summary: InvokeHTTP - Get Request Body From Attribute Key: NIFI-7596 URL: https://issues.apache.org/jira/browse/NIFI-7596 Project: Apache NiFi Issue Type: Improvement

[jira] [Commented] (NIFI-6975) Processor for SAP Java Connector (SAP JCo)

[ https://issues.apache.org/jira/browse/NIFI-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144018#comment-17144018 ] Firenz commented on NIFI-6975: -- It seems difficult due to the fact that the JCO cannot be red

[jira] [Updated] (NIFI-7522) Processor Kafka 2.5 / Static Membership

[ https://issues.apache.org/jira/browse/NIFI-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-7522: - Attachment: (was: nifi-kafka-2-5-nar-1.11.5-SNAPSHOT.nar) > Processor Kafka 2.5 / Static Membership >

[jira] [Updated] (NIFI-7522) Processor Kafka 2.5 / Static Membership

[ https://issues.apache.org/jira/browse/NIFI-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-7522: - Description: Kafka 2.4 introduced the static membership  [[KIP-345|https://cwiki.apache.org/confluence/display/KAF

[jira] [Commented] (NIFI-7533) Urgent requirement for cdc for Postgres

[ https://issues.apache.org/jira/browse/NIFI-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138184#comment-17138184 ] Firenz commented on NIFI-7533: -- CDC for MySQL and PostgreSQL are two distinct "technologies"

[jira] [Updated] (NIFI-7522) Processor Kafka 2.5 / Static Membership

[ https://issues.apache.org/jira/browse/NIFI-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-7522: - Description: Kafka 2.4 introduced the static membership  [[KIP-345|https://cwiki.apache.org/confluence/display/KAF

[jira] [Updated] (NIFI-7522) Processor Kafka 2.5 / Static Membership

[ https://issues.apache.org/jira/browse/NIFI-7522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-7522: - Description: Kafka 2.4 introduced the static membership  [[KIP-345|https://cwiki.apache.org/confluence/display/KAF

[jira] [Created] (NIFI-7522) Processor Kafka 2.5 / Static Membership

Firenz created NIFI-7522: Summary: Processor Kafka 2.5 / Static Membership Key: NIFI-7522 URL: https://issues.apache.org/jira/browse/NIFI-7522 Project: Apache NiFi Issue Type: Improvement C

[jira] [Commented] (NIFI-6777) Data Provenance SIGSEGV : Search Lucene Index-1

[ https://issues.apache.org/jira/browse/NIFI-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989925#comment-16989925 ] Firenz commented on NIFI-6777: -- The disabling of G1GC did not solved our issue. We've just ha

[jira] [Commented] (NIFI-6777) Data Provenance SIGSEGV : Search Lucene Index-1

[ https://issues.apache.org/jira/browse/NIFI-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953028#comment-16953028 ] Firenz commented on NIFI-6777: -- Thanks for you answer. We are using G1GC. So, we've just disa

[jira] [Updated] (NIFI-6777) Data Provenance SIGSEGV : Search Lucene Index-1

[ https://issues.apache.org/jira/browse/NIFI-6777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-6777: - Description: NIFI crashes with a core dump when using data provenance (5 times in 1 months, 4 differents VMs).  

[jira] [Created] (NIFI-6777) Data Provenance SIGSEGV : Search Lucene Index-1

Firenz created NIFI-6777: Summary: Data Provenance SIGSEGV : Search Lucene Index-1 Key: NIFI-6777 URL: https://issues.apache.org/jira/browse/NIFI-6777 Project: Apache NiFi Issue Type: Bug C

[jira] [Resolved] (NIFI-5964) InvokeHTTP, Dynamic Headers not sent (Cluster)

[ https://issues.apache.org/jira/browse/NIFI-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz resolved NIFI-5964. -- Resolution: Cannot Reproduce Not reproduct since. > InvokeHTTP, Dynamic Headers not sent (Cluster) > --

[jira] [Commented] (NIFI-6697) HandleHttpRequest - 500, stopping does not works

[ https://issues.apache.org/jira/browse/NIFI-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934661#comment-16934661 ] Firenz commented on NIFI-6697: -- Thanks for the hint. I may try to create a quick fix for NIFI

[jira] [Updated] (NIFI-6697) HandleHttpRequest - 500, stopping does not works

[ https://issues.apache.org/jira/browse/NIFI-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-6697: - Description: My HandleHTTPRequest does not accept anymore POST messages, after some time, returning 500 (port 100

[jira] [Created] (NIFI-6697) HandleHttpRequest - 500, stopping does not works

Firenz created NIFI-6697: Summary: HandleHttpRequest - 500, stopping does not works Key: NIFI-6697 URL: https://issues.apache.org/jira/browse/NIFI-6697 Project: Apache NiFi Issue Type: Bug

[jira] [Created] (NIFI-6233) HandleHttpRequest -> File Leak if Port already Bind

Firenz created NIFI-6233: Summary: HandleHttpRequest -> File Leak if Port already Bind Key: NIFI-6233 URL: https://issues.apache.org/jira/browse/NIFI-6233 Project: Apache NiFi Issue Type: Bug Aff

[jira] [Commented] (NIFI-5964) InvokeHTTP, Dynamic Headers not sent (Cluster)

[ https://issues.apache.org/jira/browse/NIFI-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746454#comment-16746454 ] Firenz commented on NIFI-5964: -- Additionnal infos : it happened with two differents invokeHtt

[jira] [Created] (NIFI-5964) InvokeHTTP, Dynamic Headers not sent (Cluster)

Firenz created NIFI-5964: Summary: InvokeHTTP, Dynamic Headers not sent (Cluster) Key: NIFI-5964 URL: https://issues.apache.org/jira/browse/NIFI-5964 Project: Apache NiFi Issue Type: Bug Affects

[jira] [Updated] (NIFI-5964) InvokeHTTP, Dynamic Headers not sent (Cluster)

[ https://issues.apache.org/jira/browse/NIFI-5964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-5964: - Attachment: Step 1 - Bulletin.png Step 1 - InvokeHTTP conf.png Step 2 - Bulletin.pn

[jira] [Updated] (NIFI-5825) ConsumeJMS - Not using Clientid / durable does not works

[ https://issues.apache.org/jira/browse/NIFI-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-5825: - Description: I cannot make the ConsumeJMS 1.8.0 processor work as a "durable consumer". I set the client id, but

[jira] [Updated] (NIFI-5825) ConsumeJMS - Not using Clientid / durable does not works

[ https://issues.apache.org/jira/browse/NIFI-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-5825: - Attachment: amq_consume.JPG > ConsumeJMS - Not using Clientid / durable does not works > -

[jira] [Updated] (NIFI-5825) ConsumeJMS - Not using Clientid / durable does not works

[ https://issues.apache.org/jira/browse/NIFI-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz updated NIFI-5825: - Attachment: nifi_consumejms.JPG > ConsumeJMS - Not using Clientid / durable does not works > -

[jira] [Created] (NIFI-5825) ConsumeJMS - Not using Clientid / durable does not works

Firenz created NIFI-5825: Summary: ConsumeJMS - Not using Clientid / durable does not works Key: NIFI-5825 URL: https://issues.apache.org/jira/browse/NIFI-5825 Project: Apache NiFi Issue Type: Bug

[jira] [Commented] (NIFI-5536) Add EL support for password on AMQP processors

[ https://issues.apache.org/jira/browse/NIFI-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586984#comment-16586984 ] Firenz commented on NIFI-5536: -- A first iteration shouldn't be to enable EL on password like

[jira] [Resolved] (NIFI-5046) Nifi toolkit - "server" - Bad check on listening port

[ https://issues.apache.org/jira/browse/NIFI-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firenz resolved NIFI-5046. -- Resolution: Not A Bug The port specified with "--port" is overwritten by the one specified in the "-configJsonIn

[jira] [Commented] (NIFI-5046) Nifi toolkit - "server" - Bad check on listening port

[ https://issues.apache.org/jira/browse/NIFI-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428238#comment-16428238 ] Firenz commented on NIFI-5046: -- My mistake, the port specified with "--port" is just overwritt

[jira] [Created] (NIFI-5046) Nifi toolkit - "server" - Bad check on listening port

Firenz created NIFI-5046: Summary: Nifi toolkit - "server" - Bad check on listening port Key: NIFI-5046 URL: https://issues.apache.org/jira/browse/NIFI-5046 Project: Apache NiFi Issue Type: Bug A

[jira] [Created] (NIFI-4500) Alternative UI - Table Way

Firenz created NIFI-4500: Summary: Alternative UI - Table Way Key: NIFI-4500 URL: https://issues.apache.org/jira/browse/NIFI-4500 Project: Apache NiFi Issue Type: Wish Components: Core UI