Yeah it does the same thing anyway. It's fine to consistently use the method. I think there's an instance in ClientSuite that can use it.
On Mon, Jun 13, 2016 at 6:50 PM, Jacek Laskowski <ja...@japila.pl> wrote: > Hi, > > Just noticed that yarn.Client#populateClasspath uses Path.SEPARATOR > [1] to build a CLASSPATH entry while another similar-looking line uses > buildPath method [2]. > > Could a pull request with a change to use buildPath at [1] be > accepted? I'm always confused how to fix such small changes. > > [1] > https://github.com/apache/spark/blob/master/yarn/src/main/scala/org/apache/spark/deploy/yarn/Client.scala#L1298 > [2] Path.SEPARATOR > > Pozdrawiam, > Jacek Laskowski > ---- > https://medium.com/@jaceklaskowski/ > Mastering Apache Spark http://bit.ly/mastering-apache-spark > Follow me at https://twitter.com/jaceklaskowski > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org > For additional commands, e-mail: dev-h...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
