Thanks to both for the responses! Yi, thanks for pointing that out, I didn't see this before.
systems.system-name.streams.stream-name. samza.msg.serde That's exactly what I need! Thanks, José Luis On May 11, 2015 6:03 PM, "Yi Pan" <nickpa...@gmail.com> wrote: > Hi, Jose, > > Please refer to the configure wiki: > > http://samza.apache.org/learn/documentation/0.9/jobs/configuration-table.html > Samza actually allows multiple Serde classes to be defined for different > topics, as long as you don't have multiple schemas of messages in the same > topic. > > Best, > > -Yi > > On Mon, May 11, 2015 at 5:30 PM, José Barrueta <j...@stormpath.com> wrote: > > > Hi all, > > > > We're planning to have a Samza Job that reads from 2 or more Kafka > topics, > > the messages are serialized using Binary Json, we'd like to deserialize > > each message to its specific Java Type, the job configuration only allows > > to declare one system msg deserializer, is there any plan to allow per > > input deserializers? If not, and you guys find it useful, I'd be happy to > > contribute in it. > > > > So the other option I have is to send the raw bytes to the StreamTask and > > handle the deserialization in the `process(...)` method based on the > stream > > source, i.e. envelope.getSystemStreamPartition().getStream() what I don't > > like about this approach, is that I'll be coupling the name of a > partition > > to a specific behavior in the application. > > > > Any other suggestions? > > > > Jose Luis > > >
