[ 
https://issues.apache.org/jira/browse/AVRO-3266?focusedWorklogId=777976&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-777976
 ]

ASF GitHub Bot logged work on AVRO-3266:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Jun/22 08:43
            Start Date: 03/Jun/22 08:43
    Worklog Time Spent: 10m 
      Work Description: opwvhk commented on PR #1618:
URL: https://github.com/apache/avro/pull/1618#issuecomment-1145738375

   Looks reasonable good to me as well, but personally I prefer PR #1431 
because it doesn't use reflection (there's no need; the `PathOutputComitter` 
interface is generic enough).
   
   On the other hand: I don't use Hadoop, so maybe I'm missing something.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 777976)
    Time Spent: 2h 40m  (was: 2.5h)

> Output stream incompatible with MagicS3GuardCommitter
> -----------------------------------------------------
>
>                 Key: AVRO-3266
>                 URL: https://issues.apache.org/jira/browse/AVRO-3266
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: java
>            Reporter: Michiel de Jong
>            Assignee: Emil Ejbyfeldt
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.11.1
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Avro's output stream can not be used in combination with the 
> MagicS3GuardCommitter
> {code:java}
> Error: java.lang.ClassCastException: class 
> org.apache.hadoop.fs.s3a.commit.magic.MagicS3GuardCommitter cannot be cast to 
> class org.apache.hadoop.mapreduce.lib.output.FileOutputCommitter{code}
> The reason for this problem is that 
> AvroOutputFormatBase.getAvroFileOutputStream tries to cast the outputcommiter 
> to a FileOutputCommitter.
> It can be solved by casting to a PathOutputCommitter instead (which is a 
> superclass of both the FileOutputCommitter and the MagicS3GuardCommitter)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to