bump versions

stackabletech · maltesander · Oct 18, 2023 · Oct 10, 2023 · Oct 10, 2023 · Oct 10, 2023
commit fd85eef608c4b0ce32383264fc1caad1ee1892ca
diff --git a/docs/modules/spark-k8s/examples/example-encapsulated.yaml b/docs/modules/spark-k8s/examples/example-encapsulated.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0 # <1>
+ productVersion: 3.5.0 # <1>
  mode: cluster
  mainClass: org.apache.spark.examples.SparkPi
  mainApplicationFile: /stackable/spark/examples/jars/spark-examples.jar # <2>

diff --git a/docs/modules/spark-k8s/examples/example-history-app.yaml b/docs/modules/spark-k8s/examples/example-history-app.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  pullPolicy: IfNotPresent
  mode: cluster
  mainClass: org.apache.spark.examples.SparkPi

diff --git a/docs/modules/spark-k8s/examples/example-history-server.yaml b/docs/modules/spark-k8s/examples/example-history-server.yaml
@@ -5,7 +5,7 @@ metadata:
  name: spark-history
 spec:
  image:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  logFileDirectory: # <1>
  s3:
  prefix: eventlogs/ # <2>

diff --git a/docs/modules/spark-k8s/examples/example-sparkapp-configmap.yaml b/docs/modules/spark-k8s/examples/example-sparkapp-configmap.yaml
@@ -7,7 +7,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: s3a://stackable-spark-k8s-jars/jobs/ny-tlc-report-1.1.0.jar # <3>
  mainClass: tech.stackable.demo.spark.NYTLCReport

diff --git a/docs/modules/spark-k8s/examples/example-sparkapp-external-dependencies.yaml b/docs/modules/spark-k8s/examples/example-sparkapp-external-dependencies.yaml
@@ -7,7 +7,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: s3a://stackable-spark-k8s-jars/jobs/ny_tlc_report.py # <1>
  args:

diff --git a/docs/modules/spark-k8s/examples/example-sparkapp-image.yaml b/docs/modules/spark-k8s/examples/example-sparkapp-image.yaml
@@ -8,7 +8,7 @@ spec:
  version: "1.0"
  image: docker.stackable.tech/stackable/ny-tlc-report:0.1.0 # <1>
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: local:///stackable/spark/jobs/ny_tlc_report.py # <2>
  args:

diff --git a/docs/modules/spark-k8s/examples/example-sparkapp-pvc.yaml b/docs/modules/spark-k8s/examples/example-sparkapp-pvc.yaml
@@ -7,7 +7,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: s3a://stackable-spark-k8s-jars/jobs/ny-tlc-report-1.0-SNAPSHOT.jar # <1>
  mainClass: org.example.App # <2>

diff --git a/docs/modules/spark-k8s/examples/example-sparkapp-s3-private.yaml b/docs/modules/spark-k8s/examples/example-sparkapp-s3-private.yaml
@@ -6,7 +6,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: s3a://my-bucket/spark-examples.jar # <1>
  mainClass: org.apache.spark.examples.SparkPi # <2>

diff --git a/docs/modules/spark-k8s/examples/example-sparkapp-streaming.yaml b/docs/modules/spark-k8s/examples/example-sparkapp-streaming.yaml
@@ -7,7 +7,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: local:///stackable/spark/examples/src/main/python/streaming/hdfs_wordcount.py
  args:

diff --git a/docs/modules/spark-k8s/examples/getting_started/getting_started.sh b/docs/modules/spark-k8s/examples/getting_started/getting_started.sh
@@ -59,7 +59,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: local:///stackable/spark/examples/src/main/python/pi.py
  driver:

diff --git a/docs/modules/spark-k8s/examples/getting_started/getting_started.sh.j2 b/docs/modules/spark-k8s/examples/getting_started/getting_started.sh.j2
@@ -59,7 +59,7 @@ metadata:
 spec:
  version: "1.0"
  sparkImage:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  mode: cluster
  mainApplicationFile: local:///stackable/spark/examples/src/main/python/pi.py
  driver:

diff --git a/docs/modules/spark-k8s/pages/crd-reference.adoc b/docs/modules/spark-k8s/pages/crd-reference.adoc
@@ -24,7 +24,7 @@ Below are listed the CRD fields that can be defined by the user:
 |User-supplied image containing spark-job dependencies that will be copied to the specified volume mount
 
 |`spec.sparkImage`
-| Spark image which will be deployed to driver and executor pods, which must contain spark environment needed by the job e.g. `docker.stackable.tech/stackable/spark-k8s:3.3.0-stackable0.3.0`
+| Spark image which will be deployed to driver and executor pods, which must contain spark environment needed by the job e.g. `docker.stackable.tech/stackable/spark-k8s:3.5.0-stackable0.0.0-dev`
 
 |`spec.sparkImagePullPolicy`
 | Optional Enum (one of `Always`, `IfNotPresent` or `Never`) that determines the pull policy of the spark job image

diff --git a/docs/modules/spark-k8s/pages/usage-guide/history-server.adoc b/docs/modules/spark-k8s/pages/usage-guide/history-server.adoc
@@ -76,7 +76,7 @@ For a role group of the Spark history server, you can specify: `configOverrides`
 
 The `security.properties` file is used to configure JVM security properties. It is very seldom that users need to tweak any of these, but there is one use-case that stands out, and that users need to be aware of: the JVM DNS cache.
 
-The JVM manages it's own cache of successfully resolved host names as well as a cache of host names that cannot be resolved. Some products of the Stackable platform are very sensible to the contents of these caches and their performance is heavily affected by them. As of version 3.4.0, Apache Spark may perform poorly if the positive cache is disabled. To cache resolved host names, and thus speeding up queries you can configure the TTL of entries in the positive cache like this:
+The JVM manages its own cache of successfully resolved host names as well as a cache of host names that cannot be resolved. Some products of the Stackable platform are very sensible to the contents of these caches and their performance is heavily affected by them. As of version 3.4.0, Apache Spark may perform poorly if the positive cache is disabled. To cache resolved host names, and thus speeding up queries you can configure the TTL of entries in the positive cache like this:
 
 [source,yaml]
 ----

diff --git a/docs/modules/spark-k8s/partials/supported-versions.adoc b/docs/modules/spark-k8s/partials/supported-versions.adoc
@@ -3,5 +3,6 @@
 // Stackable Platform documentation.
 // Please sort the versions in descending order (newest first)
 
-- 3.4.0 (Hadoop 3.3.4, Scala 2.12, Python 3.11, Java 11)
-- 3.3.0 (Hadoop 3.3.3, Scala 2.12, Python 3.9, Java 11)
+- 3.5.0 (Hadoop 3.3.4, Scala 2.12, Python 3.11, Java 11)
+- 3.4.1 (Hadoop 3.3.4, Scala 2.12, Python 3.11, Java 11)
+- 3.4.0 (Hadoop 3.3.4, Scala 2.12, Python 3.11, Java 11) (deprecated)
diff --git a/rust/crd/src/affinity.rs b/rust/crd/src/affinity.rs
@@ -47,7 +47,7 @@ mod test {
  name: spark-history
  spec:
  image:
- productVersion: 3.3.0
+ productVersion: 3.5.0
  logFileDirectory:
  s3:
  prefix: eventlogs/