[CASSANDRA-19528] [Analytics] Use a classloader to isolate in-jvm dtest classes in integration test

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: NA
• Component/s: Analytics Library
• Labels: analytics test-framework
• Change Category: Semantic
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra-analytics/commit/47fdb6448b6956249790d5dc7bb76b699d35c079

Test and Documentation Plan

The change involves touching they integration test code.

• Assignee: Francisco Guerrero
• Reporter: Francisco Guerrero

Authors

Francisco Guerrero

Reviewers

Yifan Cai

• Created: 04/Apr/24 17:51
• Updated: 04/Apr/24 23:19
• Resolved: 04/Apr/24 23:19

Description

We need to isolate the in-jvm dtest classes (coming from the shaded dtest jar) from the classes in Cassandra Analytics when running integration tests. The isolation will allow us to test the Analytics code in the AppClassloader without any class pollution from classes coming from the shaded dtest jar. In some cases, the pollution can spill to classes that are shaded in the analytics project (metrics, json serialization, guava, etc).

With the isolation in place we can be more confident that the code we are testing is the code that will be running in a Spark environment.

Issue Links

• links to: GitHub Pull Request #50