@Lakshmana Maddineni The issue is because of duplicate rows. When 'not match' is combined with 'match' under the Merge statement, then the cardinality check is applied by default. The Cardinality check needs to be disabled when using both 'matched' and 'not matched'. Set the following property in your hive shell and then try to execute the merge statement again. Set hive.merge.cardinality.check=false; Refer to this support KB article for more details regards to the same exact issue..!! - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

@CHEH YIH LIM I think you are using extract text processor to extract the content and keep as attribute to the flowfile if yes then change Maximum Buffer Size 1 MB Specifies the maximum amount of data to buffer (per file) in order to apply the regular expressions. Files larger than the specified maximum will not be fully evaluated. Maximum Capture Group Length 1024 Specifies the maximum number of characters a given capture group value can have. Any characters beyond the max will be truncated. These two property values as per your flowfile size. - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

@Parth Karkhanis Could you try with introducing SplitAvro Processor in your flow after QueryDatabaseTable processor and configure the processor to create small chunks of flowfile instead of one big AVRO file then try to run your commands again. ... View more

@shraddha srivastav Stop Update Record and add some sample records after GetFile processor by listing the queue i.e. Input sample records like 10(not screenshots) and Expected output. That would be helpful to recreated and resolve the issue..!! ... View more

@shraddha srivastav Use UpdateRecord processor below configs in CSVRecordSetWriter controller service add filename column with string type as last field in the avro schema. UpdateRecord Configs: Add new property in UpdateRecord processor as /filename concat(/UutId,/Test) //column names will be case sensitive As we are using Record Path Value as Replacement Value Strategy now update record processor will concat UutId,Test values to filename column value. Refer to this link for more details regarding Update Record processor. Example: InputData: UutId,Test 1,2 CsvReaderConfigs: CsvRecordSetWriter avro schema: { "namespace": "nifi", "name": "balances", "type": "record", "fields": [ {"name": "UutId", "type": ["null", "string"]}, {"name": "Test", "type": ["null", "string"]}, {"name": "filename", "type": ["null", "string"]} ] } Configs: Ouput: UutId,Test,filename 1,2,12 - If the Answer helped to resolve your issue, Click on Accept button below to accept the answer, That would be great help to Community users to find solution quickly for these kind of issues. ... View more

@Gillu Varghese Both cron triggers in the screenshot are same you can use either of them for scheduling purpose. We cannot trigger just at 3AM, the largest time that we can trigger is at 2:59:59AM with one cron expression. ... View more

@Gillu Varghese Quartz cron expression needs to be atleast 6 fileds and last field will be optional 0 0/15 2 ? * * //no specific value for day of month as we have scheduled at 2 AM so cron triggers starting at 2AM 0 0/15 2 1/1 ? //invalid as month field doesn’t allow ? in it. 0 0/15 2 1/1 * ? (or) 0 0/15 2 * * ? //start first day of the month and execute each 1 day at 2AM In this case both expressions will be same. Please refer to this awesome explanation regards to Quartz cron: 0 0 0/1 1/1 * ? * | | | | | | | | | | | | | +-- Year (range: 1970-2099) | | | | | +---- Day of the Week (range: 1-7 or SUN-SAT) | | | | +------ Month of the Year (range: 0-11 or JAN-DEC) | | | +--------- Day of the Month (range: 1-31) | | +------------- Hour (range: 0-23) | +---------------- Minute (range: 0-59) +------------------ Second (range: 0-59) * (“all values”) used to select all values within a field. For example, “” in the minute field means *“every minute”. ? (“no specific value”) useful when you need to specify something in one of the two fields in which the character is allowed, but not the other. For example, if I want my trigger to fire on a particular day of the month (say, the 10th), but don’t care what day of the week that happens to be, I would put “10” in the day-of-month field, and “?” in the day-of-week field. / used to specify increments. For example: “0/15” in the seconds field means “the seconds 0, 15, 30, and 45”. And “5/15” in the seconds field means “the seconds 5, 20, 35, and 50”. You can also specify ‘/’ after the ‘’ character - in this case ‘’ is equivalent to having ‘0’ before the ‘/’. ‘1/3’ in the day-of-month field means “fire every 3 days starting on the first day of the month”. To explain difference between ? and * in the expressions, first of all take a look at this table: Field Name Mandatory Allowed Values Allowed Special Characters Seconds YES 0-59 , - * / Minutes YES 0-59 , - * / Hours YES 0-23 , - * / Day of month YES 1-31 , - * ? / L W //allowed '?' Month YES 1-12 or JAN-DEC , - * / Day of week YES 1-7 or SUN-SAT , - * ? / L # //allowed '?' Year NO empty, 1970-2099 , - * / ... View more