Github user ramaddepally commented on the issue:
https://github.com/apache/spark/pull/23053
> Hm, reviewing this again I think a better way to do it is to only opt-in
to building images of different bindings. So for example the Python image
should only be built when `-p <file>` is specified. It seems strange that by
default the utility is building all images.
>
> Perhaps a better interface for this entry point is this:
>
> ```
> bin/docker-image-tool.sh -f <path to dockerfile> -j <optional java
override> -p <optional python override>
> ```
> What does everyone think"?
I do not mind this approach, where we build JVM image by default and build
pyspark and SparkR (and other optional images) on demand. But changing the
behavior means, breaking ppl out there that are already using this script. If
we are OK to do such change, then I can modify the script accordingly.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
