Ok, I have done some research and here are some proposed names :
Toree
Zawn
Smirr
Inlata
We used Sam approach and replaced vowels from our previous choice and came
up with Toree, and if nobody have any issues with the name, we will use it.
I will leave this open for couple days before I update
Hi,
On Tue, Dec 15, 2015 at 7:26 PM, Luciano Resende wrote:
> ...We used Sam approach and replaced vowels from our previous choice and came
> up with Toree, and if nobody have any issues with the name, we will use it
Note that we have TomEE which is fairly similar.
On Mon, Nov 30, 2015 at 4:13 PM, Julien Le Dem wrote:
> Sorry for the late reply.
> FYI there is an opensource project called torii already:
> https://vestorly.github.io/torii/
> Whether there is a trademark or not, I'd recommend a name that does not
> collide with another
On Wed, Dec 2, 2015 at 5:52 PM, Luciano Resende wrote:
> On Mon, Nov 30, 2015 at 4:13 PM, Julien Le Dem wrote:
>
>> Sorry for the late reply.
>> FYI there is an opensource project called torii already:
>> https://vestorly.github.io/torii/
>> Whether there
Sorry for the late reply.
FYI there is an opensource project called torii already:
https://vestorly.github.io/torii/
Whether there is a trademark or not, I'd recommend a name that does not
collide with another project.
On Wed, Nov 25, 2015 at 9:00 PM, Luciano Resende
wrote:
Hi David & All,
The 'spark-kernel/torii' is a "good to have" tool.
Pardon me, I am not the judge in any way.After going through this thread and
the referred links, it seems, by giving it a decent publicity in Apache Spark
(may be provide link, etc.),would be sufficient enough for its survival
> On 13 Nov 2015, at 22:19, Matei Zaharia wrote:
>
> One question about this from the Spark side: have you considered giving the
> project a different name so that it doesn't sound like a Spark component?
> Right now "Spark Kernel" may be confused with "Spark Core"
Hi Taylor, I don't know the Spark community's opinion on the "outright vs
subproject" issue, although I have told a couple people in that community about
the proposal and have posted an FYI to the spark-dev list. From a technical
perspective, Spark-Kernel mainly uses public Spark APIs (except for
One question about this from the Spark side: have you considered giving the
project a different name so that it doesn't sound like a Spark component? Right
now "Spark Kernel" may be confused with "Spark Core" and things like that. I
don't see a lot of Apache TLPs with related names, though
Thanks for the reference Alex. It answers my question regarding the path you
chose.
-Taylor
> On Nov 13, 2015, at 12:13 AM, Alexander Bezzubov wrote:
>
> Hi,
>
> it looks pretty interesting, especially a part about integration with
> Zeppelin as another Scala
> On Nov 13, 2015, at 5:19 PM, Matei Zaharia wrote:
>
> In terms of whether to put this in Apache Spark proper, we can have a
> discussion about it later, but my feeling is that it's not necessary. One
> reason is that this only uses public APIs, and another is that
On Fri, Nov 13, 2015 at 6:49 PM, Reynold Xin wrote:
>
> I'd also like to second Matei that spark-kernel as a name is fairly
> confusing. It only makes sense when viewing from IPython notebook's point
> of view to refer to these things as kernels. Outside of that context, it
>
Recent example was the MySos proposal, it is MySQL in Mesos, which
renamed to Cotton before officially entering incubator.
I think it would be easier for infra if the name is decided a bit
early to something that have better chance to pass incubation.
- Henry
On Fri, Nov 13, 2015 at 3:57 PM,
I'm happy to mentor the incubation if you are still looking for mentors.
I'd also like to second Matei that spark-kernel as a name is fairly
confusing. It only makes sense when viewing from IPython notebook's point
of view to refer to these things as kernels. Outside of that context, it
sounds
On Fri, Nov 13, 2015 at 2:13 AM, Alexander Bezzubov
wrote:
> Hi,
>
> it looks pretty interesting, especially a part about integration with
> Zeppelin as another Scala interpreter implementation.
>
> AFAIK there was a discussion on including Spark-Kernel to spark core
>
Hi David,
I would be happy to help out as a mentor.
thanks
— Hitesh
On Nov 12, 2015, at 4:17 PM, da...@fallside.com wrote:
> Hello, we would like to start a discussion on accepting the Spark-Kernel,
> a mechanism for applications to interactively and remotely access Apache
> Spark, into the
Hi,
it looks pretty interesting, especially a part about integration with
Zeppelin as another Scala interpreter implementation.
AFAIK there was a discussion on including Spark-Kernel to spark core
https://issues.apache.org/jira/browse/SPARK-4605 but not sure about a
possibility of becoming a
Hello, we would like to start a discussion on accepting the Spark-Kernel,
a mechanism for applications to interactively and remotely access Apache
Spark, into the Apache Incubator.
The proposal is available online at
https://wiki.apache.org/incubator/SparkKernelProposal, and it is appended
to
I'd be happy to help as a mentor if you need more.
On Thu, Nov 12, 2015 at 4:17 PM, wrote:
> Hello, we would like to start a discussion on accepting the Spark-Kernel,
> a mechanism for applications to interactively and remotely access Apache
> Spark, into the Apache
Just a quick (or maybe not :) ) question...
Given the tight coupling to the Apache Spark project, were there any
considerations or discussions with the Spark community regarding including the
Spark-Kernel functionality outright in Spark, or the possibility of becoming a
subproject?
I'm just
20 matches
Mail list logo