Re: Unable to connect to Confluent Schema Registry with credentials

Thanks, Bryan. NiFi-6576 is created. Thanks, Ali On Wed, Aug 21, 2019 at 12:10 AM Bryan Bende wrote: > I believe it would require a code change to the > ConfluentSchemaRegistry service to have properties for basic auth > username and

Re: Custom Processor Upgrade

Thanks all for the support. We resolved the issue by creating a new nar file itself. It seems the old version code was using some outdated dependencies which was not getting fixed when upgrading the processor. On Thu, Aug 15, 2019 at 2:06 PM James Srinivasan wrote: > I find strace (or procmon

Creating External Hive Table on Parquet Files

Hi, We have a sub Flow - QueryDatabaseTable->SplitAvro->ConvertAvrotoORC->PutHDFS->ReplaceText->PutHQL. We are using ConverAvrotoORC for generating the DDL. The flow works fine. However in Cloudera distribution we are not able to query the table that has been created as the DDL creates the table

Re: Unable to connect to Confluent Schema Registry with credentials

I believe it would require a code change to the ConfluentSchemaRegistry service to have properties for basic auth username and password, and then pass them down to the client calls. Feel free to create a JIRA to capture this improvement. On Mon, Aug 19, 2019 at 8:17 PM Ali Nazemian wrote: > > I

Re: Data Ingestion pipeline - NiFi to ElasticSearch

It's done all the time. You'll want to use PutElasticsearchHttpRecord with a CSVReader for the record reader. You won't need to write a schema for it right away, but without one it will rely on schema inference which will probably give you sub-optimal field generation (assuming you don't also

Re: "Deadlock" data provenance after few days

Giulia, not sure if this is helpful or not. We had similar issues with NiFi 1.9.x but it was because we upgraded 1.9.0 -> 1.9.1 -> 1.9.2. The culprit was ever running 1.9.1. We saw issues if the node ever ran 1.9.1 on any of our NiFi instances then the data providence was corrupted.

Re: ldap authentication and initial admin identity

Cool! Glad you got it sorted out! Le mar. 20 août 2019 à 11:30, Nicolas Delsaux a écrit : > Wow, I'm really REALLY puzzled. > > I'm using Nifi through the docker image, and docker-compose. > > I was used to do docker-compose up/down, and it failed. > > But this time, I did a docker-compose

Re: ldap authentication and initial admin identity

Wow, I'm really REALLY puzzled. I'm using Nifi through the docker image, and docker-compose. I was used to do docker-compose up/down, and it failed. But this time, I did a docker-compose down, AND destroyed the folder in which the application is deployed. And this time, it worked ! I'm now

Re: ldap authentication and initial admin identity

Something that I can suggest: the users.xml and authorizations.xml files are generated when NiFi starts for the first time. If you did some modifications (such as the initial admin identity), the files users/authorizations won't be updated with your configuration change... Something you could try:

Re: ldap authentication and initial admin identity

When I try to login, UI shows Insufficient Permissions Unable to view the user interface. Contact the system administrator. The log file contains 2019-08-20 08:22:18,808 INFO [main] o.a.n.a.FileAccessPolicyProvider Authorizations file loaded at Tue Aug 20 08:22:18 UTC 2019 2019-08-20

Re: "Deadlock" data provenance after few days

Hi guys, I’m jumping in here, we see the same as Giulia, just in another timeframe. We are using the default provenance settings (nothing changed except the path) with 4GB space on the provenance partition. Are there any suggestions what to change? Of course as I’m checking it now we should