@ Justen Starting from NiFi-1.8.0 we are going to have filename same as flowfileuuid so you are able to search based on flowfileuuid to find out the specific filename. If you are using prior to NiFi-1.8 then you can search based on filename using below process instead of clicking on "i" Click on the right search then you are able to view search events box then keep your desired filename overthere then click on search to get only the specific file from the provenance. ... View more

@ravi kargam As a work around Instead of using replaceRegex function use replace function with below configs: UpdateRecord Configs: Replacement Value Strategy Record Path Value /employeeName replace(/employeeName,'[','(') (or) If you are updating only one column value then Replacement Value Strategy Literal Value /employeeName ${field.value:replaceAll('\\[','(')} ... View more

@Henrik Olsen The same exact case is introduced in NiFi-1.6 version jira addressing this bug NiFi-4883. Starting from NiFi-1.6 we are able to use one record writer for invalid records and use different record writer for the valid records. ... View more

@n c So the month ie "10" is actually appearing as part of the table data. Is that correct? Yes this is correct, when we create partition table we are going to have all partition columns at the end of the column list. Partitions are going to boost the query performance when we are using partition column in out where clause. Example: if you want to count number of records are in mth=10 then select count(*) from test_par_tbl where mth=10; Now the above query won't do full table scan as predicate only scan the mth=10 partition and shows up the result. when dealing with 100's of million datasets partitions will be optimization techniques to boost up the query performances by avoiding full table scans. 2.Even with out partition field in where clause you can still able to run the below query but this will do full table scan select count(*) from test_par_tbl where month(create_dt)=10; Both these queries will give you same results but taking performance as consideration on big data sets first query will run more efficiently. Is it possible to partition the table as above and not have the partition column/value as part of the table data? This is not possible because if you won't have partition column as part of table data then hive will do full table scan on the entire dataset. If you still want to take off the partition column from the dataset, then create a view on top of the partition_table it by excluding the column. ... View more