Hi all,
I see some people repeatedly create new versions such as "3.4" (it has to
be "3.4.0") in JIRA.
[image: Screen Shot 2022-06-07 at 2.29.02 PM.png]
I manually check, remove and reassign them but I think it's the fifth time
IIRC.
Please avoid creating a new version such as 3.4 without
What I like most about this SPIP are:
1. We could leverage this SPIP to dispatch the driver to the cluster (e.g.,
yarn-cluster or K8S cluster mode) with an interactive shell which Spark
currently doesn't support.
2. Makes it easier for other languages to support, especially given that we
talked
+1 (non-binding)
1. Verify binary checksums and signatures.
2. Check kubernetes and pyspark documentation
3. Verify K8S integration test on aarch64
4. Verify customized scheduler and volcano integration test with Volcano
1.5.1.
On Mon, Jun 6, 2022 at 3:43 PM Dongjoon Hyun
wrote:
> +1.
>
> I
+1. Ran and verified results through internal tests.
On Mon, Jun 6, 2022 at 3:43 PM Dongjoon Hyun
wrote:
> +1.
>
> I double-checked the following additionally.
>
> - Run unit tests on Apple Silicon with Java 17/Python 3.9.11/R 4.1.2
> - Run unit tests on Linux with Java11/Scala 2.12/2.13
> -
Hi Mich,
I think I must have been not clear enough in the document. The proposal is
not for connecting Spark to other engines but to connect to Spark from
other clients remotely (without using SQL)
Please let me know if that clarifies things or if I can provide additional
context.
Thanks
Martin
+1.
I double-checked the following additionally.
- Run unit tests on Apple Silicon with Java 17/Python 3.9.11/R 4.1.2
- Run unit tests on Linux with Java11/Scala 2.12/2.13
- K8s integration test (including Volcano batch scheduler) on K8s v1.24
- Check S3 read/write with spark-shell with Scala
