Hi, problem is solved. Seems the root cause is my groovy misunderstanding I have an instance of storm Tuple: tupleInstance.*sourceStreamId* returns null tupleInstance.*getSourceStreamId()* returns value
Problem is solved :) 2015-12-28 13:00 GMT+01:00 Matthias J. Sax <[email protected]>: > Hi, > > message IDs are only used if you enable fault-tolerance, ie, assign an > ID to each tuple in your spouts. > > You do not assign an ID: "id: {}" > > >> 6520 [Thread-14-UserContextBolt] INFO b.s.d.executor - Processing > >> received message FOR 3 TUPLE: source: *GenericEventSpout*:1, stream: > >> *GameEvent*, id: {}, > >> [{"type":"GameEvent","id":"0","attributes":null,"ts":1451232574860}] > > -Matthias > > On 12/27/2015 05:14 PM, Serega Sheypak wrote: > > Hi, I'm trying to get input Tuple streamId. Unfortunately, all Tuple > > metadata fields are equal to null. > > > > Here is my topology and sample code, please have a look at gist: > > https://gist.github.com/seregasheypak/0adc0fd79e7784483c50 > > > > The weird thing is: > > > > 6520 [Thread-14-UserContextBolt] INFO b.s.d.executor - Processing > > received message FOR 3 TUPLE: source: *GenericEventSpout*:1, stream: > > *GameEvent*, id: {}, > > [{"type":"GameEvent","id":"0","attributes":null,"ts":1451232574860}] > > > > 6524 [Thread-14-UserContextBolt] INFO c.u.c.b.UserContextBolt - input: > > > [GameEvent:{"type":"GameEvent","id":"0","attributes":null,"ts":1451232574860}] > > | null|null null null null > > > > The first log line says that tuple is received, source and stream are > > set correctly. The same fields are null when Tuple is processed inside > bolt. > > > > I'm using storm 10.0. Thanks! > >
