Hey, I didn't look through the whole code so I probably don't get something but why don't you just do what storm does? Keep a map from the field names to indexes somewhere (make this accessible from the tuple) and then you can just use a simple Flink tuple.
I think this is what's happening in storm, they get the index from the context, which knows the declared output fields. Gyula Matthias J. Sax <mj...@informatik.hu-berlin.de> ezt írta (időpont: 2015. jún. 29., H, 18:08): > Hi, > > I started to work on a missing feature for the Storm compatibility > layer: named attribute access > > In Storm, each attribute of an input tuple can be accessed via index or > by name. Currently, only index access is supported. In order to support > this feature in Flink (embedded Bolt in Flink program), I see two > (independent and complementary) ways to support this feature: > > 1) the input type is a POJO > 2) Flink's Tuple type is extended to support named attributes > > Right now I started a prototype for POJOs. I would like to extend Tuple > type with named attributes. However, I am not sure how the community > likes this idea. > > I would like to get some feedback for the POJO prototype, too. I use > reflections and I am not sure if my code is elegant enough. You can find > it here: https://github.com/mjsax/flink/tree/flink-storm-compatibility > > > -Matthias > > > > >
