Because both of the plugins export avro and parquet, we run into the familiar classloading issues we've seen with other plugins if plugins from both artifacts are used. For example, a gcs source reading parquet and a file sink writing parquet. I don't believe the problem shows up if sources and sinks are not mixed in a pipeline.
One short term fix could be to shade the relevant classes. Not sure how/if that will work with the maven bundle plugin.
Fixed an issue that caused avro, parquet, and orc classes across file, gcs, and s3 plugins to clash and cause pipeline failures.
shading appears to work, though I had to move the manifest creation to shade using org.apache.maven.plugins.shade.resource.ManifestResourceTransformer and remove the maven-bundle-plugin. The jar size also increased from 51M to 60M
If everything works after more testing, will probably just shade it. We really need to move these formats to plugins sometime soon to avoid these issues.
going to try to do this properly instead of shading.