tejaslodayadd opened a new pull request, #208:
URL: https://github.com/apache/cassandra-analytics/pull/208

   ## Patch by Tejas Lodaya for 
[CASSANALYTICS-67](https://issues.apache.org/jira/browse/CASSANALYTICS-67)
   
   ### What
   Disable the Spark UI (`spark.ui.enabled=false`) for every `SparkSession` 
created by the test suites.
   
   ### Why
   By default, each `SparkSession` started during tests stands up a Spark UI on 
port 4040 (falling back to 4041, 4042, … on conflict). It serves no purpose in 
automated runs, consumes resources, and is a recurring source of port-binding 
noise when tests run in parallel — which is exactly what was flagged in the 
JIRA.
   
   ### Where the change lives
   There are two distinct entry points that construct a `SparkSession` in 
tests, so the flag is set in both:
   
   | File | Scope |
   | --- | --- |
   | `cassandra-analytics-integration-tests/.../SparkTestUtils.java` 
(`defaultSparkConf`) | All integration tests — covers 
`SharedClusterSparkIntegrationTestBase`, `CoordinatedBulkWriteSimpleTest`, and 
any future caller of `defaultSparkConf()`. Setting it once on the shared 
`SparkConf` is preferred over patching `getOrCreateSparkSession` in the base 
class so additional callers stay covered automatically. |
   | `cassandra-analytics-core/.../TestUtils.java` (`Holder.createSession`) | 
Unit tests using the shared `SparkSession` holder in 
`cassandra-analytics-core`. |
   
   ### Notes / scope
   - Test-only change. No production code is touched.
   - `CHANGES.txt` updated under `0.5.0`.
   - Validated locally that `./gradlew check` (with deps built via 
`scripts/build-dependencies.sh`) still passes checkstyle on the changed modules.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to