Release 3.3.2 (#480)

* updated version.properties and readmes * updated comments * Added readme notes about versioning. * Added spark and vertica version tested to readme. * Update note on connector versioning * updated badges and removed version * capitalized letter Co-authored-by: jeremyp-bq <[email protected]>
vertica · Aug 15, 2022 · bd5c677 · bd5c677
1 parent f9f2f78
commit bd5c677
Show file tree

Hide file tree

Showing 6 changed files with 13 additions and 5 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -72,7 +72,7 @@ cd connector
 sbt assembly
 ```
 
-Running this will run all unit tests and build the jar to target/scala-2.12/spark-vertica-connector-assembly-3.3.1.jar.
+Running this will run all unit tests and build the jar to target/scala-2.12/spark-vertica-connector-assembly-3.3.2.jar.
 
 **Note:** Make sure that you are building the jar on your local machine; Building it inside our docker environment 
 will be extremely slow.
@@ -284,3 +284,8 @@ Pull requests are usually reviewed within a few days. If there are comments to a
 That's it! Thank you for your code contribution!
 
 After your pull request is merged, you can safely delete your branch and pull the changes from the upstream repository.
+
+## Versioning
+
+We are targeting support for all Spark releases since 3.0. Our release number format is `major.minor.patch`, with the major
+and minor numbers always trying to match the latest Spark release.
diff --git a/README.md b/README.md
@@ -10,6 +10,9 @@
 [![contributing](https://img.shields.io/badge/contributing-read-orange)](CONTRIBUTING.md)
 [![license](https://img.shields.io/badge/license-Apache%202.0-orange.svg)](https://opensource.org/licenses/Apache-2.0)
 
+![vertica-tested](https://img.shields.io/badge/Vertica%20Tested-10%20%7C%2011%20%7C%2012-blue)
+![spark-tested](https://img.shields.io/badge/Spark%20Tested-3.0%20%7C%203.1%20%7C%203.2%20%7C%203.3-blue)
+
 This component acts as a bridge between Spark and Vertica, allowing the user to either retrieve data from Vertica for processing in Spark, or store processed data from Spark into Vertica.
 
 Why is this connector desired instead of using a more generic JDBC connector? A few reasons:

diff --git a/examples/pyspark/run-python-example.sh b/examples/pyspark/run-python-example.sh
@@ -1,5 +1,5 @@
 CONNECTOR_VERSION=$(cat ../../version.properties | grep ${connector-version} | cut -d'=' -f2)
-spark-submit --master spark://spark:7077 --jars ../../connector/target/scala-2.12/spark-vertica-connector-assembly-CONNECTOR_VERSION.jar sparkapp.py
+spark-submit --master spark://spark:7077 --jars ../../connector/target/scala-2.12/spark-vertica-connector-assembly-$CONNECTOR_VERSION.jar sparkapp.py
 
 
 

diff --git a/examples/sparklyr/sparkapp.r b/examples/sparklyr/sparkapp.r
@@ -7,7 +7,7 @@ library('properties')
 
 props <- read.properties("../../version.properties")
 version <- props["connector-version"]
-# construct the path to Vertica-Spark connector jar
+# construct the path to Vertica-Spark connector jar. Replace this if the path to the jar is different
 connectorJar <- paste("../../connector/target/scala-2.12/spark-vertica-connector-assembly-", version, ".jar", sep = "")
 
 # Create a Spark config and disable Hive support to avoid errors

diff --git a/functional-tests/README.md b/functional-tests/README.md
@@ -8,7 +8,7 @@ Configuration is specified with application.conf (HOCON format)
 From the functional-tests directory, run the following commands:
 ```
 mkdir lib
-cd ../connector && sbt assembly && cp target/scala-2.12/spark-vertica-connector-assembly-3.3.1.jar ../functional-tests/lib && cd ../functional-tests
+cd ../connector && sbt assembly && cp target/scala-2.12/spark-vertica-connector-assembly-3.3.2.jar ../functional-tests/lib && cd ../functional-tests
 ```
 This will create a lib folder and then build and copy the connector JAR file to it.
 

diff --git a/version.properties b/version.properties
@@ -1,2 +1,2 @@
-connector-version=3.3.1
+connector-version=3.3.2