We were able to reproduce the issue and this is a regression in how we serialize the SerializableCoder, we used to only save the class but now save the class and type variable. The type variable is unnecessary and being marked as transient.
On Thu, May 11, 2017 at 4:52 PM, Thomas Groh <[email protected]> wrote: > Hey Antony; > > I've tried to update your code to compile in Java 7 and removed the > SerializableUtils Dan mentioned, and I can't seem to reproduce the issue. > Can you share more about the specific issue you're having? A stack trace > would be really helpful. > > Thanks, > > Thomas > > On Thu, May 11, 2017 at 4:42 PM, Dan Halperin <[email protected]> wrote: > >> Hi Anthony, >> >> I'm a little confused by your code snippet: >> >> SerializableUtils.serializeToByteArray( >> input.apply(ParDo.of(new NonGenericOutput<>())).apply("passing", >> View.asSingleton()) >> ); >> >> is serializing a PCollectionView object. Those are not necessarily >> serializable and it's not clear that it makes sense to do this at all. >> >> Can you say more about what you're trying to do? >> >> Thanks, >> Dan >> >> On Thu, May 11, 2017 at 4:21 PM, Antony Mayi <[email protected]> >> wrote: >> >>> I tried the 2.0.0rc2 and I started facing weird serialization issue >>> that's not been happening on 0.6.0. I am able to reproduce it using the >>> attached unit test - see first serialization attempt which is passing ok >>> and second one slightly different (transform output type is generic) that's >>> failing just on 2.0.0 >>> >>> Can anyone find a way around it? In my real case I depend on generics >>> output types. >>> >>> thanks, >>> antony. >> >> >> >
