to be accessed at runtime (e.g. max num of supersteps). > > One way is to read them from the conf in the first superstep and save them > in memory in the vertex. > However this solution is wasteful in terms of memory, as it replicates the > same value multiple times. This is the preferred way of doing it and, assuming the values are too large, shouldn't be too bad on memory.
> Another solution is to read them from the conf every time, but this > requires reparsing them each time. > > The WorkerContext looks the right place to put this kind of data. > However there is no way (I know of) to access the configuration from the > WorkerContext. > Am I correct? This could work too. > Would it be difficult to implement this change? > Are there reasons why it is not in place already? Most likely because no one has requested it. We also should have some way to access the distributed cache. Go ahead and file a JIRA. Patches welcome!
