Github user imatiach-msft commented on the issue:
https://github.com/apache/spark/pull/19439
@MrBago in regards to the question below -- I discussed with @drdarshan who
is familiar with Python, and he said that it wouldn't be standard to create a
class just to change the namespace and have static methods everywhere (having a
class does not make sense here since there is no common state). I don't think
the namespace being slightly different is an issue.
"@imatiach-msft just a few more comments. When I was looking over this I
realized that the python and Scala name spaces are going to be a little
different, eg pyspark.ml.image.readImages vs
spark.ml.image.ImageSchema.readImages. Should we use an ImageSchema class in
python as a namespace? Does spark do that in other pyspark modules?"
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
