Closed devictr closed 2 years ago
Hi there!
I recently joined Jetbrains to help with the Spark API specifically. This means it is now definitely actively maintained :). In the short term, we are looking at streamlining the project so that releasing the API for the latest couple of Spark versions, as well as Scala versions, can be done quicker and more easily. It's namely a bit difficult at the moment. In the long term there are also some ideas for features that are not present yet. Feel free to leave an issue if you think something should be added!
As for the official Spark API, we know as much as you do. Apache probably does not want their project to depend on the Kotlin libraries, so official integration by Apache will likely not be a thing. That said, .NET is also not officially supported by Apache, but there's also a Spark API for that, so if we can keep it as "official" as that, that's good, right?
Hi @Jolanrensen
Congrats on the new gig! That is great to hear. Thank you for all those precisions
Hi folks,
First of all, thank you for all the work you've done to create this Kotlin Spark API. My company is evaluating using
kotlin-spark-api
for our Spark pipelines. As you know, when evaluating a new library, we need to ask ourselves if it is being actively maintained and assess any risks of becoming too dependent on it. Thus, please allow me to ask the following questions:I believe that having answers to those questions would be beneficial to my company, other companies or projects that may be wondering the same things when evaluating
kotlin-spark-api
, and perhaps help reassure people and increase adoption in the short/medium term.Thanks!