Hey Cheng,

As mentioned on the PR, there is not much evidence that anyone is using the
parquet-scala module:
https://mvnrepository.com/artifact/org.apache.parquet/parquet-scala. Scala
2.12 is EOL while there are still maintenance releases
<https://endoflife.date/scala> being done, and I don't see much interest in
Scala 2.13. I would be in favor of retiring the module since there
haven't been any contributions
<https://github.com/apache/parquet-java/commits/master/parquet-scala> in
the last few major releases. This will also allow us to remove the Scala
build, making the project quite a bit leaner.

Curious to learn what others think!

Kind regards,
Fokko

Op do 7 nov 2024 om 10:36 schreef Cheng Pan <pan3...@gmail.com>:

> Hi parquet developers,
>
> I’m wondering if anyone consumes the `parquet-scala` dependency in your
> project, the module exists for a long time but with rare code change[1],
> all recently commit applied to this module is just dependency upgrading /
> build fixing [2].
>
> I suggest retiring the parquet-scala module, or even dropping it directly.
>
> The module only contains one `Dsl` class[3], which is thin wrapper of the
> Java API, users are easy to copy and embed it if we drop the parquet-scala
> module. Additionally, it's rare to publish a scala lib that only supports a
> single scala binary version, most scala libs support 2~3 scala binary
> versions in each version.
>
> [1] https://github.com/apache/parquet-java/commits/master/parquet-scala
> [2] https://github.com/apache/parquet-java/pull/3044
> [3]
> https://github.com/apache/parquet-java/blob/master/parquet-scala/src/main/scala/org/apache/parquet/filter2/dsl/Dsl.scala
>
> Thanks,
> Cheng Pan
>
>
>
>

Reply via email to