You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by Tobin Baker <td...@cs.washington.edu> on 2015/12/12 00:31:14 UTC

`org.apache.reef.runtime.yarn.client.YarnDriverConfiguration` vs `org.apache.reef.runtime.yarn.driver.YarnDriverConfiguration`

I'm working on https://issues.apache.org/jira/browse/REEF-1034, which
involves adding
`org.apache.reef.runtime.yarn.driver.parameters.JobSubmissionDirectoryPrefix`
as an `OptionalParameter` to
`org.apache.reef.runtime.yarn.driver.YarnDriverConfiguration`, by analogy
with `org.apache.reef.runtime.mesos.driver.MesosDriverConfiguration`. But
then I noticed that there are actually two instances of
`YarnDriverConfiguration`:
`org.apache.reef.runtime.yarn.client.YarnDriverConfiguration` and
`org.apache.reef.runtime.yarn.driver.YarnDriverConfiguration`.
`MesosDriverConfiguration` isn't similarly bifurcated. So my question is:
1) why are there two different classes named `YarnDriverConfiguration`, and
2) which of these classes is appropriate to contain the parameter
`JobSubmissionDirectoryPrefix`?

Thanks,
Tobin