Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java support #454

Open
jonathanindig opened this issue Sep 20, 2019 · 4 comments
Open

Java support #454

jonathanindig opened this issue Sep 20, 2019 · 4 comments
Labels
feature-idea A feature request or idea for something to implement in the future language-support

Comments

@jonathanindig
Copy link
Collaborator

Some Java libraries take in POJOs for ser/de, etc.

It would be easier to work with those libraries if we could define POJOs in Polynote (instead of Scala classes).

@sjparsons
Copy link

I'm on a team that uses Java for interacting with Spark and I'd like the ability to run Java code in a notebook. What are the blockers that prevent using Java in a notebook?

@jonathanindig
Copy link
Collaborator Author

Welcome, @sjparsons! Thanks for your interest in Polynote :)

Java is definitely high on the list of new languages we'd like to add, but we just haven't gotten there yet.

We're planning to add some rough developer documentation soon, but the main part of adding a new language is implementing this interface: https://github.com/polynote/polynote/blob/master/polynote-kernel/src/main/scala/polynote/kernel/interpreter/Interpreter.scala

A PR would be most welcome!

@davidpham87
Copy link

Once we get Java, I guess all other JVM language could be integrated as well (e.g Clojure)?

@seralf
Copy link

seralf commented Oct 26, 2019

Some Java libraries take in POJOs for ser/de, etc.

It would be easier to work with those libraries if we could define POJOs in Polynote (instead of Scala classes).

a partial workaround when using Java libraries requiring POJO from Scala is the usage of annotation for classes (please ignore this comment if you already mentioned it):
https://alvinalexander.com/scala/scala-javabeans-beanproperty-annotation
anyway is quite annoying to write classes like this, especially case classes, as it introduces a lot of boilerplate code... my solution in some case was to actually duplicate the model, and provide the beans by requests, but it's not always possible.

@jonathanindig jonathanindig added feature-idea A feature request or idea for something to implement in the future language-support labels Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-idea A feature request or idea for something to implement in the future language-support
Projects
None yet
Development

No branches or pull requests

4 participants