About steven-matison

steven-matison · ‎08-21-2023

Let's take this a different direction... open up a code box in your reply. Choose Preformatted: Insert Lines 0 - 11 here Remove anything sensitive of course.

cjervis · ‎08-21-2023

@learner-loading were you able to resolve your issue? If any of the above posts were the solution please mark the appropriate, as it will make it easier for others to find the answer in the future.

sinRudra · ‎08-18-2023

For information, jira ticket created. https://issues.apache.org/jira/browse/NIFI-11967

steven-matison · ‎08-17-2023

@sree21 You should be able to download the driver and use it anywhere. The license is just for hive endpoint itself. You can find that download page here: https://www.cloudera.com/downloads/connectors/hive/odbc/2-6-1.html

Kiranq · ‎08-17-2023

Thanks. It was an issue with the connection string. It was pointing to another database while my processor was inserting into another database.

steven-matison · ‎08-16-2023

@janvit04 The pattern you need is this: ${input_date:toDate("MM/dd/yyyy hh:mm:ss"):format("yyyy-MM-dd HH:mm:ss")} I did this in a test which you can find here. In this example I have UpdateAttribute with an input attribute called input_date and its string value is "8/6/2023 12:46 am". In next UpdateAttribute i do the toDate and format. With this setup you may need to modify the format in toDate function to match your input string until it gets right format. For example I thought it should be m/d/yyyy but i got right output using MM/dd/yyyy.

StatistiX · ‎08-14-2023

Hi Steven, will do! I leave this topic open for a while in case anyone found a known issue for this combination CDP 7.1.8 + RHEL 8.8 Thanks

JohnSilver · ‎08-09-2023

Hey Matt! I am truly grateful for your answer. You made me realize what I was doing wrong and I learned a lot while reading trough your explanation. I am going to revise the documentation again, as I am realizing that I did not had some concepts crystal clear before. Thanks again and I wish you a good day.

MattWho · ‎08-07-2023

@sam_s0ni Apache NiFi never intended with the context of the NiFi framework to allow parameters to be dynamically accessed within NiFi Expression Language (NEL). The EvaluateElString() exposed a bug in which this was possible while never intended. That bug was addressed in apache NiFi 1.19 thus resulting in what you are seeing. As an alternative, you could store your schemas in an external database and pull those schemas back dynamically based on a FlowFile attribute instead of using Parameter contexts to store those schemas. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt

steven-matison · ‎08-07-2023

@ibrooks Excellent article here. I will definitely be using this in my CML Demos going foward. I just sent a PR w/ some flow improvements you may like to use as well.

Online	Offline
Last Visited	‎06-13-2026 05:03 AM

Member Since	‎02-01-2022 01:27 PM
Last Visited	‎06-13-2026 05:03 AM
Posts	287
Kudos received	102

Cloudera Community

Re: Nifi - Flow Analysis Rules - Possibility to cr...

Re: Apache Nifi Release 2.0 M1 & M2 High CPU Utili...

Re: error nifi connecting as cluster

Re: Difficulty Sending GraphQL POST Requests Using...

Re: Should i have to restart entire cluster if CM ...

Re: How to skip first 10 rows of a csv and read th...

Re: NiFi Site-to-Site example

Re: ListFTP not taking into account french special...

Re: License for Cloudera Hive ODBC driver

Re: Move data from locally installed SQL Server to...

Re: Convert date time to 24 hour format in NiFi

Re: CDP upgrade for RHEL 8.8

Re: (Apache NiFi) - ListSMB + FetchSMB don't work ...

Re: Dynamically references parameters from paramet...

Re: How to call a CML Deployed Model From Apache N...