I believe that the confusion is coming from the fact that the /MONTH_CAL_ID is present in the record itself - and hence considered to be part of normal column names and then at the same time used as a partition column as well.
I would recommend to "move" the /MONTH_CAL_ID from record to its header using expression evaluator and then drop the /MONTH_CAL_ID from the record itself (using field remover). And finally changing the partition value expression to ${record:attribute('partition')} (or similar).  2 No.2 Revision LC 188 ●2 ●8 ●15 I believe that the confusion is coming from the fact that the /MONTH_CAL_ID is present in the record itself - and hence considered to be part of normal column names and then at the same time used as a partition column as well. I would recommend to "move" the /MONTH_CAL_ID from record to its header using expression evaluator the Expression Evaluator and then drop the /MONTH_CAL_ID from the record itself (using field remover). the Field Remover). And finally changing the partition value expression to ${record:attribute('partition')} (or similar).
I believe that the confusion is coming from the fact that the /MONTH_CAL_ID is present in the record itself - and hence considered to be part of normal column names and then at the same time used as a partition column as well.
I would recommend to "move" the /MONTH_CAL_ID from record to its header using the Expression Evaluator Evaluator and then drop the /MONTH_CAL_ID from the record itself (using the Field Remover). Remover). And finally changing the partition value expression to \${record:attribute('partition')} (or similar).