Member since 
    
	
		
		
		03-10-2017
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                170
            
            
                Posts
            
        
                80
            
            
                Kudos Received
            
        
                32
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 1173 | 08-12-2024 08:42 AM | |
| 1998 | 05-30-2024 04:11 AM | |
| 2590 | 05-29-2024 06:58 AM | |
| 1745 | 05-16-2024 05:05 AM | |
| 1330 | 04-23-2024 01:46 AM | 
			
    
	
		
		
		03-12-2024
	
		
		05:52 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 403 : Client is not authorized to make this request.   This means you are Authenticated and since you have a valid token but you are not authorized to do this action.  to double-check if your user is Authorized, check if you can do the same action directly from NiFi UI ?    Thank you  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-12-2024
	
		
		03:50 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							  The first step is to create a template, which can be  created within in NiFi cluster from another flow or uploaded from the filesystem, this action will load the templates under   /nifi-api/flow/templates  Then use the below one to create a process group from a template.   /process-groups/{id}/template-instance  import is not the right API call, you can verify this from from web developer tool doing the same actions from UI.  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-12-2024
	
		
		02:22 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 If you have  to load the new template from the filesystem/local to the NiFi cluster, the following API call should be made with POST method   nifi-api/process-groups/{pg-id}/templates/upload  Thank you       
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		01-29-2024
	
		
		03:36 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 When a specific node is down, all the new ingestion will be handled by the remaining nodes.   But the data queued on the down node will be there on that node until the node comes back. If this is HW failure such as disk failure and the node can't be brought back, stuck data will be lost.   Since NiFi is not a storage system but more of an In/out pipeline, we expect the data that is pushed to NiFi not to be the only copy. systems that are pushing data to NiFi should have some room to keep the data intact for some buffer days/hrs until it is processed.  NiFi does not provide any sort of backup/restore or real-time replication.  To avoid such data loss it is expected to have the data at source for some time until data is processed by NiFi for further downstream processing.   Hope this helps.  Thank you        
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-29-2023
	
		
		05:51 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Thanks, The Error message tells me that "access unknown certificate of token not found"   This means NiFi as a service expects client cert to be present if there are No client certs then a token must be present which would be obtained after entering the user name password.  But in LB connection it is possible that the token has been obtained from one nifi node but LB is redirecting the next request to a different NiFi node and it will not work   Have you configured the stick session at the Load Balancing Proxy?  Refer to why it is needed in NiFi   https://community.cloudera.com/t5/Support-Questions/Nifi-authentication-fails-when-a-HTTPS-load-balancer-is-used/td-p/343785  https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration  https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#session_affinity       
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-28-2023
	
		
		06:49 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 How you are trying to log in? using certificate? or Username&Passsword ? Is NiFi running on the container?       
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		12-28-2023
	
		
		05:23 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Looking at the thread, Ans is No, that's not the way NiFi Processor is meant to handle relationships, The Client Processor has to initialize /start properly with the given configuration then only it can try to write and then based on the write results flow files can be routed to failure or success, Here Processor can't even start properly.     
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		11-24-2023
	
		
		05:56 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 The reported behavior with Lock wait timeout in Mysql/MariaDB is not in control of NiFi PutSQL, You have to check your DB Table for possible issues.   Thank you  
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-31-2023
	
		
		05:01 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 You can evaluate the following for better approach   1. Batch use case with ListSFTP/FetchSFTP   2 . ExecuteStateless processor    Thank you     
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-30-2023
	
		
		06:02 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		2 Kudos
		
	
				
		
	
		
					
							 InvokeHTTP does not provide a way to read user Authentication in the form of secrets from files or environment variables.    
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		 
        













