Job would need to do some similar tricks to get the flow process too right?

If its not part of the stats and it doesn't fit there anymore I think I'd
rather we address it in another PR and remove it for now?


On Sun, Jan 26, 2014 at 2:04 PM, avibryant <notifications@github.com> wrote:

> In scalding-core/src/main/scala/com/twitter/scalding/Stats.scala:
>
> > @@ -8,24 +8,65 @@ import scala.collection.JavaConverters._
> >
> >  import org.slf4j.{Logger, LoggerFactory}
> >
> > +import java.util.concurrent.ConcurrentHashMap
> > +
> > +case class Stat(name: String, group: String = Stats.ScaldingGroup)(@transient implicit val uniqueIdCont: Job#UniqueID) {
> > +  @transient private lazy val logger: Logger = LoggerFactory.getLogger(this.getClass)
> > +  val uniqueId = uniqueIdCont.get
> > +  lazy val flowProcess: FlowProcess[_] = RuntimeStats.getFlowProcessForUniqueId(uniqueId)
> > +
> > +// Use this if a map or reduce phase takes a while before emitting tuples.
> > +  def keepAlive: Unit =
>
> Could we add it to Job?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/twitter/scalding/pull/757/files#r9177808>
> .
>