Member since 
    
	
		
		
		03-26-2024
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                35
            
            
                Posts
            
        
                18
            
            
                Kudos Received
            
        
                0
            
            
                Solutions
            
        
			
    
	
		
		
		05-28-2025
	
		
		10:13 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thank you @MattWho for your quick help. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		05-20-2025
	
		
		11:28 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thank you @MattWho @linssab for the help.    The Groovy script with the ExecuteScript processor is working fine to convert JSON file content to flow file attributes. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		05-09-2025
	
		
		09:38 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @avinashmv   Thank you for the Info    Could you please suggest an alternative processor to use in NiFi as part of CFM 2.1.7 that provides the same functionality and attributes as the CountText processor? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		05-09-2025
	
		
		08:04 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi Team,  I'm currently using a custom NiFi processor to convert JSON file content into flow file attributes, and I'm looking to replace it with a standard NiFi processor if possible.  Sample JSON Input:  The JSON files look like this (keys may vary per file):  {  "SourceFilePath": "/root/rdw/SrcFiles",  "SourceFilePattern": "Sales_data",  "SourceFile": "Sales_data_20241211.csv"  }    Current Setup:  I'm using a custom processor of type CreateFlatJSON (Bundle: NestedJSONToFlatJSON) to extract the key-value pairs from the JSON and assign them to attributes.  After processing, the flow file attributes look like:  SourceFilePath = /root/rdw/SrcFiles  SourceFile = Sales_data_20231111164536.csv  SourceFilePattern = Sales_data  These attributes are then used in downstream processors like so:  ${SourceFilePath}/${SourceFile}  Current Flow:  FetchSFTP → ExtractText → CreateFlatJSON (Custom) → Downstream Processors  FetchSFTP: Retrieves the JSON file.  ExtractText: Reads the content into the flow file.  CreateFlatJSON: Parses JSON and converts key-value pairs to attributes.  Question  Is there a standard NiFi processor that can replace the custom CreateFlatJSON processor and achieve the same functionality — i.e., convert JSON content in the flow file into flow file attributes (with dynamic keys/values)? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
	
					
			
		
	
	
	
	
				
		
	
	
			
    
	
		
		
		05-09-2025
	
		
		12:22 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi Team,  Could you please confirm whether the CountText processor is a standard NiFi processor? I couldn't find it listed under the "Supported NiFi Processors" section in the Cloudera Flow Management 2.1.7 release notes:  https://docs.cloudera.com/cfm/2.1.7/release-notes/topics/cfm-supported-processors.html  Your insights would be appreciated. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
- 
						
							
		
			Apache NiFi
			
    
	
		
		
		03-24-2025
	
		
		09:53 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thank you, @MattWho , for the additional information. I really appreciate you providing timely and clear solutions. You’re awesome! 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-23-2025
	
		
		11:01 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @MattWho   Please disregard my previous response.    I removed the retry relationship which is connecting back to the InvokeHttp Processor and  I am able to check both the "terminate" and "retry" boxes.  The retry option is working as expected.     
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-21-2025
	
		
		10:19 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thank you @MattWho  for your valuable input.  Yes, as you mentioned, my requirement is to retry 3 times, and if all three attempts result in routing to the retry relationship, terminate the FlowFile.  I tried both options you mentioned.  The first option doesn’t seem to be possible. I tried checking both the "terminate" and "retry" boxes on the retry relationship, but an error popped up: "Cannot automatically terminate 'Retry' relationship because a connection already exists with this relationship." Since I’ve already connected the retry relationship back to the InvokeHttp processor, it’s not allowing me to enable "terminate."      Could you please provide more input on this option?  The second option is working fine. Instead of looping the "retry" relationship back to the processor, I routed it to another processor. After the 3 retry attempts, it routes to the next processor and terminates the FlowFile.     
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		03-21-2025
	
		
		09:00 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I have configured an InvokeHttp Processor with the 'Retry' relationship enabled to capture HTTP status codes between 500 and 599 and initiate retries. I connected the 'Retry' relationship back to the InvokeHTTP processor to enable automatic reattempts. The number of retry attempts is set to 3. However, after all retry attempts are exhausted, the process does not complete and ends up queuing in the Retry relationship, as shown below:  Could you please help how to fix it?                 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
- 
						
							
		
			Apache NiFi
			
    
	
		
		
		11-11-2024
	
		
		11:57 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hi Team,  How can I replace the custom ConsumeASB Processor with the InvokeHttp Processor in NiFi? I am currently using a Topic subscription with my ConsumeASB Processor to read messages from an Azure Service Bus endpoint.  How can I configure the InvokeHttp Processor to achieve the same functionality?  Could you please provide some inputs. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
- 
						
							
		
			Apache NiFi
 
        






