Mārtiņš Kalvāns created CRUNCH-502: --------------------------------------
Summary: OutputFormat has inconsistent context state in interface functions Key: CRUNCH-502 URL: https://issues.apache.org/jira/browse/CRUNCH-502 Project: Crunch Issue Type: Bug Components: IO Affects Versions: 0.12.0 Reporter: Mārtiņš Kalvāns I created example project to demonstrate problematic behaviour: https://github.com/sisidra/crunch-ofb 1. FormatBundle config is not populated to Configuration in checkOutputSpecs: https://github.com/sisidra/crunch-ofb/blob/master/src/main/java/com/spotify/crunch/bugreport/MyOutputFormat.java#L39 {code} 15/03/02 15:40:24 INFO bugreport.MyOutputFormat: my.config.key (checkOutputSpecs): null 15/03/02 15:40:24 ERROR bugreport.MyOutputFormat: Wrong my.config.key value in checkOutputSpecs! {code} 2. TaskAttemptContext. getTaskAttemptID().toString() is different in getRecordWriter and getOutputCommitter: {code} 2015-03-02 15:40:38,960 INFO [main] com.spotify.crunch.bugreport.MyOutputFormat: TaskAttemptID (getOutputCommitter): attempt_1422406067005_0121_m_000000_0 ... 2015-03-02 15:40:39,789 INFO [main] com.spotify.crunch.bugreport.MyOutputFormat: TaskAttemptID (getRecordWriter): attempt_1422406067005_out0_0121_m_000000_0 {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)