@Saisai This will not be a wrapper around the REST API. The plan is to support a Livy POST /sessions request where kind == "sparkdotnet". Livy will eventually push this request down to the ReplDriver, and in turn the ReplDriver will create a new SparkDotnet Interpreter class. This will be similar to how the PythonInterpreter, SparkRInterpreter, and SQLInterpreter classes get instantiated and used.
Regards, -Steve On Sun, Jan 12, 2020 at 5:45 PM Saisai Shao <sai.sai.s...@gmail.com> wrote: > Is this just a wrapper of Livy REST API, or it could support Livy Job API? > > From my opinion, if it is just a wrapper of REST API, then it would be > better to maintain out of Livy, since REST API is language independent, if > we're going to have all the languages support in Livy, then it is hard to > maintain. > > Just my two cents. > > Thanks > Saisai > > Steve Suh <suhst...@gmail.com> 于2020年1月12日周日 下午3:49写道： > > > Hi, > > > > I contribute to the .NET for Apache Spark < > https://github.com/dotnet/spark > > > > > project and we have seen *a lot* of *user interest* in providing first > > class notebook support for *.NET for Apache Spark*. > > > > Livy currently supports *Scala*, *Python *and *R **interactive sessions*. > > We have a working prototype > > < > > > https://github.com/dotnet/spark/tree/master/deployment/HDI-Spark/Notebooks > > > > > available > > that adds support for a Spark *Dotnet **interactive session* and I would > > like to know if the Livy community would be interested in adding this > > feature to the main code base. If so, please let me know and I can work > on > > creating this PR. > > > > For now, I've created a Jira item > > <https://issues.apache.org/jira/browse/LIVY-742> to track this. > > > > > > Regards, > > -Steve > > >
