Member since
07-25-2024
3
Posts
2
Kudos Received
0
Solutions
11-06-2024
02:11 PM
@CommanderLaus Gitlab integration is available in latest version Nifi 2.0 (released few days ago). I was able to import and export flows directly from Gitlab repo. Note: Until Nifi 2.0M4, the file extension is "snapshot", but in 2.0 if you use Gitlab, flow config file extension should be ".json" We need to provide access token of the gitlab repository in Registry controller settings.
... View more
07-26-2024
12:29 AM
1 Kudo
Hi @monica345 , Thanks a lot for your valuable input! We have restarted the NiFi multiple times and find below the list of jar files placed in the NiFi lib folder. Please let us know if there is any additional jar file that needs to be used in NiFi for connecting to Hive. Thanks! slf4j-api-2.0.6.jar nifi-stateless-bootstrap-1.18.0.2.1.5.3000-3.jar nifi-stateless-api-1.18.0.2.1.5.3000-3.jar nifi-server-api-1.18.0.2.1.5.3000-3.jar nifi-runtime-1.18.0.2.1.5.3000-3.jar nifi-property-utils-1.18.0.2.1.5.3000-3.jar nifi-properties-1.18.0.2.1.5.3000-3.jar nifi-nar-utils-1.18.0.2.1.5.3000-3.jar nifi-framework-api-1.18.0.2.1.5.3000-3.jar nifi-api-1.18.0.2.1.5.3000-3.jar logback-core-1.3.5.jar logback-classic-1.3.5.jar log4j-over-slf4j-2.0.6.jar jul-to-slf4j-2.0.6.jar jetty-schemas-5.2.jar jcl-over-slf4j-2.0.6.jar javax.servlet-api-3.1.0.jar aspectjweaver-1.9.6.jar oracle-connector-java.jar mysql-connector-java.jar ojdbc8.jar ojdbc10.jar hive-jdbc-3.1.3000.7.1.7.2000-305.jar libthrift-0.9.3.jar
... View more
07-25-2024
01:12 AM
Hello, @kelly01 wrote: When I use the GETMONGO processor to read source data from MongoDB with the output format set to Standard JSON, it converts the original date value to the local timestamp. However, when using the Extended JSON format, the original date value appears but in a different format. I need one of the following solutions: 1. Original date value in Standard JSON format: The date should appear as "createdAt": "2012-08-27T22:32:56Z". 2. Date format in Extended JSON: The date should appear as {"createdAt": "2012-08-27T22:32:56Z"}. 3. Transformation: Convert the Extended JSON format from "createdAt": {"$date": "2012-08-27T22:32:56Z"} to {"createdAt": "2012-08-27T22:32:56Z"}. Here are examples of the outputs: **Standard JSON output:** [ { "_id": "629f3a565f65e119263fa79e", "id": "46dd1621-910f-4eb6-91a0-5ae609a77b10", "firstName": "kelly", "createdAt": "2012-08-28T10:32:56Z", "modifiedAt": "2024-07-01T18:17:29Z", "suspended": false, "linkedAccounts": [ { "accountNumber": "100000000", "accountType": "SAV", "linkedAt": "2012-08-28T10:36:58Z" } ], "auth0Id": "46dd1621-910f-4eb6-91a0-5ae609a77b10", "gender": "FEMALE" } ] **Extended JSON output:** [ { "_id": {"$oid": "629f3a565f65e119263fa79e"}, "id": "46dd1621-910f-4eb6-91a0-5ae609a77b10", "firstName": "kelly", "createdAt": {"$date": "2012-08-27T22:32:56Z"}, "modifiedAt": {"$date": "2024-07-01T06:17:29.467Z"}, "suspended": false, "linkedAccounts": [ { "accountNumber": "100000000", "accountType": "SAV", "linkedAt": {"$date": "2012-08-27T22:36:58Z"} } ], "auth0Id": "46dd1621-910f-4eb6-91a0-5ae609a77b10", "gender": "FEMALE" } ] Thanks for the help. Your data is coming out in a weird format. You want the dates to look normal, not like a computer wrote them. Here's the deal: The easy way: Use a tool to fix the weird date format after you get the data. The complicated way: Change how you get the data so the dates come out normal from the start. Let me know if you want to try either of these!
... View more