Member since 
    
	
		
		
		01-10-2022
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                5
            
            
                Posts
            
        
                1
            
            
                Kudos Received
            
        
                0
            
            
                Solutions
            
        
			
    
	
		
		
		04-19-2024
	
		
		09:12 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi,  I have seen an error in the processor PutS3Object, Even though it shows the error, it is successfully putting the object in AWS S3. Looks like the below line in the onTrigger method is causing this. If I comment on this and build, it does not throw any error.   ageoffS3Uploads(context, s3, now, bucket);   this is the error it is throwing in the UI.   else {      getLogger().info("Error checking S3 Multipart Upload list for {}: {}",              new Object[]{bucket, e.getMessage()});  }   My Processor config looks like this, I have tried both ways for ObjectKey and Bucket attributes and still see the unnecessary errors.           And this as well.      Error's in both cases.               
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
 - 
						
							
		
			Apache NiFi
 
			
    
	
		
		
		04-19-2024
	
		
		03:46 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I am still seeing the same error, despite having just Bucket Name in Bucket and file path in ObjectKey. Anything i was missing? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		06-16-2022
	
		
		01:21 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I had a zNode ACL issue for zookeeper, once ACL access is fixed it started working fine. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		02-27-2022
	
		
		05:48 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi ,     We are seeing the below error message in nifi-app.log   apache.nifi.web.api.SAMLAccessResource The RelayState value returned by the SAML IDP does not match the stored state  and on the UI we are seeing the below error.  Purposed RelayState does not match the stored state. Unable to continue login process.     in nifi-user.log , we see below error :   [Anonymous authentication has not been configured.]  Any idea? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
 - 
						
							
		
			Apache NiFi
 
			
    
	
		
		
		01-14-2022
	
		
		10:59 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 the issue is fixed now, it was zookeeper issue 
						
					
					... View more