Ask Your Question

Revision history [back]

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).

click to hide/show revision 2
No.2 Revision

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).

click to hide/show revision 3
No.3 Revision

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).