I see. Is there one way to keep the original object? My use case might be a lit different, because the read and projected schema can change frequently but the file schema is kind of fixed.
Thanks, Yan On Thu, Dec 4, 2014 at 12:23 PM, Ryan Blue <[email protected]> wrote: > On 12/04/2014 12:21 PM, Ryan Blue wrote: > >> Can you send the full log from the task that failed? It looks like it >> was cut off because you only get the first part in the `hadoop` command >> output. >> >> Without all the information, I'm gussing that "java.lang.Cl" is a >> ClassCastException. That would happen if your read schema doesn't have >> the necessary java-class properties that cause Avro to instantiate your >> specific object rather than a GenericData.Record object. >> >> I recommend taking the schema you are using for the read schema and >> building a Specific object for it. Then you can use that stripped-down >> specific object as you were before (call it PartialProfile or something) >> to avoid this issue. >> > > Actually, I think it might need the same name (and namespace) as the > original object. You will want to build this job with the read schema and > object generated by it replacing the original object. > > rb > > > > -- > Ryan Blue > Software Engineer > Cloudera, Inc. >
