[jira] [Comment Edited] (NIFI-7357) Make Zookeeper TLS Properties Available via nifi.properties
[ https://issues.apache.org/jira/browse/NIFI-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083612#comment-17083612 ] Jeff Storck edited comment on NIFI-7357 at 4/14/20, 9:13 PM: - Should the scope of this Jira include making these properties configurable via the environment variables for the docker image(s), or should a separate Jira be created for that? was (Author: jtstorck): Should the scope of this Jira include making these properties configurable via the environment variables for the docker image(s)? > Make Zookeeper TLS Properties Available via nifi.properties > --- > > Key: NIFI-7357 > URL: https://issues.apache.org/jira/browse/NIFI-7357 > Project: Apache NiFi > Issue Type: Sub-task > Components: Configuration, Configuration Management, Security >Reporter: Troy Melhase >Assignee: Troy Melhase >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-7357) Make Zookeeper TLS Properties Available via nifi.properties
[ https://issues.apache.org/jira/browse/NIFI-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083612#comment-17083612 ] Jeff Storck commented on NIFI-7357: --- Should the scope of this Jira include making these properties configurable via the environment variables for the docker image(s)? > Make Zookeeper TLS Properties Available via nifi.properties > --- > > Key: NIFI-7357 > URL: https://issues.apache.org/jira/browse/NIFI-7357 > Project: Apache NiFi > Issue Type: Sub-task > Components: Configuration, Configuration Management, Security >Reporter: Troy Melhase >Assignee: Troy Melhase >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7353) ReplaceText does not document that EL values are literalized for Search Value
Jeff Storck created NIFI-7353:
-
Summary: ReplaceText does not document that EL values are
literalized for Search Value
Key: NIFI-7353
URL: https://issues.apache.org/jira/browse/NIFI-7353
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Affects Versions: 1.11.4
Reporter: Jeff Storck
ReplaceText should document for the {{Search Value}} property that EL values
will be literalized/quoted.
For example, if {{Search Value}} is set to {{$\{myregex}}}, and
{code:java}
myregex = ^.*$
{code}
the evaluated value for the {{Search Value}} property will be
{code:java}
\Q^.*$\E
{code}
That makes {{Search Value}} effectively the literal string "^.*$", and it will
not be used as a regular expression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-7025) Add kerberos password property to NiFi Hive components
[ https://issues.apache.org/jira/browse/NIFI-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7025: -- Status: Patch Available (was: Reopened) > Add kerberos password property to NiFi Hive components > -- > > Key: NIFI-7025 > URL: https://issues.apache.org/jira/browse/NIFI-7025 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Fix For: 1.12.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi Hive components, a password field > should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * Hive3ConnectionPool > * Hive_1_1ConnectionPool > * HiveConnectionPool > * PutHive3Streaming > * PutHiveStreaming -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (NIFI-7025) Add kerberos password property to NiFi Hive components
[ https://issues.apache.org/jira/browse/NIFI-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck reopened NIFI-7025: --- Reopening to address an issue with PutHive3Streaming encountering authentication issues caused by not wrapping calls to Hive with UGI.doAs. > Add kerberos password property to NiFi Hive components > -- > > Key: NIFI-7025 > URL: https://issues.apache.org/jira/browse/NIFI-7025 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Fix For: 1.12.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi Hive components, a password field > should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * Hive3ConnectionPool > * Hive_1_1ConnectionPool > * HiveConnectionPool > * PutHive3Streaming > * PutHiveStreaming -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7030) Add kerberos password property to NiFi Solr components
[ https://issues.apache.org/jira/browse/NIFI-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7030: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to Apache NiFI master via: https://github.com/apache/nifi/commit/852d2f32104f96e47e6d42ddfaba3747d0e05dc0 > Add kerberos password property to NiFi Solr components > -- > > Key: NIFI-7030 > URL: https://issues.apache.org/jira/browse/NIFI-7030 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Bryan Bende >Priority: Major > Fix For: 1.12.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized Solr endpoints from NiFi Solr components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * SolrProcessor > * SolrUtils (in the nifi-solr-processors module) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7019) Add kerberos principal and password properties to NiFi DBPCConnectionPool
[ https://issues.apache.org/jira/browse/NIFI-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7019: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to Apache NiFi master via: https://github.com/apache/nifi/commit/e0fc75a963ba88fd9d272244df920d210a98a895 > Add kerberos principal and password properties to NiFi DBPCConnectionPool > - > > Key: NIFI-7019 > URL: https://issues.apache.org/jira/browse/NIFI-7019 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Bryan Bende >Priority: Major > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > In addition to the KerberosCredentialsService option for accessing kerberized > databases from DBCPConnectionPool, principal and password fields should be > added. > Components should validate that only one set of options should be configured: > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7029) Add kerberos password property to NiFi Kudu components
[ https://issues.apache.org/jira/browse/NIFI-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7029: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to Apache NiFi master via:https://github.com/apache/nifi/commit/5b93e537d59bc005e5e1cab0aa14537566dbac2c > Add kerberos password property to NiFi Kudu components > -- > > Key: NIFI-7029 > URL: https://issues.apache.org/jira/browse/NIFI-7029 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Bryan Bende >Priority: Major > Fix For: 1.12.0 > > Time Spent: 40m > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized Kudu endpoints from NiFi Kudu components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * AbstractKuduProcessor > * PutKudu > * KuduLookupService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7026) Add kerberos password property to NiFi HortonworksSchemaRegistry
[ https://issues.apache.org/jira/browse/NIFI-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7026: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged via [https://github.com/apache/nifi/commit/c74e71306eae381fee7b0bf5f643ae7462461461] > Add kerberos password property to NiFi HortonworksSchemaRegistry > > > Key: NIFI-7026 > URL: https://issues.apache.org/jira/browse/NIFI-7026 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Bryan Bende >Priority: Major > Fix For: 1.12.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized Schema Registry from the HortonworksSchemaRegistry > controller service, a password field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7024) Add kerberos password property to NiFi HBase components
[ https://issues.apache.org/jira/browse/NIFI-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7024: -- Status: Patch Available (was: In Progress) > Add kerberos password property to NiFi HBase components > --- > > Key: NIFI-7024 > URL: https://issues.apache.org/jira/browse/NIFI-7024 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi HBase components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * HBase_1_1_2_ClientService > * HBase_2_ClientService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-7024) Add kerberos password property to NiFi HBase components
[ https://issues.apache.org/jira/browse/NIFI-7024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck reassigned NIFI-7024: - Assignee: Jeff Storck > Add kerberos password property to NiFi HBase components > --- > > Key: NIFI-7024 > URL: https://issues.apache.org/jira/browse/NIFI-7024 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi HBase components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * HBase_1_1_2_ClientService > * HBase_2_ClientService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7025) Add kerberos password property to NiFi Hive components
[ https://issues.apache.org/jira/browse/NIFI-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7025: -- Status: Patch Available (was: In Progress) > Add kerberos password property to NiFi Hive components > -- > > Key: NIFI-7025 > URL: https://issues.apache.org/jira/browse/NIFI-7025 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi Hive components, a password field > should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * Hive3ConnectionPool > * Hive_1_1ConnectionPool > * HiveConnectionPool > * PutHive3Streaming > * PutHiveStreaming -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-7025) Add kerberos password property to NiFi Hive components
[ https://issues.apache.org/jira/browse/NIFI-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck reassigned NIFI-7025: - Assignee: Jeff Storck > Add kerberos password property to NiFi Hive components > -- > > Key: NIFI-7025 > URL: https://issues.apache.org/jira/browse/NIFI-7025 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi Hive components, a password field > should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * Hive3ConnectionPool > * Hive_1_1ConnectionPool > * HiveConnectionPool > * PutHive3Streaming > * PutHiveStreaming -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7018) Add kerberos password property to NiFi HDFS components
[ https://issues.apache.org/jira/browse/NIFI-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7018: -- Status: Patch Available (was: In Progress) > Add kerberos password property to NiFi HDFS components > -- > > Key: NIFI-7018 > URL: https://issues.apache.org/jira/browse/NIFI-7018 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized HDFS endpoints from NiFi HDFS components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (NIFI-7065) Update JCenter repository URL to HTTPS
[ https://issues.apache.org/jira/browse/NIFI-7065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck resolved NIFI-7065. --- Fix Version/s: (was: 1.12.0) Resolution: Not A Problem This was already fixed on master previously. > Update JCenter repository URL to HTTPS > -- > > Key: NIFI-7065 > URL: https://issues.apache.org/jira/browse/NIFI-7065 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Affects Versions: 1.11.0 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > As of January 2020, JCenter now allows access via HTTPS. > For reference: https://jfrog.com/blog/secure-jcenter-with-https/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7065) Update JCenter repository URL to HTTPS
[ https://issues.apache.org/jira/browse/NIFI-7065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7065: -- Affects Version/s: (was: 1.11.0) > Update JCenter repository URL to HTTPS > -- > > Key: NIFI-7065 > URL: https://issues.apache.org/jira/browse/NIFI-7065 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > As of January 2020, JCenter now allows access via HTTPS. > For reference: https://jfrog.com/blog/secure-jcenter-with-https/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7065) Update JCenter repository URL to HTTPS
Jeff Storck created NIFI-7065: - Summary: Update JCenter repository URL to HTTPS Key: NIFI-7065 URL: https://issues.apache.org/jira/browse/NIFI-7065 Project: Apache NiFi Issue Type: Task Components: Tools and Build Affects Versions: 1.11.0 Reporter: Jeff Storck Assignee: Jeff Storck Fix For: 1.12.0 As of January 2020, JCenter now allows access via HTTPS. For reference: https://jfrog.com/blog/secure-jcenter-with-https/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6988) Add password properties to NiFi components that support kerberos
[ https://issues.apache.org/jira/browse/NIFI-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6988: -- Remaining Estimate: 240h (was: 336h) Original Estimate: 240h (was: 336h) > Add password properties to NiFi components that support kerberos > > > Key: NIFI-6988 > URL: https://issues.apache.org/jira/browse/NIFI-6988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Affects Versions: 1.10.0 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Original Estimate: 240h > Remaining Estimate: 240h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi components, a password field > should be added to the affected component configurations. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change are listed as sub-tasks > of this JIRA. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7018) Add kerberos password property to NiFi HDFS components
[ https://issues.apache.org/jira/browse/NIFI-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7018: -- Description: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized HDFS endpoints from NiFi HDFS components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService was: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized services from NiFi HDFS components, a password field should be added. Components should validate that only one set of options should be configured: principal and keytab principal and password KerberosCredentialsService > Add kerberos password property to NiFi HDFS components > -- > > Key: NIFI-7018 > URL: https://issues.apache.org/jira/browse/NIFI-7018 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized HDFS endpoints from NiFi HDFS components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7019) Add kerberos principal and password properties to NiFi DBPCConnectionPool
[ https://issues.apache.org/jira/browse/NIFI-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7019: -- Summary: Add kerberos principal and password properties to NiFi DBPCConnectionPool (was: Add Kerberos principal and password properties to NiFi DBPCConnectionPool) > Add kerberos principal and password properties to NiFi DBPCConnectionPool > - > > Key: NIFI-7019 > URL: https://issues.apache.org/jira/browse/NIFI-7019 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the KerberosCredentialsService option for accessing kerberized > databases from DBCPConnectionPool, principal and password fields should be > added. > Components should validate that only one set of options should be configured: > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6988) Add password properties to NiFi components that support kerberos
[ https://issues.apache.org/jira/browse/NIFI-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6988: -- Description: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized services from NiFi components, a password field should be added to the affected component configurations. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change are listed as sub-tasks of this JIRA. was: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized services from NiFi Hadoop components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * AbstractHadoopProcessor * AbstractKuduProcessor * DBCPConnectionPool * HBase_1_1_2_ClientService * HBase_2_ClientService * Hive3ConnectionPool * Hive_1_1ConnectionPool * HiveConnectionPool * HortonworksSchemaRegistry * KafkaProcessorUtils * KafkaRecordSink_1_0 * KafkaRecordSink_2_0 * Kerberos (in the nifi-atlas-reporting-task module) * KuduLookupService * PutHive3Streaming * PutHiveStreaming * ReportLineageToAtlas * SolrProcessor * SolrUtils (in the nifi-solr-processors module) > Add password properties to NiFi components that support kerberos > > > Key: NIFI-6988 > URL: https://issues.apache.org/jira/browse/NIFI-6988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Affects Versions: 1.10.0 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Original Estimate: 336h > Remaining Estimate: 336h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi components, a password field > should be added to the affected component configurations. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change are listed as sub-tasks > of this JIRA. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7027) Add kerberos password property to NiFi Kafka components
[ https://issues.apache.org/jira/browse/NIFI-7027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7027: -- Summary: Add kerberos password property to NiFi Kafka components (was: Add kerberos password property to Kafka components) > Add kerberos password property to NiFi Kafka components > --- > > Key: NIFI-7027 > URL: https://issues.apache.org/jira/browse/NIFI-7027 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized Kafka endpoints from NiFi's Kafka components, a > password field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * KafkaProcessorUtils > * KafkaRecordSink_1_0 > * KafkaRecordSink_2_0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7029) Add kerberos password property to NiFi Kudu components
[ https://issues.apache.org/jira/browse/NIFI-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7029: -- Description: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Kudu endpoints from NiFi Kudu components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * AbstractKuduProcessor * PutKudu * KuduLookupService was: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Kudu endpoints from NiFi Kudu components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * PutKudu * KuduLookupService > Add kerberos password property to NiFi Kudu components > -- > > Key: NIFI-7029 > URL: https://issues.apache.org/jira/browse/NIFI-7029 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized Kudu endpoints from NiFi Kudu components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * AbstractKuduProcessor > * PutKudu > * KuduLookupService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7026) Add kerberos password property to NiFi HortonworksSchemaRegistry
[ https://issues.apache.org/jira/browse/NIFI-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7026: -- Summary: Add kerberos password property to NiFi HortonworksSchemaRegistry (was: Add kerberos password property to HortonworksSchemaRegistry) > Add kerberos password property to NiFi HortonworksSchemaRegistry > > > Key: NIFI-7026 > URL: https://issues.apache.org/jira/browse/NIFI-7026 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized Schema Registry from the HortonworksSchemaRegistry > controller service, a password field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7018) Add kerberos password property to NiFi HDFS components
[ https://issues.apache.org/jira/browse/NIFI-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7018: -- Summary: Add kerberos password property to NiFi HDFS components (was: Add password property to HDFS components) > Add kerberos password property to NiFi HDFS components > -- > > Key: NIFI-7018 > URL: https://issues.apache.org/jira/browse/NIFI-7018 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi HDFS components, a password field > should be added. > Components should validate that only one set of options should be configured: > principal and keytab > principal and password > KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7019) Add Kerberos principal and password properties to NiFi DBPCConnectionPool
[ https://issues.apache.org/jira/browse/NIFI-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7019: -- Summary: Add Kerberos principal and password properties to NiFi DBPCConnectionPool (was: Add principal and password properties to NiFi DBPCConnectionPool) > Add Kerberos principal and password properties to NiFi DBPCConnectionPool > - > > Key: NIFI-7019 > URL: https://issues.apache.org/jira/browse/NIFI-7019 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the KerberosCredentialsService option for accessing kerberized > databases from DBCPConnectionPool, principal and password fields should be > added. > Components should validate that only one set of options should be configured: > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7030) Add kerberos password property to NiFi Solr components
Jeff Storck created NIFI-7030: - Summary: Add kerberos password property to NiFi Solr components Key: NIFI-7030 URL: https://issues.apache.org/jira/browse/NIFI-7030 Project: Apache NiFi Issue Type: Sub-task Components: Extensions Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Solr endpoints from NiFi Solr components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * SolrProcessor * SolrUtils (in the nifi-solr-processors module) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7029) Add kerberos password property to NiFi Kudu components
[ https://issues.apache.org/jira/browse/NIFI-7029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7029: -- Description: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Kudu endpoints from NiFi Kudu components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * PutKudu * KuduLookupService was: In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Kudu endpoints from NiFi Kudu components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService > Add kerberos password property to NiFi Kudu components > -- > > Key: NIFI-7029 > URL: https://issues.apache.org/jira/browse/NIFI-7029 > Project: Apache NiFi > Issue Type: Sub-task > Components: Extensions >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized Kudu endpoints from NiFi Kudu components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * PutKudu > * KuduLookupService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7029) Add kerberos password property to NiFi Kudu components
Jeff Storck created NIFI-7029: - Summary: Add kerberos password property to NiFi Kudu components Key: NIFI-7029 URL: https://issues.apache.org/jira/browse/NIFI-7029 Project: Apache NiFi Issue Type: Sub-task Components: Extensions Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Kudu endpoints from NiFi Kudu components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7028) Add kerberos password property to NiFi Atlas components
Jeff Storck created NIFI-7028: - Summary: Add kerberos password property to NiFi Atlas components Key: NIFI-7028 URL: https://issues.apache.org/jira/browse/NIFI-7028 Project: Apache NiFi Issue Type: Sub-task Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Atlas endpoints from NiFi's Atlas components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * Kerberos (in the nifi-atlas-reporting-task module) * ReportLineageToAtlas -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7027) Add kerberos password property to Kafka components
Jeff Storck created NIFI-7027: - Summary: Add kerberos password property to Kafka components Key: NIFI-7027 URL: https://issues.apache.org/jira/browse/NIFI-7027 Project: Apache NiFi Issue Type: Sub-task Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Kafka endpoints from NiFi's Kafka components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * KafkaProcessorUtils * KafkaRecordSink_1_0 * KafkaRecordSink_2_0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7026) Add kerberos password property to HortonworksSchemaRegistry
Jeff Storck created NIFI-7026: - Summary: Add kerberos password property to HortonworksSchemaRegistry Key: NIFI-7026 URL: https://issues.apache.org/jira/browse/NIFI-7026 Project: Apache NiFi Issue Type: Sub-task Components: Extensions Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized Schema Registry from the HortonworksSchemaRegistry controller service, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-7019) Add principal and password properties to NiFi DBPCConnectionPool
[ https://issues.apache.org/jira/browse/NIFI-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-7019: -- Description: In addition to the KerberosCredentialsService option for accessing kerberized databases from DBCPConnectionPool, principal and password fields should be added. Components should validate that only one set of options should be configured: * principal and password * KerberosCredentialsService was: In addition to the KerberosCredentialsService option for accessing kerberized services from DBCPConnectionPool, principal and password fields should be added. Components should validate that only one set of options should be configured: principal and password KerberosCredentialsService > Add principal and password properties to NiFi DBPCConnectionPool > > > Key: NIFI-7019 > URL: https://issues.apache.org/jira/browse/NIFI-7019 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the KerberosCredentialsService option for accessing kerberized > databases from DBCPConnectionPool, principal and password fields should be > added. > Components should validate that only one set of options should be configured: > * principal and password > * KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7025) Add kerberos password property to NiFi Hive components
Jeff Storck created NIFI-7025: - Summary: Add kerberos password property to NiFi Hive components Key: NIFI-7025 URL: https://issues.apache.org/jira/browse/NIFI-7025 Project: Apache NiFi Issue Type: Sub-task Components: Extensions Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized services from NiFi Hive components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * Hive3ConnectionPool * Hive_1_1ConnectionPool * HiveConnectionPool * PutHive3Streaming * PutHiveStreaming -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7024) Add kerberos password property to NiFi HBase components
Jeff Storck created NIFI-7024: - Summary: Add kerberos password property to NiFi HBase components Key: NIFI-7024 URL: https://issues.apache.org/jira/browse/NIFI-7024 Project: Apache NiFi Issue Type: Sub-task Components: Extensions Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized services from NiFi HBase components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * HBase_1_1_2_ClientService * HBase_2_ClientService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7019) Add principal and password properties to NiFi DBPCConnectionPool
Jeff Storck created NIFI-7019: - Summary: Add principal and password properties to NiFi DBPCConnectionPool Key: NIFI-7019 URL: https://issues.apache.org/jira/browse/NIFI-7019 Project: Apache NiFi Issue Type: Sub-task Reporter: Jeff Storck Assignee: Jeff Storck In addition to the KerberosCredentialsService option for accessing kerberized services from DBCPConnectionPool, principal and password fields should be added. Components should validate that only one set of options should be configured: principal and password KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-7018) Add password property to HDFS components
Jeff Storck created NIFI-7018: - Summary: Add password property to HDFS components Key: NIFI-7018 URL: https://issues.apache.org/jira/browse/NIFI-7018 Project: Apache NiFi Issue Type: Sub-task Components: Extensions Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized services from NiFi HDFS components, a password field should be added. Components should validate that only one set of options should be configured: principal and keytab principal and password KerberosCredentialsService -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6988) Add password properties to NiFi components that support kerberos
[ https://issues.apache.org/jira/browse/NIFI-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6988: -- Summary: Add password properties to NiFi components that support kerberos (was: Add password properties to NiFi Hadoop components) > Add password properties to NiFi components that support kerberos > > > Key: NIFI-6988 > URL: https://issues.apache.org/jira/browse/NIFI-6988 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Affects Versions: 1.10.0 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Original Estimate: 336h > Remaining Estimate: 336h > > In addition to the principal/keytab and KerberosCredentialsService options > for accessing kerberized services from NiFi Hadoop components, a password > field should be added. > Components should validate that only one set of options should be configured: > * principal and keytab > * principal and password > * KerberosCredentialsService > The components that will be affected by this change: > * AbstractHadoopProcessor > * AbstractKuduProcessor > * DBCPConnectionPool > * HBase_1_1_2_ClientService > * HBase_2_ClientService > * Hive3ConnectionPool > * Hive_1_1ConnectionPool > * HiveConnectionPool > * HortonworksSchemaRegistry > * KafkaProcessorUtils > * KafkaRecordSink_1_0 > * KafkaRecordSink_2_0 > * Kerberos (in the nifi-atlas-reporting-task module) > * KuduLookupService > * PutHive3Streaming > * PutHiveStreaming > * ReportLineageToAtlas > * SolrProcessor > * SolrUtils (in the nifi-solr-processors module) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6833) Provide instance qualification of principals in KeytabCredentialsService
[ https://issues.apache.org/jira/browse/NIFI-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6833: -- Fix Version/s: (was: 1.11.0) > Provide instance qualification of principals in KeytabCredentialsService > > > Key: NIFI-6833 > URL: https://issues.apache.org/jira/browse/NIFI-6833 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > A KeytabCredentialsService should be able to qualify a principal or shortname > with the instance on which it is running. > A new property should be added that allows the user to select one of the > following qualification options: > * none > * hostname > * FQDN > If NiFi is running on host "nifi.apache.org" and a *KeytabCredentialsService* > was created with a *Kerberos Principal* property value of "n...@example.com", > the *KeytabCredentialsService*** should be able return a qualified principal, > based on the qualification option: > * none -> "n...@example.com" > * hostname -> "nifi/n...@example.com" > * FQDN -> "nifi/nifi.apache@example.com" > If a shortname is used it should be qualified as the qualification option > indicates: > * none -> "nifi" > * hostname -> "nifi/nifi" > * FQDN -> "nifi/nifi.apache.org" > Validation of the *KeytabCredentialsService* should fail if the principal is > already instance-qualified and "hostname" or "FQDN" is selected for the > qualification option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-6833) Provide instance qualification of principals in KeytabCredentialsService
[
https://issues.apache.org/jira/browse/NIFI-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17014613#comment-17014613
]
Jeff Storck commented on NIFI-6833:
---
Since there's an EL workaround for this (using ${hostname()} or
$hostname(true)} in the principal field depending on the desired result), I'll
remove the fix version of 1.11.0 from the ticket. This can be merged for the
next release.
> Provide instance qualification of principals in KeytabCredentialsService
>
>
> Key: NIFI-6833
> URL: https://issues.apache.org/jira/browse/NIFI-6833
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A KeytabCredentialsService should be able to qualify a principal or shortname
> with the instance on which it is running.
> A new property should be added that allows the user to select one of the
> following qualification options:
> * none
> * hostname
> * FQDN
> If NiFi is running on host "nifi.apache.org" and a *KeytabCredentialsService*
> was created with a *Kerberos Principal* property value of "n...@example.com",
> the *KeytabCredentialsService*** should be able return a qualified principal,
> based on the qualification option:
> * none -> "n...@example.com"
> * hostname -> "nifi/n...@example.com"
> * FQDN -> "nifi/nifi.apache@example.com"
> If a shortname is used it should be qualified as the qualification option
> indicates:
> * none -> "nifi"
> * hostname -> "nifi/nifi"
> * FQDN -> "nifi/nifi.apache.org"
> Validation of the *KeytabCredentialsService* should fail if the principal is
> already instance-qualified and "hostname" or "FQDN" is selected for the
> qualification option.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (NIFI-6833) Provide instance qualification of principals in KeytabCredentialsService
[ https://issues.apache.org/jira/browse/NIFI-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012322#comment-17012322 ] Jeff Storck commented on NIFI-6833: --- With the release candidate preparation for Apache NiFi 1.11.0 approaching, I'd like to get the PR for this JIRA merged to master. I need another day or two to address the comments on the PR. > Provide instance qualification of principals in KeytabCredentialsService > > > Key: NIFI-6833 > URL: https://issues.apache.org/jira/browse/NIFI-6833 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > A KeytabCredentialsService should be able to qualify a principal or shortname > with the instance on which it is running. > A new property should be added that allows the user to select one of the > following qualification options: > * none > * hostname > * FQDN > If NiFi is running on host "nifi.apache.org" and a *KeytabCredentialsService* > was created with a *Kerberos Principal* property value of "n...@example.com", > the *KeytabCredentialsService*** should be able return a qualified principal, > based on the qualification option: > * none -> "n...@example.com" > * hostname -> "nifi/n...@example.com" > * FQDN -> "nifi/nifi.apache@example.com" > If a shortname is used it should be qualified as the qualification option > indicates: > * none -> "nifi" > * hostname -> "nifi/nifi" > * FQDN -> "nifi/nifi.apache.org" > Validation of the *KeytabCredentialsService* should fail if the principal is > already instance-qualified and "hostname" or "FQDN" is selected for the > qualification option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6988) Add password properties to NiFi Hadoop components
Jeff Storck created NIFI-6988: - Summary: Add password properties to NiFi Hadoop components Key: NIFI-6988 URL: https://issues.apache.org/jira/browse/NIFI-6988 Project: Apache NiFi Issue Type: New Feature Components: Extensions Affects Versions: 1.10.0 Reporter: Jeff Storck Assignee: Jeff Storck In addition to the principal/keytab and KerberosCredentialsService options for accessing kerberized services from NiFi Hadoop components, a password field should be added. Components should validate that only one set of options should be configured: * principal and keytab * principal and password * KerberosCredentialsService The components that will be affected by this change: * AbstractHadoopProcessor * AbstractKuduProcessor * DBCPConnectionPool * HBase_1_1_2_ClientService * HBase_2_ClientService * Hive3ConnectionPool * Hive_1_1ConnectionPool * HiveConnectionPool * HortonworksSchemaRegistry * KafkaProcessorUtils * KafkaRecordSink_1_0 * KafkaRecordSink_2_0 * Kerberos (in the nifi-atlas-reporting-task module) * KuduLookupService * PutHive3Streaming * PutHiveStreaming * ReportLineageToAtlas * SolrProcessor * SolrUtils (in the nifi-solr-processors module) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6833) Provide instance qualification of principals in KeytabCredentialsService
[ https://issues.apache.org/jira/browse/NIFI-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6833: -- Status: Patch Available (was: In Progress) > Provide instance qualification of principals in KeytabCredentialsService > > > Key: NIFI-6833 > URL: https://issues.apache.org/jira/browse/NIFI-6833 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Fix For: 1.11.0 > > Time Spent: 10m > Remaining Estimate: 0h > > A KeytabCredentialsService should be able to qualify a principal or shortname > with the instance on which it is running. > A new property should be added that allows the user to select one of the > following qualification options: > * none > * hostname > * FQDN > If NiFi is running on host "nifi.apache.org" and a *KeytabCredentialsService* > was created with a *Kerberos Principal* property value of "n...@example.com", > the *KeytabCredentialsService*** should be able return a qualified principal, > based on the qualification option: > * none -> "n...@example.com" > * hostname -> "nifi/n...@example.com" > * FQDN -> "nifi/nifi.apache@example.com" > If a shortname is used it should be qualified as the qualification option > indicates: > * none -> "nifi" > * hostname -> "nifi/nifi" > * FQDN -> "nifi/nifi.apache.org" > Validation of the *KeytabCredentialsService* should fail if the principal is > already instance-qualified and "hostname" or "FQDN" is selected for the > qualification option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-6897) NiFi toolkit not Java 11 compatible
[
https://issues.apache.org/jira/browse/NIFI-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982572#comment-16982572
]
Jeff Storck commented on NIFI-6897:
---
The toolkit's classpath needs to include the same JAXB dependencies that are in
NiFI's lib/java11 directory; src/main/assembly/dependencies.xml will need to be
updated to establish dependencies on the JAXB libs (and if following NiFi's
example, those libs should be added to the lib/java11 dir), and the artifacts
that invoke the toolkit binaries that use XML will have to detect the JDK
version on which they are running and add the libs (or the lib/java11 dir) to
the classpath.
> NiFi toolkit not Java 11 compatible
> ---
>
> Key: NIFI-6897
> URL: https://issues.apache.org/jira/browse/NIFI-6897
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: 1.10.0
>Reporter: Mark Payne
>Assignee: Endre Kovacs
>Priority: Major
>
> With version 1.10.0, NiFi was made Java 11 compatible. However, the toolkit
> is not. Ran into the following error when attempting to use the CLI with Java
> 11:
> {code:java}
> bash-4.4$ $NIFI_TOOLKIT_HOME/bin/cli.sh nifi cluster-summary -ot json
> Exception in thread "main" java.lang.NoClassDefFoundError:
> javax/xml/bind/annotation/XmlElement
> at
> com.fasterxml.jackson.module.jaxb.JaxbAnnotationIntrospector.(JaxbAnnotationIntrospector.java:139)
> at
> com.fasterxml.jackson.module.jaxb.JaxbAnnotationIntrospector.(JaxbAnnotationIntrospector.java:126)
> at
> org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient.jacksonJaxbJsonProvider(JerseyNiFiClient.java:359)
> at
> org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient.(JerseyNiFiClient.java:111)
> at
> org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient.(JerseyNiFiClient.java:57)
> at
> org.apache.nifi.toolkit.cli.impl.client.nifi.impl.JerseyNiFiClient$Builder.build(JerseyNiFiClient.java:349)
> at
> org.apache.nifi.toolkit.cli.impl.client.NiFiClientFactory.createClient(NiFiClientFactory.java:105)
> at
> org.apache.nifi.toolkit.cli.impl.client.NiFiClientFactory.createClient(NiFiClientFactory.java:44)
> at
> org.apache.nifi.toolkit.cli.impl.command.nifi.AbstractNiFiCommand.doExecute(AbstractNiFiCommand.java:62)
> at
> org.apache.nifi.toolkit.cli.impl.command.AbstractPropertyCommand.execute(AbstractPropertyCommand.java:74)
> at
> org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.processCommand(CommandProcessor.java:252)
> at
> org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.processGroupCommand(CommandProcessor.java:233)
> at
> org.apache.nifi.toolkit.cli.impl.command.CommandProcessor.process(CommandProcessor.java:188)
> at
> org.apache.nifi.toolkit.cli.CLIMain.runSingleCommand(CLIMain.java:145)
> at org.apache.nifi.toolkit.cli.CLIMain.main(CLIMain.java:72)
> Caused by: java.lang.ClassNotFoundException:
> javax.xml.bind.annotation.XmlElement
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 15 more{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-6808) Use KeytabCredentialsService in HWX Schema Registry Service
[ https://issues.apache.org/jira/browse/NIFI-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6808: -- Resolution: Done Status: Resolved (was: Patch Available) > Use KeytabCredentialsService in HWX Schema Registry Service > --- > > Key: NIFI-6808 > URL: https://issues.apache.org/jira/browse/NIFI-6808 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 1.11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Previously the schema registry client did not provide a way to pass in JAAS > config, so it relied on the JAAS system property. > They recently merged an improvement to the client: > [https://github.com/hortonworks/registry/pull/611] > We should now be able to use a KeytabCredentialService to obtain the > principal and keytab and pass in the appropriate configuration to the client. > We'll have to wait until a new release of their client jar before we can > merge this change. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6833) Provide instance qualification of principals in KeytabCredentialsService
[ https://issues.apache.org/jira/browse/NIFI-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6833: -- Summary: Provide instance qualification of principals in KeytabCredentialsService (was: Provide FQDN qualification of principals in KeytabCredentialsService) > Provide instance qualification of principals in KeytabCredentialsService > > > Key: NIFI-6833 > URL: https://issues.apache.org/jira/browse/NIFI-6833 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Fix For: 1.11.0 > > > A KeytabCredentialsService should be able to qualify a principal or shortname > with the instance on which it is running. > A new property should be added that allows the user to select one of the > following qualification options: > * none > * hostname > * FQDN > If NiFi is running on host "nifi.apache.org" and a *KeytabCredentialsService* > was created with a *Kerberos Principal* property value of "n...@example.com", > the *KeytabCredentialsService*** should be able return a qualified principal, > based on the qualification option: > * none -> "n...@example.com" > * hostname -> "nifi/n...@example.com" > * FQDN -> "nifi/nifi.apache@example.com" > If a shortname is used it should be qualified as the qualification option > indicates: > * none -> "nifi" > * hostname -> "nifi/nifi" > * FQDN -> "nifi/nifi.apache.org" > Validation of the *KeytabCredentialsService* should fail if the principal is > already instance-qualified and "hostname" or "FQDN" is selected for the > qualification option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6833) Provide FQDN qualification of principals in KeytabCredentialsService
Jeff Storck created NIFI-6833: - Summary: Provide FQDN qualification of principals in KeytabCredentialsService Key: NIFI-6833 URL: https://issues.apache.org/jira/browse/NIFI-6833 Project: Apache NiFi Issue Type: Improvement Components: Extensions Affects Versions: 1.9.2 Reporter: Jeff Storck Assignee: Jeff Storck Fix For: 1.11.0 A KeytabCredentialsService should be able to qualify a principal or shortname with the instance on which it is running. A new property should be added that allows the user to select one of the following qualification options: * none * hostname * FQDN If NiFi is running on host "nifi.apache.org" and a *KeytabCredentialsService* was created with a *Kerberos Principal* property value of "n...@example.com", the *KeytabCredentialsService*** should be able return a qualified principal, based on the qualification option: * none -> "n...@example.com" * hostname -> "nifi/n...@example.com" * FQDN -> "nifi/nifi.apache@example.com" If a shortname is used it should be qualified as the qualification option indicates: * none -> "nifi" * hostname -> "nifi/nifi" * FQDN -> "nifi/nifi.apache.org" Validation of the *KeytabCredentialsService* should fail if the principal is already instance-qualified and "hostname" or "FQDN" is selected for the qualification option. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NIFI-6275) ListHDFS with Full Path filter mode regex does not work as intended
[
https://issues.apache.org/jira/browse/NIFI-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6275:
--
Fix Version/s: 1.10.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ListHDFS with Full Path filter mode regex does not work as intended
> ---
>
> Key: NIFI-6275
> URL: https://issues.apache.org/jira/browse/NIFI-6275
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation Website, Extensions
>Affects Versions: 1.8.0, 1.9.0, 1.9.1, 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Minor
> Fix For: 1.10.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When using the *{{Full Path}}* filter mode, the regex is applied to the URI
> returned for each file which includes the scheme and authority (hostname, HA
> namespace, port). For the filter to work across multiple HDFS installations
> (such as a flow used on multiple environments that is retrieved from NiFi
> Registry), the regex filter would have to account for the scheme and
> authority by matching possible scheme and authority values.
> To make it easier for the user, the *{{Full Path}}* filter mode's filter
> regex should only be applied to the path components of the URI, without the
> scheme and authority. This can be done by updating the filter for *{{Full
> Path}}* mode to use:
> [Path.getPathWithoutSchemeAndAuthority(Path)|https://hadoop.apache.org/docs/r3.0.0/api/org/apache/hadoop/fs/Path.html#getPathWithoutSchemeAndAuthority-org.apache.hadoop.fs.Path-].
> This will bring the regex values in line with the other modes, since those
> are only applied to the value of *{{Path.getName()}}*.
> Migration guidance will be needed when this improvement is released.
> Existing regex values for *{{Full Path}}* filter mode that accepted any
> scheme and authority will still work.
> Those that specify a scheme and authority will *_not_* work, and will have
> to be updated to specify only path components.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (NIFI-6694) Travis build is unstable due to Hive3-exec access issue
[ https://issues.apache.org/jira/browse/NIFI-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck resolved NIFI-6694. --- Resolution: Fixed > Travis build is unstable due to Hive3-exec access issue > --- > > Key: NIFI-6694 > URL: https://issues.apache.org/jira/browse/NIFI-6694 > Project: Apache NiFi > Issue Type: Bug > Environment: Travis-CI >Reporter: Joe Witt >Assignee: Jeff Storck >Priority: Critical > Fix For: 1.10.0 > > Time Spent: 50m > Remaining Estimate: 0h > > If this is a result of caching issues/etc.. should we disable caching? I > think this occurred recently and required manual changes to work. > [~jtstorck] what options do we have? > [ERROR] error: error reading > /home/travis/.m2/repository/org/apache/hive/hive-exec/3.1.0/hive-exec-3.1.0.jar; > error in opening zip file > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (groovy-tests) @ > nifi-hive3-processors --- > [INFO] Changes detected - recompiling the module! > [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files > [INFO] Compiling in a forked process using > /home/travis/.m2/repository/org/codehaus/groovy/groovy-eclipse-batch/2.5.4-01/groovy-eclipse-batch-2.5.4-01.jar > [INFO] > [INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) > @ nifi-livy-processors --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ > nifi-livy-processors --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 3 source files to > /home/travis/build/apache/nifi/nifi-nar-bundles/nifi-spark-bundle/nifi-livy-processors/target/test-classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] Failure executing groovy-eclipse compiler: > -- > 1. ERROR in > /home/travis/build/apache/nifi/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/src/test/java/org/apache/nifi/util/orc/TestNiFiOrcUtils.java > (at line 0) > /* > ^ > The type org.apache.hadoop.hive.ql.metadata.Table cannot be resolved. It is > indirectly referenced from required .class files > -- > 1 problem (1 error) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (NIFI-6694) Travis build is unstable due to Hive3-exec access issue
[ https://issues.apache.org/jira/browse/NIFI-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck reopened NIFI-6694: --- Reopened for [https://github.com/apache/nifi/pull/3781] to resolve in unintentional inclusion of Hive 3 modules in the Travis build stage for the ja_JP locale. > Travis build is unstable due to Hive3-exec access issue > --- > > Key: NIFI-6694 > URL: https://issues.apache.org/jira/browse/NIFI-6694 > Project: Apache NiFi > Issue Type: Bug > Environment: Travis-CI >Reporter: Joe Witt >Assignee: Jeff Storck >Priority: Critical > Fix For: 1.10.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > If this is a result of caching issues/etc.. should we disable caching? I > think this occurred recently and required manual changes to work. > [~jtstorck] what options do we have? > [ERROR] error: error reading > /home/travis/.m2/repository/org/apache/hive/hive-exec/3.1.0/hive-exec-3.1.0.jar; > error in opening zip file > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (groovy-tests) @ > nifi-hive3-processors --- > [INFO] Changes detected - recompiling the module! > [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files > [INFO] Compiling in a forked process using > /home/travis/.m2/repository/org/codehaus/groovy/groovy-eclipse-batch/2.5.4-01/groovy-eclipse-batch-2.5.4-01.jar > [INFO] > [INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) > @ nifi-livy-processors --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ > nifi-livy-processors --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 3 source files to > /home/travis/build/apache/nifi/nifi-nar-bundles/nifi-spark-bundle/nifi-livy-processors/target/test-classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] Failure executing groovy-eclipse compiler: > -- > 1. ERROR in > /home/travis/build/apache/nifi/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/src/test/java/org/apache/nifi/util/orc/TestNiFiOrcUtils.java > (at line 0) > /* > ^ > The type org.apache.hadoop.hive.ql.metadata.Table cannot be resolved. It is > indirectly referenced from required .class files > -- > 1 problem (1 error) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-6694) Travis build is unstable due to Hive3-exec access issue
[ https://issues.apache.org/jira/browse/NIFI-6694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939844#comment-16939844 ] Jeff Storck commented on NIFI-6694: --- I'll work on this over the weekend and update the Travis build to skip the Hive 3 portion until we can figure out a better solution. I'll comment on this Jira once I have a PR ready for review. > Travis build is unstable due to Hive3-exec access issue > --- > > Key: NIFI-6694 > URL: https://issues.apache.org/jira/browse/NIFI-6694 > Project: Apache NiFi > Issue Type: Bug > Environment: Travis-CI >Reporter: Joe Witt >Assignee: Jeff Storck >Priority: Critical > Fix For: 1.10.0 > > > If this is a result of caching issues/etc.. should we disable caching? I > think this occurred recently and required manual changes to work. > [~jtstorck] what options do we have? > [ERROR] error: error reading > /home/travis/.m2/repository/org/apache/hive/hive-exec/3.1.0/hive-exec-3.1.0.jar; > error in opening zip file > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (groovy-tests) @ > nifi-hive3-processors --- > [INFO] Changes detected - recompiling the module! > [INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files > [INFO] Compiling in a forked process using > /home/travis/.m2/repository/org/codehaus/groovy/groovy-eclipse-batch/2.5.4-01/groovy-eclipse-batch-2.5.4-01.jar > [INFO] > [INFO] --- maven-resources-plugin:3.0.2:testResources (default-testResources) > @ nifi-livy-processors --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ > nifi-livy-processors --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 3 source files to > /home/travis/build/apache/nifi/nifi-nar-bundles/nifi-spark-bundle/nifi-livy-processors/target/test-classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] Failure executing groovy-eclipse compiler: > -- > 1. ERROR in > /home/travis/build/apache/nifi/nifi-nar-bundles/nifi-hive-bundle/nifi-hive3-processors/src/test/java/org/apache/nifi/util/orc/TestNiFiOrcUtils.java > (at line 0) > /* > ^ > The type org.apache.hadoop.hive.ql.metadata.Table cannot be resolved. It is > indirectly referenced from required .class files > -- > 1 problem (1 error) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (NIFI-6655) Investigate maven-failsafe-plugin version for Java 11 compatibility
Jeff Storck created NIFI-6655: - Summary: Investigate maven-failsafe-plugin version for Java 11 compatibility Key: NIFI-6655 URL: https://issues.apache.org/jira/browse/NIFI-6655 Project: Apache NiFi Issue Type: Sub-task Components: Tools and Build Reporter: Jeff Storck The maven-surefire-plugin was upgraded to 2.22.0, most likely maven-failsafe-plugin should be updated to that version as well. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6655) Investigate maven-failsafe-plugin version for Java 11 compatibility
[ https://issues.apache.org/jira/browse/NIFI-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6655: -- Labels: Java11 (was: ) > Investigate maven-failsafe-plugin version for Java 11 compatibility > --- > > Key: NIFI-6655 > URL: https://issues.apache.org/jira/browse/NIFI-6655 > Project: Apache NiFi > Issue Type: Sub-task > Components: Tools and Build >Reporter: Jeff Storck >Priority: Major > Labels: Java11 > > The maven-surefire-plugin was upgraded to 2.22.0, most likely > maven-failsafe-plugin should be updated to that version as well. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6563) Add support for TLSv1.3 when running on Java 11
[ https://issues.apache.org/jira/browse/NIFI-6563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6563: -- Issue Type: Sub-task (was: Improvement) Parent: NIFI-5174 > Add support for TLSv1.3 when running on Java 11 > --- > > Key: NIFI-6563 > URL: https://issues.apache.org/jira/browse/NIFI-6563 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Tools and Build >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Priority: Major > > Add full support for TLSv1.3 running on Java 11. > Some components currently work (S2S over HTTP, for example) with TLSv1.3. > One issue related to specifying "TLS" for the protocol in an SSLContext is > different (implied) behavior between running on Java 8 and 11, since the > "newest" version of the TLS protocol available on the JVM will be used. > More details will be added upon further analysis. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6563) Add support for TLSv1.3 when running on Java 11
Jeff Storck created NIFI-6563: - Summary: Add support for TLSv1.3 when running on Java 11 Key: NIFI-6563 URL: https://issues.apache.org/jira/browse/NIFI-6563 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, Tools and Build Affects Versions: 1.9.2 Reporter: Jeff Storck Add full support for TLSv1.3 running on Java 11. Some components currently work (S2S over HTTP, for example) with TLSv1.3. One issue related to specifying "TLS" for the protocol in an SSLContext is different (implied) behavior between running on Java 8 and 11, since the "newest" version of the TLS protocol available on the JVM will be used. More details will be added upon further analysis. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-5952) RAW Site-to-Site fails with java.nio.channels.IllegalBlockingModeException
[
https://issues.apache.org/jira/browse/NIFI-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5952:
--
Labels: Java11 (was: )
> RAW Site-to-Site fails with java.nio.channels.IllegalBlockingModeException
> --
>
> Key: NIFI-5952
> URL: https://issues.apache.org/jira/browse/NIFI-5952
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Environment: jdk-11.0.1
>Reporter: Koji Kawamura
>Assignee: Koji Kawamura
>Priority: Critical
> Labels: Java11
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> During the review cycle of NIFI-5820, I found that while HTTP S2S works
> without issue, RAW S2S is failing with following Exception:
> {code:java}
> 2018-12-19 16:19:26,811 ERROR [Site-to-Site Listener] org.apache.nifi.NiFi
> java.nio.channels.IllegalBlockingModeException: null
> at
> java.base/sun.nio.ch.ServerSocketAdaptor.accept(ServerSocketAdaptor.java:121)
> at
> org.apache.nifi.remote.SocketRemoteSiteListener$1.run(SocketRemoteSiteListener.java:125)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {code}
> Despite of the fact that the RAW has been worked with older Java versions, it
> seems current nio usage at RAW S2S is not correct. And JDK 11 starts
> complaining about it.
> Here are few things I've discovered with current NiFi and nio SocketChannel:
> - NiFi accepts RAW S2S client connection with SocketRemoteSiteListener,
> which uses ServerSocketChannel as non-blocking manner [1]
> - But SocketRemoteSiteListener doesn't use Selector API to accept incoming
> connection and transfer data with the channel. This is the cause of above
> exception.
> - SocketRemoteSiteListener spawns new thread when it accepts connection.
> This is how connections are handled with a non-nio, standard Socket
> programming. If we want to use non-blocking NIO, we need to use channels with
> Selector
> - But using non-blocking IO with current NiFi S2S protocol can only add few
> or none benefit by doing so. [2]
> To make RAW S2S work with Java 11, we need either:
> A. Stop using nio packages.
> B. Implement correct nio usage, meaning use Selector IO and probably we need
> another thread pool.
> I'm going to take the approach A above, because B would take much more
> refactoring.
> [1]
> [https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-site-to-site/src/main/java/org/apache/nifi/remote/SocketRemoteSiteListener.java#L120]
> [2]
> [https://stackoverflow.com/questions/12338204/in-java-nio-is-a-selector-useful-for-a-client-socketchannel]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-6561) Certificate compatibility broken for JDK8 build running on JRE11
[
https://issues.apache.org/jira/browse/NIFI-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6561:
--
Issue Type: Sub-task (was: Improvement)
Parent: NIFI-5174
> Certificate compatibility broken for JDK8 build running on JRE11
>
>
> Key: NIFI-6561
> URL: https://issues.apache.org/jira/browse/NIFI-6561
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Security
>Affects Versions: 1.10.0
>Reporter: Nathan Gough
>Priority: Major
> Labels: Java11, certificate, tls
>
> When testing Java 11 build compatibility, I found an issue with TLS
> certificates when using a remote process group looped back to an input port
> on the same cluster. The same certificates were used for JDK8/JRE8,
> JDK8/JRE11, JDK11/JRE11 ie. they contained relevant SAN entries in each case.
> *Building on JDK 1.8.0_172 and run on JRE11.0.5+10 caused exceptions when
> attempting to send to local input port with RPG*:
> {code:java}
> 2019-08-13 18:17:07,946 WARN [Http Site-to-Site PeerSelector]
> o.apache.nifi.remote.client.PeerSelector Could not communicate with
> natog0.com:9551 to determine which nodes exist in the remote NiFi cluster,
> due to javax.net.ssl.SSLPeerUnverifiedException: Certificate for
> doesn't match any of the subject alternative names: [natog1.com]
> 2019-08-13 18:17:07,946 WARN [Http Site-to-Site PeerSelector]
> o.apache.nifi.remote.client.PeerSelector
> org.apache.nifi.remote.client.PeerSelector@6d5e02f8 Unable to refresh Remote
> Group's peers due to Unable to communicate with remote NiFi cluster in order
> to determine which nodes exist in the remote cluster{code}
> But did not see this error on the matching builds (JDK8/JRE8, JDK11/JRE11).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-6561) Certificate compatibility broken for JDK8 build running on JRE11
[
https://issues.apache.org/jira/browse/NIFI-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6561:
--
Labels: Java11 certificate tls (was: certificate tls)
> Certificate compatibility broken for JDK8 build running on JRE11
>
>
> Key: NIFI-6561
> URL: https://issues.apache.org/jira/browse/NIFI-6561
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Security
>Affects Versions: 1.10.0
>Reporter: Nathan Gough
>Priority: Major
> Labels: Java11, certificate, tls
>
> When testing Java 11 build compatibility, I found an issue with TLS
> certificates when using a remote process group looped back to an input port
> on the same cluster. The same certificates were used for JDK8/JRE8,
> JDK8/JRE11, JDK11/JRE11 ie. they contained relevant SAN entries in each case.
> *Building on JDK 1.8.0_172 and run on JRE11.0.5+10 caused exceptions when
> attempting to send to local input port with RPG*:
> {code:java}
> 2019-08-13 18:17:07,946 WARN [Http Site-to-Site PeerSelector]
> o.apache.nifi.remote.client.PeerSelector Could not communicate with
> natog0.com:9551 to determine which nodes exist in the remote NiFi cluster,
> due to javax.net.ssl.SSLPeerUnverifiedException: Certificate for
> doesn't match any of the subject alternative names: [natog1.com]
> 2019-08-13 18:17:07,946 WARN [Http Site-to-Site PeerSelector]
> o.apache.nifi.remote.client.PeerSelector
> org.apache.nifi.remote.client.PeerSelector@6d5e02f8 Unable to refresh Remote
> Group's peers due to Unable to communicate with remote NiFi cluster in order
> to determine which nodes exist in the remote cluster{code}
> But did not see this error on the matching builds (JDK8/JRE8, JDK11/JRE11).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-5174) NiFi Compatibility with Java 11
[ https://issues.apache.org/jira/browse/NIFI-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5174: -- Summary: NiFi Compatibility with Java 11 (was: NiFi Compatibility with 11) > NiFi Compatibility with Java 11 > --- > > Key: NIFI-5174 > URL: https://issues.apache.org/jira/browse/NIFI-5174 > Project: Apache NiFi > Issue Type: Task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-5174) NiFi Compatibility with 11
[ https://issues.apache.org/jira/browse/NIFI-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5174: -- Summary: NiFi Compatibility with 11 (was: NiFi Compatibility with Java 9/10/11) > NiFi Compatibility with 11 > -- > > Key: NIFI-5174 > URL: https://issues.apache.org/jira/browse/NIFI-5174 > Project: Apache NiFi > Issue Type: Task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6557) Build on master fails for Java 11 builds due RocksDB JNI Issues
[ https://issues.apache.org/jira/browse/NIFI-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908243#comment-16908243 ] Jeff Storck edited comment on NIFI-6557 at 8/15/19 4:19 PM: [~joewitt], what version of Java 11 are you using? If it's AdoptOpenJDK 11.0.4, there is an issue with loading native libraries on OSX. You can use AdoptOpenJDK 11.0.3 until a new release of 11.0.4 has been made. Since this is only an issue on OSX, the Travis build will not run into since it's linux-based and uses AdoptOpenJDK 11.0.4. To downgrade to AdoptOpenJDK 11.0.3, you can follow the instructions in this comment: [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211#issuecomment-521392147] A couple references with the issue: * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1206] * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211] And the PR to fix it, which has been merged: [https://github.com/AdoptOpenJDK/openjdk-build/pull/1207] Hopefully the fixed version will be released soon. was (Author: jtstorck): [~joewitt], what version of Java 11 are you using? If it's AdoptOpenJDK 11.0.4, there is an issue with loading native libraries on OSX. You can use AdoptOpenJDK 11.0.3 until a new release of 11.0.4 has been made. Since this is only an issue on OSX, the Travis build will not run into this issue, since it's linux-based and uses AdoptOpenJDK 11.0.4. To downgrade to AdoptOpenJDK 11.0.3, you can follow the instructions in this comment: [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211#issuecomment-521392147] A couple references with the issue: * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1206] * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211] And the PR to fix it, which has been merged: [https://github.com/AdoptOpenJDK/openjdk-build/pull/1207] Hopefully the fixed version will be released soon. > Build on master fails for Java 11 builds due RocksDB JNI Issues > --- > > Key: NIFI-6557 > URL: https://issues.apache.org/jira/browse/NIFI-6557 > Project: Apache NiFi > Issue Type: Bug >Reporter: Joseph Witt >Priority: Blocker > Labels: Java11 > Fix For: 1.10.0 > > > [~jtstorck] recently got the Java 11 build for NiFi working and it was merged. > [~devriesb] recently got the RocksDB flowfile impl commited. However, it > doesn't appear to work on Java 11 builds. > This needs to be resolved as we need Java 11 builds to work going forward. > Can you two please coordinate and resolve. > [ERROR] Tests run: 10, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: > 1.004 s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome > [ERROR] testColumnFamilies(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.54 s <<< ERROR! > java.lang.UnsatisfiedLinkError: > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > > dlopen(/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib, > 1): no suitable image found. Did find: > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > code signature in > (/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib) > not valid for use in process using Library Validation: mapped file has no > cdhash, completely unsigned? Code has to be at least ad-hoc signed. > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > stat() failed with errno=38 > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:163) > [ERROR] testWaitForSync(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.004 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:260) > [ERROR] > testWaitForSyncWithValue(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.003 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:291) > [ERROR] testCounterIncrement(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(TestRocksDBMetronome.java:241) > [ERROR] testPutGetDelete(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could
[jira] [Comment Edited] (NIFI-6557) Build on master fails for Java 11 builds due RocksDB JNI Issues
[ https://issues.apache.org/jira/browse/NIFI-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908243#comment-16908243 ] Jeff Storck edited comment on NIFI-6557 at 8/15/19 4:18 PM: [~joewitt], what version of Java 11 are you using? If it's AdoptOpenJDK 11.0.4, there is an issue with loading native libraries on OSX. You can use AdoptOpenJDK 11.0.3 until a new release of 11.0.4 has been made. Since this is only an issue on OSX, the Travis build will not run into this issue, since it's linux-based and uses AdoptOpenJDK 11.0.4. To downgrade to AdoptOpenJDK 11.0.3, you can follow the instructions in this comment: [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211#issuecomment-521392147] A couple references with the issue: * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1206] * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211] And the PR to fix it, which has been merged: [https://github.com/AdoptOpenJDK/openjdk-build/pull/1207] Hopefully the fixed version will be released soon. was (Author: jtstorck): [~joewitt], what version of Java 11 are you using? If it's AdoptOpenJDK 11.0.4, there is an issue with loading native libraries on OSX. You can use AdoptOpenJDK 11.0.3 until a new release of 11.0.4 has been made. To downgrade to AdoptOpenJDK 11.0.3, you can follow the instructions in this comment: [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211#issuecomment-521392147] A couple references with the issue: * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1206] * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211] And the PR to fix it, which has been merged: [https://github.com/AdoptOpenJDK/openjdk-build/pull/1207] Hopefully the fixed version will be released soon. > Build on master fails for Java 11 builds due RocksDB JNI Issues > --- > > Key: NIFI-6557 > URL: https://issues.apache.org/jira/browse/NIFI-6557 > Project: Apache NiFi > Issue Type: Bug >Reporter: Joseph Witt >Priority: Blocker > Labels: Java11 > Fix For: 1.10.0 > > > [~jtstorck] recently got the Java 11 build for NiFi working and it was merged. > [~devriesb] recently got the RocksDB flowfile impl commited. However, it > doesn't appear to work on Java 11 builds. > This needs to be resolved as we need Java 11 builds to work going forward. > Can you two please coordinate and resolve. > [ERROR] Tests run: 10, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: > 1.004 s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome > [ERROR] testColumnFamilies(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.54 s <<< ERROR! > java.lang.UnsatisfiedLinkError: > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > > dlopen(/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib, > 1): no suitable image found. Did find: > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > code signature in > (/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib) > not valid for use in process using Library Validation: mapped file has no > cdhash, completely unsigned? Code has to be at least ad-hoc signed. > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > stat() failed with errno=38 > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:163) > [ERROR] testWaitForSync(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.004 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:260) > [ERROR] > testWaitForSyncWithValue(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.003 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:291) > [ERROR] testCounterIncrement(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(TestRocksDBMetronome.java:241) > [ERROR] testPutGetDelete(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at >
[jira] [Commented] (NIFI-6557) Build on master fails for Java 11 builds due RocksDB JNI Issues
[ https://issues.apache.org/jira/browse/NIFI-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908243#comment-16908243 ] Jeff Storck commented on NIFI-6557: --- [~joewitt], what version of Java 11 are you using? If it's AdoptOpenJDK 11.0.4, there is an issue with loading native libraries on OSX. You can use AdoptOpenJDK 11.0.3 until a new release of 11.0.4 has been made. To downgrade to AdoptOpenJDK 11.0.3, you can follow the instructions in this comment: [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211#issuecomment-521392147] A couple references with the issue: * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1206] * [https://github.com/AdoptOpenJDK/openjdk-build/issues/1211] And the PR to fix it, which has been merged: [https://github.com/AdoptOpenJDK/openjdk-build/pull/1207] Hopefully the fixed version will be released soon. > Build on master fails for Java 11 builds due RocksDB JNI Issues > --- > > Key: NIFI-6557 > URL: https://issues.apache.org/jira/browse/NIFI-6557 > Project: Apache NiFi > Issue Type: Bug >Reporter: Joseph Witt >Priority: Blocker > Labels: Java11 > Fix For: 1.10.0 > > > [~jtstorck] recently got the Java 11 build for NiFi working and it was merged. > [~devriesb] recently got the RocksDB flowfile impl commited. However, it > doesn't appear to work on Java 11 builds. > This needs to be resolved as we need Java 11 builds to work going forward. > Can you two please coordinate and resolve. > [ERROR] Tests run: 10, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: > 1.004 s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome > [ERROR] testColumnFamilies(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.54 s <<< ERROR! > java.lang.UnsatisfiedLinkError: > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > > dlopen(/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib, > 1): no suitable image found. Did find: > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > code signature in > (/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib) > not valid for use in process using Library Validation: mapped file has no > cdhash, completely unsigned? Code has to be at least ad-hoc signed. > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > stat() failed with errno=38 > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:163) > [ERROR] testWaitForSync(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.004 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:260) > [ERROR] > testWaitForSyncWithValue(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.003 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:291) > [ERROR] testCounterIncrement(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(TestRocksDBMetronome.java:241) > [ERROR] testPutGetDelete(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutGetDelete(TestRocksDBMetronome.java:98) > [ERROR] testPutClosed(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.002 s <<< ERROR! > java.lang.Exception: Unexpected exception, > expected but > was > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutClosed(TestRocksDBMetronome.java:148) > [ERROR] testPutGetConfiguration(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutGetConfiguration(TestRocksDBMetronome.java:122) > [ERROR] testPutBeforeInit(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.04 s <<< ERROR! > java.lang.Exception: Unexpected exception, > expected but > was > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutBeforeInit(TestRocksDBMetronome.java:138) > [ERROR]
[jira] [Updated] (NIFI-6557) Build on master fails for Java 11 builds due RocksDB JNI Issues
[ https://issues.apache.org/jira/browse/NIFI-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6557: -- Labels: Java11 (was: ) > Build on master fails for Java 11 builds due RocksDB JNI Issues > --- > > Key: NIFI-6557 > URL: https://issues.apache.org/jira/browse/NIFI-6557 > Project: Apache NiFi > Issue Type: Bug >Reporter: Joseph Witt >Priority: Blocker > Labels: Java11 > Fix For: 1.10.0 > > > [~jtstorck] recently got the Java 11 build for NiFi working and it was merged. > [~devriesb] recently got the RocksDB flowfile impl commited. However, it > doesn't appear to work on Java 11 builds. > This needs to be resolved as we need Java 11 builds to work going forward. > Can you two please coordinate and resolve. > [ERROR] Tests run: 10, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: > 1.004 s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome > [ERROR] testColumnFamilies(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.54 s <<< ERROR! > java.lang.UnsatisfiedLinkError: > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > > dlopen(/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib, > 1): no suitable image found. Did find: > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > code signature in > (/private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib) > not valid for use in process using Library Validation: mapped file has no > cdhash, completely unsigned? Code has to be at least ad-hoc signed. > > /private/var/folders/16/93g5x2rn1bz04szc2t62xcrmgp/T/librocksdbjni6839704530639209130.jnilib: > stat() failed with errno=38 > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:163) > [ERROR] testWaitForSync(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.004 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:260) > [ERROR] > testWaitForSyncWithValue(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.003 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:291) > [ERROR] testCounterIncrement(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(TestRocksDBMetronome.java:241) > [ERROR] testPutGetDelete(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutGetDelete(TestRocksDBMetronome.java:98) > [ERROR] testPutClosed(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.002 s <<< ERROR! > java.lang.Exception: Unexpected exception, > expected but > was > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutClosed(TestRocksDBMetronome.java:148) > [ERROR] testPutGetConfiguration(org.apache.nifi.rocksdb.TestRocksDBMetronome) > Time elapsed: 0.002 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutGetConfiguration(TestRocksDBMetronome.java:122) > [ERROR] testPutBeforeInit(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.04 s <<< ERROR! > java.lang.Exception: Unexpected exception, > expected but > was > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutBeforeInit(TestRocksDBMetronome.java:138) > [ERROR] testIterator(org.apache.nifi.rocksdb.TestRocksDBMetronome) Time > elapsed: 0.003 s <<< ERROR! > java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB > at > org.apache.nifi.rocksdb.TestRocksDBMetronome.testIterator(TestRocksDBMetronome.java:214) > [INFO] > [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ > nifi-druid-controller-service-api --- > [INFO] Deleting > /Users/jwitt/development/nifi.git/nifi-nar-bundles/nifi-druid-bundle/nifi-druid-controller-service-api/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ > nifi-druid-controller-service-api --- > [INFO] > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven) @ >
[jira] [Updated] (NIFI-5505) Need Travis CI for building NiFi on Java 11
[ https://issues.apache.org/jira/browse/NIFI-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5505: -- Summary: Need Travis CI for building NiFi on Java 11 (was: Need CI for building NiFi on Java 11) > Need Travis CI for building NiFi on Java 11 > --- > > Key: NIFI-5505 > URL: https://issues.apache.org/jira/browse/NIFI-5505 > Project: Apache NiFi > Issue Type: Sub-task > Components: Tools and Build >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > In addition to the multi-language Java 1.8 builds that are currently > integrated into our CI with Travis, builds should be triggered for Java 11. > Appveyor should have a Java 11 build as well. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-5505) Need Travis CI for building NiFi on Java 11
[ https://issues.apache.org/jira/browse/NIFI-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5505: -- Description: In addition to the multi-language Java 1.8 builds that are currently integrated into our CI with Travis, builds should be triggered for Java 11. (was: In addition to the multi-language Java 1.8 builds that are currently integrated into our CI with Travis, builds should be triggered for Java 11. Appveyor should have a Java 11 build as well.) > Need Travis CI for building NiFi on Java 11 > --- > > Key: NIFI-5505 > URL: https://issues.apache.org/jira/browse/NIFI-5505 > Project: Apache NiFi > Issue Type: Sub-task > Components: Tools and Build >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > In addition to the multi-language Java 1.8 builds that are currently > integrated into our CI with Travis, builds should be triggered for Java 11. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6529) Fix tests that fail when user.langage and user.region are not set to "en" and "US" respectively
[
https://issues.apache.org/jira/browse/NIFI-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6529:
--
Status: Patch Available (was: In Progress)
> Fix tests that fail when user.langage and user.region are not set to "en"
> and "US" respectively
>
>
> Key: NIFI-6529
> URL: https://issues.apache.org/jira/browse/NIFI-6529
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Some tests are failing when {{user.language}} and {{user.region}} are set to
> values other than {{en}} and {{US}} respectively.
> The following test failures were initially observed (from the builds with
> fr_FR and ja_JP locales, others exist in those builds):
> {code:java}
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043
> s <<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
> [ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
> elapsed: 0.042 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
> at
> org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
> {code}
> {code:java}
> [ERROR]
> testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
> Time elapsed: 0.195 s <<< FAILURE!
> java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]>
> but was:<6:55 [午後]>
> at
> org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
> Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55
> [午後]>
> at
> org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.lambda$testPutElasticSearchOnTriggerIndex$0(TestPutElasticsearchHttpRecord.java:76)
> {code}
>
> The Travis CI build's configuration currently does not properly run tests
> with a non-en_US locale. This will be resolved in NIFI-5505.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-6529) Fix tests that fail when user.langage and user.region are not set to "en" and "US" respectively
[
https://issues.apache.org/jira/browse/NIFI-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6529:
--
Description:
Some tests are failing when {{user.language}} and {{user.region}} are set to
values other than {{en}} and {{US}} respectively.
The following test failures were initially observed (from the builds with fr_FR
and ja_JP locales, others exist in those builds):
{code:java}
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043 s
<<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
[ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
elapsed: 0.042 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
at
org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
{code}
{code:java}
[ERROR]
testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
Time elapsed: 0.195 s <<< FAILURE!
java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]> but
was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.lambda$testPutElasticSearchOnTriggerIndex$0(TestPutElasticsearchHttpRecord.java:76)
{code}
The Travis CI build's configuration currently does not properly run tests with
a non-en_US locale. This will be resolved in NIFI-5505.
was:
Some tests are failing when {{user.language}} and {{user.region}} are set to
values other than {{en}} and {{US}} respectively.
The following test failures were observed:
{code:java}
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043 s
<<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
[ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
elapsed: 0.042 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
at
org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
{code}
{code:java}
[ERROR]
testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
Time elapsed: 0.195 s <<< FAILURE!
java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]> but
was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.lambda$testPutElasticSearchOnTriggerIndex$0(TestPutElasticsearchHttpRecord.java:76)
{code}
The Travis CI build's configuration currently does not properly run tests with
a non-en_US locale. This will be resolved in NIFI-5505.
> Fix tests that fail when user.langage and user.region are not set to "en"
> and "US" respectively
>
>
> Key: NIFI-6529
> URL: https://issues.apache.org/jira/browse/NIFI-6529
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> Some tests are failing when {{user.language}} and {{user.region}} are set to
> values other than {{en}} and {{US}} respectively.
> The following test failures were initially observed (from the builds with
> fr_FR and ja_JP locales, others exist in those builds):
> {code:java}
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043
> s <<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
> [ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
> elapsed: 0.042 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
> at
> org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
> {code}
> {code:java}
> [ERROR]
> testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
> Time elapsed: 0.195 s <<< FAILURE!
> java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]>
> but was:<6:55 [午後]>
> at
> org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
> Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55
> [午後]>
> at
>
[jira] [Updated] (NIFI-6529) Fix tests that fail when user.langage and user.region are not set to "en" and "US" respectively
[
https://issues.apache.org/jira/browse/NIFI-6529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6529:
--
Description:
Some tests are failing when {{user.language}} and {{user.region}} are set to
values other than {{en}} and {{US}} respectively.
The following test failures were observed:
{code:java}
[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043 s
<<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
[ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
elapsed: 0.042 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
at
org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
{code}
{code:java}
[ERROR]
testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
Time elapsed: 0.195 s <<< FAILURE!
java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]> but
was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.lambda$testPutElasticSearchOnTriggerIndex$0(TestPutElasticsearchHttpRecord.java:76)
{code}
The Travis CI build's configuration currently does not properly run tests with
a non-en_US locale. This will be resolved in NIFI-5505.
was:
Some tests are failing when {{user.language}} and {{user.region}} are set to
values other than {{en}} and {{US}} respectively.
The following test failures were observed:
|[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043
s <<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
[ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
elapsed: 0.042 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
at
org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)|
|[ERROR]
testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
Time elapsed: 0.195 s <<< FAILURE!
java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]>
but was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55
[午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.lambda$testPutElasticSearchOnTriggerIndex$0(TestPutElasticsearchHttpRecord.java:76)|
The Travis CI build's configuration currently does not properly run tests with
a non-en_US locale. This will be resolved in NIFI-5505.
> Fix tests that fail when user.langage and user.region are not set to "en"
> and "US" respectively
>
>
> Key: NIFI-6529
> URL: https://issues.apache.org/jira/browse/NIFI-6529
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> Some tests are failing when {{user.language}} and {{user.region}} are set to
> values other than {{en}} and {{US}} respectively.
> The following test failures were observed:
> {code:java}
> [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043
> s <<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
> [ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
> elapsed: 0.042 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
> at
> org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
> {code}
> {code:java}
> [ERROR]
> testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
> Time elapsed: 0.195 s <<< FAILURE!
> java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]>
> but was:<6:55 [午後]>
> at
> org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
> Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55
> [午後]>
> at
> org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.lambda$testPutElasticSearchOnTriggerIndex$0(TestPutElasticsearchHttpRecord.java:76)
> {code}
>
> The Travis CI build's configuration currently does not properly run tests
> with a
[jira] [Created] (NIFI-6529) Fix tests that fail when user.langage and user.region are not set to "en" and "US" respectively
Jeff Storck created NIFI-6529:
-
Summary: Fix tests that fail when user.langage and user.region
are not set to "en" and "US" respectively
Key: NIFI-6529
URL: https://issues.apache.org/jira/browse/NIFI-6529
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework, Extensions
Affects Versions: 1.9.2
Reporter: Jeff Storck
Assignee: Jeff Storck
Some tests are failing when {{user.language}} and {{user.region}} are set to
values other than {{en}} and {{US}} respectively.
The following test failures were observed:
|[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.043
s <<< FAILURE! - in org.apache.nifi.processor.TestFormatUtils
[ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils) Time
elapsed: 0.042 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<10[.]4 bytes> but was:<10[,]4 bytes>
at
org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)|
|[ERROR]
testPutElasticSearchOnTriggerIndex(org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord)
Time elapsed: 0.195 s <<< FAILURE!
java.lang.AssertionError: org.junit.ComparisonFailure: expected:<6:55 [PM]>
but was:<6:55 [午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.testPutElasticSearchOnTriggerIndex(TestPutElasticsearchHttpRecord.java:114)
Caused by: org.junit.ComparisonFailure: expected:<6:55 [PM]> but was:<6:55
[午後]>
at
org.apache.nifi.processors.elasticsearch.TestPutElasticsearchHttpRecord.lambda$testPutElasticSearchOnTriggerIndex$0(TestPutElasticsearchHttpRecord.java:76)|
The Travis CI build's configuration currently does not properly run tests with
a non-en_US locale. This will be resolved in NIFI-5505.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-6479) Fix TestJdbcCommon timezone issues
[
https://issues.apache.org/jira/browse/NIFI-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6479:
--
Status: Patch Available (was: Open)
Submitted [PR 3630|https://github.com/apache/nifi/pull/3630] to resolve the
timezone issues.
> Fix TestJdbcCommon timezone issues
> --
>
> Key: NIFI-6479
> URL: https://issues.apache.org/jira/browse/NIFI-6479
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing
> with timezone issues.
> The workaround for this issue is to add
> {code:java}
> -Dmaven.surefire.arguments=-Duser.timezone=UTC
> {code}
> when running maven. If {{-Dmaven.surefire.arguments}} is already specified
> as part of the build, add {{-Duser.timezone=UTC}} to the value supplied to
> that parameter.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-5505) Need CI for building NiFi on Java 11
[ https://issues.apache.org/jira/browse/NIFI-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5505: -- Description: In addition to the multi-language Java 1.8 builds that are currently integrated into our CI with Travis, builds should be triggered for Java 11. Appveyor should have a Java 11 build as well. was:In addition to the multi-language Java 1.8 builds that are currently integrated into our CI with Travis, builds should be triggered for Java 9+. > Need CI for building NiFi on Java 11 > > > Key: NIFI-5505 > URL: https://issues.apache.org/jira/browse/NIFI-5505 > Project: Apache NiFi > Issue Type: Sub-task > Components: Tools and Build >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the multi-language Java 1.8 builds that are currently > integrated into our CI with Travis, builds should be triggered for Java 11. > Appveyor should have a Java 11 build as well. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-5505) Need CI for building NiFi on Java 11
[ https://issues.apache.org/jira/browse/NIFI-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5505: -- Summary: Need CI for building NiFi on Java 11 (was: Need CI for NiFi building on Java 9+) > Need CI for building NiFi on Java 11 > > > Key: NIFI-5505 > URL: https://issues.apache.org/jira/browse/NIFI-5505 > Project: Apache NiFi > Issue Type: Sub-task > Components: Tools and Build >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the multi-language Java 1.8 builds that are currently > integrated into our CI with Travis, builds should be triggered for Java 9+. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-5505) Need CI for NiFi building on Java 9+
[ https://issues.apache.org/jira/browse/NIFI-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck reassigned NIFI-5505: - Assignee: Jeff Storck > Need CI for NiFi building on Java 9+ > > > Key: NIFI-5505 > URL: https://issues.apache.org/jira/browse/NIFI-5505 > Project: Apache NiFi > Issue Type: Sub-task > Components: Tools and Build >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > In addition to the multi-language Java 1.8 builds that are currently > integrated into our CI with Travis, builds should be triggered for Java 9+. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6479) Fix TestJdbcCommon timezone issues
[
https://issues.apache.org/jira/browse/NIFI-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6479:
--
Description:
TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing
with timezone issues.
The workaround for this issue is to add
{code:java}
-Dmaven.surefire.arguments=-Duser.timezone=UTC
{code}
when running maven. If {{-Dmaven.surefire.arguments}} is already specified as
part of the build, add {{-Duser.timezone=UTC}} to the value supplied to that
parameter.
was:
TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing
with timezone issues.
The workaround for this error is to add
{code:java}
-Dmaven.surefire.arguments=-Duser.timezone=UTC
{code}
when running maven. If {{-Dmaven.surefire.arguments}} is already specified as
part of the build, add {{-Duser.timezone=UTC}} to the value supplied to that
parameter.
> Fix TestJdbcCommon timezone issues
> --
>
> Key: NIFI-6479
> URL: https://issues.apache.org/jira/browse/NIFI-6479
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing
> with timezone issues.
> The workaround for this issue is to add
> {code:java}
> -Dmaven.surefire.arguments=-Duser.timezone=UTC
> {code}
> when running maven. If {{-Dmaven.surefire.arguments}} is already specified
> as part of the build, add {{-Duser.timezone=UTC}} to the value supplied to
> that parameter.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6479) Fix TestJdbcCommon timezone issues
[
https://issues.apache.org/jira/browse/NIFI-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897740#comment-16897740
]
Jeff Storck commented on NIFI-6479:
---
[~pcgrenier] I updated the description of this JIRA with a workaround if you
encounter this issue.
> Fix TestJdbcCommon timezone issues
> --
>
> Key: NIFI-6479
> URL: https://issues.apache.org/jira/browse/NIFI-6479
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing
> with timezone issues.
> The workaround for this error is to add
> {code:java}
> -Dmaven.surefire.arguments=-Duser.timezone=UTC
> {code}
> when running maven. If {{-Dmaven.surefire.arguments}} is already specified
> as part of the build, add {{-Duser.timezone=UTC}} to the value supplied to
> that parameter.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-6479) Fix TestJdbcCommon timezone issues
[
https://issues.apache.org/jira/browse/NIFI-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6479:
--
Description:
TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing
with timezone issues.
The workaround for this error is to add
{code:java}
-Dmaven.surefire.arguments=-Duser.timezone=UTC
{code}
when running maven. If {{-Dmaven.surefire.arguments}} is already specified as
part of the build, add {{-Duser.timezone=UTC}} to the value supplied to that
parameter.
was:TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is
failing with timezone issues.
> Fix TestJdbcCommon timezone issues
> --
>
> Key: NIFI-6479
> URL: https://issues.apache.org/jira/browse/NIFI-6479
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
>
> TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing
> with timezone issues.
> The workaround for this error is to add
> {code:java}
> -Dmaven.surefire.arguments=-Duser.timezone=UTC
> {code}
> when running maven. If {{-Dmaven.surefire.arguments}} is already specified
> as part of the build, add {{-Duser.timezone=UTC}} to the value supplied to
> that parameter.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (NIFI-6479) Fix TestJdbcCommon timezone issues
Jeff Storck created NIFI-6479: - Summary: Fix TestJdbcCommon timezone issues Key: NIFI-6479 URL: https://issues.apache.org/jira/browse/NIFI-6479 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 1.9.2 Reporter: Jeff Storck Assignee: Jeff Storck TestJdbcCommon.testConvertToAvroStreamForDateTimeAsLogicalType() is failing with timezone issues. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-5176) NiFi needs to be buildable on Java 11
[
https://issues.apache.org/jira/browse/NIFI-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5176:
--
Description:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.8.1, groovy-eclipse-compiler:3.4.0-01, and
groovy-eclipse-batch:2.5.4-01 (See NIFI-5254 for reference)|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.5.4-01 and groovy-all:2.5.4 (See NIFI-5254 for
reference)|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.2 and
mockito:2.28.2 (See NIFI-6360 for reference)|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
was:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.8.0, groovy-eclipse-compiler:3.4.0-01, and
groovy-eclipse-batch:2.5.4-01 (See NIFI-5254 for reference)|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.5.4-01 and groovy-all:2.5.4 (See NIFI-5254 for
reference)|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.2 and
mockito:2.28.2 (See NIFI-6360 for reference)|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
> NiFi needs to be
[jira] [Updated] (NIFI-5254) Upgrade to Groovy 2.5.0
[ https://issues.apache.org/jira/browse/NIFI-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5254: -- Resolution: Done Fix Version/s: 1.10.0 Status: Resolved (was: Patch Available) > Upgrade to Groovy 2.5.0 > --- > > Key: NIFI-5254 > URL: https://issues.apache.org/jira/browse/NIFI-5254 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike Thomsen >Assignee: Mike Thomsen >Priority: Major > Labels: Java11 > Fix For: 1.10.0 > > Time Spent: 7h 10m > Remaining Estimate: 0h > > Groovy 2.5 has been released and support for it should be added. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6405) GetHDFSFileInfo ignores files in the root/start directory
[ https://issues.apache.org/jira/browse/NIFI-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6405: -- Resolution: Fixed Fix Version/s: 1.10.0 Status: Resolved (was: Patch Available) Merged to master in commit 3d21059e95920ded8034e0bdc7d318571ffef54a. > GetHDFSFileInfo ignores files in the root/start directory > - > > Key: NIFI-6405 > URL: https://issues.apache.org/jira/browse/NIFI-6405 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0, 1.7.1, 1.9.2 >Reporter: Ferenc Szabo >Assignee: Ferenc Szabo >Priority: Major > Fix For: 1.10.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The processor is not listing any file in the directory set in the "Full path" > (gethdfsfileinfo-full-path) property. > Only files in subdirectories are listed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5176) NiFi needs to be buildable on Java 11
[
https://issues.apache.org/jira/browse/NIFI-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5176:
--
Description:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.8.0, groovy-eclipse-compiler:3.4.0-01, and
groovy-eclipse-batch:2.5.4-01 (See NIFI-5254 for reference)|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.5.4-01 and groovy-all:2.5.4 (See NIFI-5254 for
reference)|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.2 and
mockito:2.28.2 (See NIFI-6360 for reference)|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
was:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.8.0, groovy-eclipse-compiler:3.4.0-01, and
groovy-eclipse-batch:2.5.4-01|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.5.4-01 and groovy-all:2.5.4|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.2 and
mockito:2.28.2 (See NIFI-6360 for reference)|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
> NiFi needs to be buildable on Java 11
> -
>
>
[jira] [Updated] (NIFI-5176) NiFi needs to be buildable on Java 11
[
https://issues.apache.org/jira/browse/NIFI-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5176:
--
Description:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.8.0, groovy-eclipse-compiler:3.4.0-01, and
groovy-eclipse-batch:2.5.4-01|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.5.4-01 and groovy-all:2.5.4|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.2 and
mockito:2.28.2 (See NIFI-6360 for reference)|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
was:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.8.0, groovy-eclipse-compiler:3.4.0-01, and
groovy-eclipse-batch:2.5.4-01|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.5.4-01 and groovy-all:2.5.4|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.2 and
mockito:2.28.2|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
> NiFi needs to be buildable on Java 11
> -
>
> Key: NIFI-5176
> URL:
[jira] [Updated] (NIFI-5176) NiFi needs to be buildable on Java 11
[
https://issues.apache.org/jira/browse/NIFI-5176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-5176:
--
Description:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.8.0, groovy-eclipse-compiler:3.4.0-01, and
groovy-eclipse-batch:2.5.4-01|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.5.4-01 and groovy-all:2.5.4|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.2 and
mockito:2.28.2|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
was:
While retaining a source/target comptability of 1.8, NiFi needs to be buildable
on Java 11.
The following issues have been encountered while attempting to run a Java
1.8-built NiFi on Java 11:
||Issue||Solution||
|groovy-eclipse-compiler not working with Java 10|-Switched to gmaven-plus-
Updated to maven-compiler-plugin:3.7.0, groovy-eclipse-compiler:2.9.3-01, and
groovy-eclipse-batch:2.4.15-01|
|Antler3 issue with ambiguous method calls|Explicit cast to ValidationContext
needed in TestHL7Query.java|
|jaxb2-maven-plugin not compatible with Java 9|Switched to maven-jaxb-plugin|
|-nifi-enrich-processors uses package com.sun.jndi.dns, which does not
exist-|-Required addition of- -add-modules=jdk.naming.dns
--add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED, which prevents the
usage of compiling with the --release option (to compile only against public
APIs in the JDK) from being used. Not an optimal solution.-|
|groovy-eclipse-batch:2.4.13-01 could not find JDK base classes|Updated to
groovy-eclipse-batch:2.4.15-01 and grooy-all:2.4.15|
|maven-surefire-plugin:2.20.1 throws null pointer exceptions|Updated to
maven-surefire-plugin:2.22.0|
|okhttp client builder requires X509TrustManager on Java 9+|Added methods to
return TrustManager instances with the SSLContext created by SSLContextFactory
and updated HttpNotificationService to use the paired TrustManager|
|nifi-runtime groovy tests aren't running|Added usage of
build-helper-maven-plugin to explicitly add src/test/groovy to force groovy
compilation of test sources. groovy-eclipse-compiler skips src/test/groovy if
src/test/java doesn't exist, which is the case for nifi-runtime. (See NIFI-5341
for reference)|
|hbase-client depends on jdk.tools:jdk.tools|Excluded this dependency
{color:#f79232}*(needs live testing)* {color}|
|HBase client 1.1.2 does not allow running on Java 9+|Updated to HBase client
1.1.11, passes unit tests (See HBASE-17944 for reference)
*{color:#f79232}(needs live testing){color}*|
|powermock:1.6.5 does not support Java 10|Updated to powermock:2.0.0-beta.5 and
mockito:2.19|
|com.yammer.metrics:metrics-core:2.2.0 does not support Java 10|Upgrading
com.yammer.metrics:metrics-core:2.2.0 to
io.dropwizard.metrics:metrics-jvm:4.0.0 (See NIFI-5373 for reference)|
> NiFi needs to be buildable on Java 11
> -
>
> Key: NIFI-5176
> URL: https://issues.apache.org/jira/browse/NIFI-5176
>
[jira] [Updated] (NIFI-6360) Update Mockito and PowerMock to 2.x
[ https://issues.apache.org/jira/browse/NIFI-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6360: -- Labels: Java11 (was: ) > Update Mockito and PowerMock to 2.x > --- > > Key: NIFI-6360 > URL: https://issues.apache.org/jira/browse/NIFI-6360 > Project: Apache NiFi > Issue Type: Task > Components: Core Framework, Extensions, Tools and Build >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Labels: Java11 > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update to the most recent stable 2.x versions of Mockito and PowerMock. > This is necessary for building NiFi on Java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6196) Upgrade version of Jetty
[
https://issues.apache.org/jira/browse/NIFI-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6196:
--
Labels: Java11 (was: )
> Upgrade version of Jetty
>
>
> Key: NIFI-6196
> URL: https://issues.apache.org/jira/browse/NIFI-6196
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 1.9.2
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Major
> Labels: Java11
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Upgrade version of Jetty to 9.4.15.v20190215 from 9.4.11.v20180605.
> \\
> \\
> This upgrade is needed for building NiFi with Java 11.
> \\
> \\
> ||Issues encountered during upgrade||Resolution||
> |As of Jetty 9.4.15.v20190215, certificate verification has changed.
> Previous to version 9.4.15.v20190215,
> {{org.eclipse.jetty.util.ssl.SslContextFactory.getEndpointIdentificationAlgorithm()}}
> returned {{null}}. As of version 9.4.15.v20190215, that method returns
> {{"HTTPS"}}. This causes the {{SslContextFactory}} to verify the hostname on
> the other end of the connection, regardless of being used by a client or
> server. This works correctly for clients but results in a
> {{CertificateException}} on the server if the client cert does not contain
> the correct SAN. The following Jetty Github issues reference this scenario:
> * [https://github.com/eclipse/jetty.project/issues/3154]
> * [https://github.com/eclipse/jetty.project/issues/3454]
> * [https://github.com/eclipse/jetty.project/issues/3464]
> * [https://github.com/eclipse/jetty.project/issues/3466]|Update server
> SslContextFactory instances use
> {{org.eclipse.jetty.util.ssl.SslContextFactory.setEndpointIdentificationAlgorithm(null)}}|
> |Several tests use the same keystore between client and server:
> * ITestHandleHttpRequest
> * TestInvokeHttpSSL
> * TestInvokeHttpTwoWaySSL
> * TestListenHTTP|Update tests to use a separate keystore for clients|
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-5820) NiFi built with Java 1.8 needs to run on Java 11
[ https://issues.apache.org/jira/browse/NIFI-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5820: -- Labels: Java11 (was: ) > NiFi built with Java 1.8 needs to run on Java 11 > > > Key: NIFI-5820 > URL: https://issues.apache.org/jira/browse/NIFI-5820 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Labels: Java11 > Fix For: 1.10.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5254) Upgrade to Groovy 2.5.0
[ https://issues.apache.org/jira/browse/NIFI-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-5254: -- Labels: Java11 (was: ) > Upgrade to Groovy 2.5.0 > --- > > Key: NIFI-5254 > URL: https://issues.apache.org/jira/browse/NIFI-5254 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mike Thomsen >Assignee: Mike Thomsen >Priority: Major > Labels: Java11 > Time Spent: 4h 10m > Remaining Estimate: 0h > > Groovy 2.5 has been released and support for it should be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6355) Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics
[ https://issues.apache.org/jira/browse/NIFI-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6355: -- Fix Version/s: 1.10.0 > Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics > > > Key: NIFI-6355 > URL: https://issues.apache.org/jira/browse/NIFI-6355 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Fix For: 1.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6354) Missing LICENSE and NOTICE in nifi-kafka-2-0-nar module
[ https://issues.apache.org/jira/browse/NIFI-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6354: -- Fix Version/s: 1.10.0 > Missing LICENSE and NOTICE in nifi-kafka-2-0-nar module > --- > > Key: NIFI-6354 > URL: https://issues.apache.org/jira/browse/NIFI-6354 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Blocker > Fix For: 1.10.0 > > > nifi-kafka-2-0-nar module is missing src/main/resources/META-INF dir, and has > no LICENSE or NOTICE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6355) Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics
[ https://issues.apache.org/jira/browse/NIFI-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6355: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics > > > Key: NIFI-6355 > URL: https://issues.apache.org/jira/browse/NIFI-6355 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6354) Missing LICENSE and NOTICE in nifi-kafka-2-0-nar module
[ https://issues.apache.org/jira/browse/NIFI-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6354: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Missing LICENSE and NOTICE in nifi-kafka-2-0-nar module > --- > > Key: NIFI-6354 > URL: https://issues.apache.org/jira/browse/NIFI-6354 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Blocker > > nifi-kafka-2-0-nar module is missing src/main/resources/META-INF dir, and has > no LICENSE or NOTICE. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6275) ListHDFS with Full Path filter mode regex does not work as intended
[
https://issues.apache.org/jira/browse/NIFI-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Storck updated NIFI-6275:
--
Status: Patch Available (was: Open)
> ListHDFS with Full Path filter mode regex does not work as intended
> ---
>
> Key: NIFI-6275
> URL: https://issues.apache.org/jira/browse/NIFI-6275
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation Website, Extensions
>Affects Versions: 1.9.2, 1.9.1, 1.9.0, 1.8.0
>Reporter: Jeff Storck
>Assignee: Jeff Storck
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When using the *{{Full Path}}* filter mode, the regex is applied to the URI
> returned for each file which includes the scheme and authority (hostname, HA
> namespace, port). For the filter to work across multiple HDFS installations
> (such as a flow used on multiple environments that is retrieved from NiFi
> Registry), the regex filter would have to account for the scheme and
> authority by matching possible scheme and authority values.
> To make it easier for the user, the *{{Full Path}}* filter mode's filter
> regex should only be applied to the path components of the URI, without the
> scheme and authority. This can be done by updating the filter for *{{Full
> Path}}* mode to use:
> [Path.getPathWithoutSchemeAndAuthority(Path)|https://hadoop.apache.org/docs/r3.0.0/api/org/apache/hadoop/fs/Path.html#getPathWithoutSchemeAndAuthority-org.apache.hadoop.fs.Path-].
> This will bring the regex values in line with the other modes, since those
> are only applied to the value of *{{Path.getName()}}*.
> Migration guidance will be needed when this improvement is released.
> Existing regex values for *{{Full Path}}* filter mode that accepted any
> scheme and authority will still work.
> Those that specify a scheme and authority will *_not_* work, and will have
> to be updated to specify only path components.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-6360) Update Mockito and PowerMock to 2.x
[ https://issues.apache.org/jira/browse/NIFI-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6360: -- Status: Patch Available (was: Open) > Update Mockito and PowerMock to 2.x > --- > > Key: NIFI-6360 > URL: https://issues.apache.org/jira/browse/NIFI-6360 > Project: Apache NiFi > Issue Type: Task > Components: Core Framework, Extensions, Tools and Build >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update to the most recent stable 2.x versions of Mockito and PowerMock. > This is necessary for building NiFi on Java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6360) Update Mockito and PowerMock to 2.x
[ https://issues.apache.org/jira/browse/NIFI-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6360: -- Description: Update to the most recent stable 2.x versions of Mockito and PowerMock. This is necessary for building NiFi on Java 11. was: Update to the most recent stable versions of Mockito and PowerMock. This is necessary for building NiFi on Java 11. > Update Mockito and PowerMock to 2.x > --- > > Key: NIFI-6360 > URL: https://issues.apache.org/jira/browse/NIFI-6360 > Project: Apache NiFi > Issue Type: Task > Components: Core Framework, Extensions, Tools and Build >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > > Update to the most recent stable 2.x versions of Mockito and PowerMock. > This is necessary for building NiFi on Java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6360) Update Mockito and PowerMock to 2.x
Jeff Storck created NIFI-6360: - Summary: Update Mockito and PowerMock to 2.x Key: NIFI-6360 URL: https://issues.apache.org/jira/browse/NIFI-6360 Project: Apache NiFi Issue Type: Task Components: Core Framework, Extensions, Tools and Build Affects Versions: 1.9.2 Reporter: Jeff Storck Assignee: Jeff Storck Update to the most recent stable versions of Mockito and PowerMock. This is necessary for building NiFi on Java 11. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6355) Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics
[ https://issues.apache.org/jira/browse/NIFI-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6355: -- Status: Patch Available (was: Open) [PR 3520|https://github.com/apache/nifi/pull/3520] addresses this issue. > Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics > > > Key: NIFI-6355 > URL: https://issues.apache.org/jira/browse/NIFI-6355 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6355) Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics
[ https://issues.apache.org/jira/browse/NIFI-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6355: -- Component/s: Extensions > Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics > > > Key: NIFI-6355 > URL: https://issues.apache.org/jira/browse/NIFI-6355 > Project: Apache NiFi > Issue Type: Task > Components: Extensions >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6355) Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics
[ https://issues.apache.org/jira/browse/NIFI-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6355: -- Affects Version/s: 1.9.2 > Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics > > > Key: NIFI-6355 > URL: https://issues.apache.org/jira/browse/NIFI-6355 > Project: Apache NiFi > Issue Type: Task >Affects Versions: 1.9.2 >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6355) Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics
[ https://issues.apache.org/jira/browse/NIFI-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Storck updated NIFI-6355: -- Summary: Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics (was: Extend NOTICE clause for modules that use yammer/dropwizard metrics) > Extend/include NOTICE clauses for modules that use yammer/dropwizard metrics > > > Key: NIFI-6355 > URL: https://issues.apache.org/jira/browse/NIFI-6355 > Project: Apache NiFi > Issue Type: Task >Reporter: Jeff Storck >Assignee: Jeff Storck >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
