Move QuarkusSparkIT to a separate module

[adutra]

The Spark integration tests require specific versions of some dependencies that conflicting more and more with the versions declared in the Quarkus BOM.

This PR simply isolates QuarkusSparkIT in its own module in order to alleviate the amount of tweaks we need to do in polaris-quarkus-service to get it to build correctly.

[dimas-b]

This change LGTM. The suggested change in the base tests module can be a follow-up PR (if we want to do that)

[dimas-b]

Would it make sense to split polaris-tests into a general part (that only uses Iceberg Core) and a Spark-specific part (instead of excluding spark jars)?

[flyrain]

Can we add QuarkusSparkIT to the module integration-tests instead of creating a new module? integration-tests holds the class PolarisSparkIntegrationTest which is the class QuarkusSparkIT inherits from. It makes more sense to put them together, as their functionalities and dependencies are similar.

[dimas-b]

Can we add QuarkusSparkIT to the module integration-tests instead of creating a new module?

The idea behind the integration-tests module is to allow reuse in different environments (including downstream projects).

QuarkusSparkIT executes the sharable test code in the specific env. of the Polaris Quarkus Server Integration Tests.

TBH, I do not see how it fits inside the integration-tests module.

[flyrain]

The idea behind the integration-tests module is to allow reuse in different environments (including downstream projects).

QuarkusSparkIT executes the sharable test code in the specific env. of the Polaris Quarkus Server Integration Tests.

TBH, I do not see how it fits inside the integration-tests module.

Are we trying to support a Polaris server not powered by Quarkus? I'd assume not. In that case, the chances of reuse integration-tests module is rare. WDYT?

[dimas-b]

I mean any downstream build of Polaris. The integration-tests module allows running the sever in a variety of ways, not assuming any particular framework (like Quarkus Integration Tests).

[flyrain]

I mean any downstream build of Polaris. The integration-tests module allows running the sever in a variety of ways, not assuming any particular framework (like Quarkus Integration Tests).

That would still be rare, as people need to rewrite a lot of code to bring it up with a non-Quarkus server. I am wondering how it could happen.

[dimas-b]

I mean running a custom server outside the Quarkus Integration Test framework. The server itself may very well be based on Quarkus, but running in docker, for example.

[adutra]

@flyrain are you OK merging this?

[flyrain]

yeah, feel free to do so.