@Vin900, as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. ... View more

writes attribute of some processors (SplitRecord, ReplaceText ) does not contains the error it writes during execution.  How and where to identify the error in that case?  ... View more

@Jorge moyano I tried the below code as you suggested but still facing the same problem File fileObj = new File(pathname); FileBody fileBody = new FileBody(fileObj, ContentType.MULTIPART_FORM_DATA); HttpEntity multiPart = MultipartEntityBuilder.create().addPart("template", fileBody).build(); HttpPost httpPost = new HttpPost("http://localhost:8080/nifi-api/process-groups/root/templates/upload"); httpPost.addHeader("Content-type", "multipart/form-data"); httpPost.setEntity(multiPart); HttpClient httpClient = HttpClientBuilder.create().build(); HttpResponse response = httpClient.execute(httpPost); Response HttpResponseProxy{HTTP/1.1 500 Internal Server Error [Date: Sat, 30 Sep 2017 04:24:37 GMT, X-Frame-Options: SAMEORIGIN, Content-Type: text/plain, Transfer-Encoding: chunked, Server: Jetty(9.4.3.v20170317)] ResponseEntityProxy{[Content-Type: text/plain,Chunked: true]}} ... View more

@sri chaturvedi if you are having d_last_updt attribute value as 2017-03-12 06:07:12:01 then in Route On Attribute processor add new property as ${d_last_updt:toDate('yyyy-MM-dd'):format('yyyyMMdd'):gt('20170731')} //todate extracts year month date from your lastupdatedate attribute and formats as yyyyMMdd then give your value in gt function. This property checks all d_last_updt attribute value if the value is greater than 20170731 if attribute value satisfies the condition then it routes to property name relation , if not it routes to unmatched relation. Route on Attribute processor Configs:- ... View more

@Balakrishnan Ramasamy The NiFi expression language allows users to dynamically retrieve values from FlowFile Attributes, environment variables, JVM properties, or a variable registry file. Only properties that are marked as supporting expression language can be passed value dynamically. Floating your cursor over the little question mark next to any property will tell you if it support expression language or not. For sensitive property fields, the value entered is encrypted upon hitting OK. It is then stored in the encrypted format in the flow.xml.gz file. It does not support the expression language. Please accept my answer if you feel i have addressed your question. Thank you, Matt ... View more

@Tarek Elgamal Assuming you are referring to settings for "Max Timer Driven Thread count"? That setting controls the max number of threads that can execute at one time. Does not guarantee any order to the execution of threads. NiFi's controller in the back ground does not operate under this thread pool. Both processors will be scheduled to run based on their configured run schedule. Those concurrent tasks then get stacked in a request queue waiting on one of the threads from that pool to service them. This way, every processor is eventually going to get a chance to run thier code. Also keep in mind that some processors work on batches of FlowFiles while others process one FlowFile per task. Also hard to say that each processed FlowFile will take same amount of time to complete an operation. Really depends on processor and what it is designed to do. Thanks, Matt ... View more