Re: Interested in contributing to SPARK-24815

[Sean Owen]

Formally, an ICLA is required, and you can read more here:
https://www.apache.org/licenses/contributor-agreements.html

In practice, it's unrealistic to collect and verify an ICLA for every PR
contributed by 1000s of people. We have not gated on that.
But, contributions are in all cases governed by the same terms, even
without a signed ICLA. That's the verbiage you're referring to.
A CLA is a good idea, for sure, if there are any questions about the terms
of your contribution.

Here there does seem to be a question - retaining Twilio copyright headers
in source code. That is generally not what would happen for your everyday
contributions to an ASF project, as the copyright header (and CLAs) already
describe the relevant questions of rights: it has been licensed to the ASF.
(There are other situations where retaining a distinct copyright header is
required, typically when adding code licensed under another OSS license,
but I don't think they apply here)

I would say you should review and execute a CCLA for Twilio (assuming you
agree with the terms) to avoid doubt.


On Thu, Aug 3, 2023 at 6:34 PM Rinat Shangeeta 
wrote:

> (Adding my manager Eugene Kim who will cover me as I plan to be out of the
> office soon)
>
> Hi Kent and Sean,
>
> Nice to meet you. I am working on the OSS legal aspects with Pavan who is
> planning to make the contribution request to the Spark project. I saw that
> Sean mentioned in his email that the contributions would be governed under
> the ASF CCLA. In the Spark contribution guidelines
> , there is no mention of
> having to sign a CCLA. In fact, this is what I found in the contribution
> guidelines:
>
> Contributing code changes
>
> Please review the preceding section before proposing a code change. This
> section documents how to do so.
>
> When you contribute code, you affirm that the contribution is your
> original work and that you license the work to the project under the
> project’s open source license. Whether or not you state this explicitly,
> by submitting any copyrighted material via pull request, email, or other
> means you agree to license the material under the project’s open source
> license and warrant that you have the legal authority to do so.
>
> Can you please point us to an authoritative source about the process?
>
> Also, is there a way to find out if a signed CCLA already exists for
> Twilio from your end? Thanks and appreciate your help!
>
>
> Best,
> Rinat
>
> *Rinat Shangeeta*
> Sr. Patent/Open Source Counsel
> [image: Twilio] 
>
>
> On Wed, Jul 26, 2023 at 2:27 PM Pavan Kotikalapudi <
> pkotikalap...@twilio.com> wrote:
>
>> Thanks for the response with all the information Sean and Kent.
>>
>> Is there a way to figure out if my employer (Twilio) part of CCLA?
>>
>> cc'ing: @Rinat Shangeeta  our Open Source Counsel
>> at twilio
>>
>> Thank you,
>>
>> Pavan
>>
>> On Tue, Jul 25, 2023 at 10:48 PM Kent Yao  wrote:
>>
>>> Hi Pavan,
>>>
>>> Refer to the ASF Source Header and Copyright Notice Policy[1], code
>>> directly submitted to ASF should include the Apache license header
>>> without any additional copyright notice.
>>>
>>>
>>> Kent Yao
>>>
>>> [1]
>>> https://urldefense.com/v3/__https://www.apache.org/legal/src-headers.html*headers__;Iw!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmrsufzUc$
>>>
>>> Sean Owen  于2023年7月25日周二 07:22写道：
>>>
>>> >
>>> > When contributing to an ASF project, it's governed by the terms of the
>>> ASF ICLA:
>>> https://urldefense.com/v3/__https://www.apache.org/licenses/icla.pdf__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmZDPppZg$
>>> or CCLA:
>>> https://urldefense.com/v3/__https://www.apache.org/licenses/cla-corporate.pdf__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmUNwE-5A$
>>> >
>>> > I don't believe ASF projects ever retain an original author copyright
>>> statement, but rather source files have a statement like:
>>> >
>>> > ...
>>> >  * Licensed to the Apache Software Foundation (ASF) under one or more
>>> >  * contributor license agreements.  See the NOTICE file distributed
>>> with
>>> >  * this work for additional information regarding copyright ownership.
>>> > ...
>>> >
>>> > While it's conceivable that such a statement could live in a NOTICE
>>> file, I don't believe that's been done for any of the thousands of other
>>> contributors. That's really more for noting the license of
>>> non-Apache-licensed code. Code directly contributed to the project is
>>> assumed to have been licensed per above already.
>>> >
>>> > It might be wise to review the CCLA with Twilio and consider
>>> establishing that to govern contributions.
>>> >
>>> > On Mon, Jul 24, 2023 at 6:10 PM Pavan Kotikalapudi <
>>> pkotikalap...@twilio.com.invalid> wrote:
>>> >>
>>> >> Hi Spark Dev,
>>> >>
>>> >> My name is Pavan Kotikalapudi, I work at 

Re: Interested in contributing to SPARK-24815

[Rinat Shangeeta]

(Adding my manager Eugene Kim who will cover me as I plan to be out of the
office soon)

Hi Kent and Sean,

Nice to meet you. I am working on the OSS legal aspects with Pavan who is
planning to make the contribution request to the Spark project. I saw that
Sean mentioned in his email that the contributions would be governed under
the ASF CCLA. In the Spark contribution guidelines
, there is no mention of having
to sign a CCLA. In fact, this is what I found in the contribution
guidelines:

Contributing code changes

Please review the preceding section before proposing a code change. This
section documents how to do so.

When you contribute code, you affirm that the contribution is your original
work and that you license the work to the project under the project’s open
source license. Whether or not you state this explicitly, by submitting any
copyrighted material via pull request, email, or other means you agree
to license
the material under the project’s open source license and warrant that you
have the legal authority to do so.

Can you please point us to an authoritative source about the process?

Also, is there a way to find out if a signed CCLA already exists for Twilio
from your end? Thanks and appreciate your help!


Best,
Rinat

*Rinat Shangeeta*
Sr. Patent/Open Source Counsel
[image: Twilio] 


On Wed, Jul 26, 2023 at 2:27 PM Pavan Kotikalapudi 
wrote:

> Thanks for the response with all the information Sean and Kent.
>
> Is there a way to figure out if my employer (Twilio) part of CCLA?
>
> cc'ing: @Rinat Shangeeta  our Open Source Counsel
> at twilio
>
> Thank you,
>
> Pavan
>
> On Tue, Jul 25, 2023 at 10:48 PM Kent Yao  wrote:
>
>> Hi Pavan,
>>
>> Refer to the ASF Source Header and Copyright Notice Policy[1], code
>> directly submitted to ASF should include the Apache license header
>> without any additional copyright notice.
>>
>>
>> Kent Yao
>>
>> [1]
>> https://urldefense.com/v3/__https://www.apache.org/legal/src-headers.html*headers__;Iw!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmrsufzUc$
>>
>> Sean Owen  于2023年7月25日周二 07:22写道：
>>
>> >
>> > When contributing to an ASF project, it's governed by the terms of the
>> ASF ICLA:
>> https://urldefense.com/v3/__https://www.apache.org/licenses/icla.pdf__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmZDPppZg$
>> or CCLA:
>> https://urldefense.com/v3/__https://www.apache.org/licenses/cla-corporate.pdf__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmUNwE-5A$
>> >
>> > I don't believe ASF projects ever retain an original author copyright
>> statement, but rather source files have a statement like:
>> >
>> > ...
>> >  * Licensed to the Apache Software Foundation (ASF) under one or more
>> >  * contributor license agreements.  See the NOTICE file distributed with
>> >  * this work for additional information regarding copyright ownership.
>> > ...
>> >
>> > While it's conceivable that such a statement could live in a NOTICE
>> file, I don't believe that's been done for any of the thousands of other
>> contributors. That's really more for noting the license of
>> non-Apache-licensed code. Code directly contributed to the project is
>> assumed to have been licensed per above already.
>> >
>> > It might be wise to review the CCLA with Twilio and consider
>> establishing that to govern contributions.
>> >
>> > On Mon, Jul 24, 2023 at 6:10 PM Pavan Kotikalapudi <
>> pkotikalap...@twilio.com.invalid> wrote:
>> >>
>> >> Hi Spark Dev,
>> >>
>> >> My name is Pavan Kotikalapudi, I work at Twilio.
>> >>
>> >> I am looking to contribute to this spark issue
>> https://urldefense.com/v3/__https://issues.apache.org/jira/browse/SPARK-24815__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmgOh9sIg$
>> .
>> >>
>> >> There is a clause from the company's OSS saying
>> >>
>> >> - The proposed contribution is about 100 lines of code modification in
>> the Spark project, involving two files - this is considered a large
>> contribution. An appropriate Twilio copyright notice needs to be added for
>> the portion of code that is newly added.
>> >>
>> >> Please let me know if that is acceptable?
>> >>
>> >> Thank you,
>> >>
>> >> Pavan
>> >>
>>
>

Re: Interested in contributing to SPARK-24815

[Pavan Kotikalapudi]

Thanks for the response with all the information Sean and Kent.

Is there a way to figure out if my employer (Twilio) part of CCLA?

cc'ing: @Rinat Shangeeta  our Open Source Counsel at
twilio

Thank you,

Pavan

On Tue, Jul 25, 2023 at 10:48 PM Kent Yao  wrote:

> Hi Pavan,
>
> Refer to the ASF Source Header and Copyright Notice Policy[1], code
> directly submitted to ASF should include the Apache license header
> without any additional copyright notice.
>
>
> Kent Yao
>
> [1]
> https://urldefense.com/v3/__https://www.apache.org/legal/src-headers.html*headers__;Iw!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmrsufzUc$
>
> Sean Owen  于2023年7月25日周二 07:22写道：
>
> >
> > When contributing to an ASF project, it's governed by the terms of the
> ASF ICLA:
> https://urldefense.com/v3/__https://www.apache.org/licenses/icla.pdf__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmZDPppZg$
> or CCLA:
> https://urldefense.com/v3/__https://www.apache.org/licenses/cla-corporate.pdf__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmUNwE-5A$
> >
> > I don't believe ASF projects ever retain an original author copyright
> statement, but rather source files have a statement like:
> >
> > ...
> >  * Licensed to the Apache Software Foundation (ASF) under one or more
> >  * contributor license agreements.  See the NOTICE file distributed with
> >  * this work for additional information regarding copyright ownership.
> > ...
> >
> > While it's conceivable that such a statement could live in a NOTICE
> file, I don't believe that's been done for any of the thousands of other
> contributors. That's really more for noting the license of
> non-Apache-licensed code. Code directly contributed to the project is
> assumed to have been licensed per above already.
> >
> > It might be wise to review the CCLA with Twilio and consider
> establishing that to govern contributions.
> >
> > On Mon, Jul 24, 2023 at 6:10 PM Pavan Kotikalapudi <
> pkotikalap...@twilio.com.invalid> wrote:
> >>
> >> Hi Spark Dev,
> >>
> >> My name is Pavan Kotikalapudi, I work at Twilio.
> >>
> >> I am looking to contribute to this spark issue
> https://urldefense.com/v3/__https://issues.apache.org/jira/browse/SPARK-24815__;!!NCc8flgU!c_mZKzBbSjJtYRjillV20gRzzzDOgW2ooH6ctfrqaJA8Eu4D5yfA7OlQnGm5JpdAZIU_doYmgOh9sIg$
> .
> >>
> >> There is a clause from the company's OSS saying
> >>
> >> - The proposed contribution is about 100 lines of code modification in
> the Spark project, involving two files - this is considered a large
> contribution. An appropriate Twilio copyright notice needs to be added for
> the portion of code that is newly added.
> >>
> >> Please let me know if that is acceptable?
> >>
> >> Thank you,
> >>
> >> Pavan
> >>
>

Re: Interested in contributing to SPARK-24815

[Kent Yao]

Hi Pavan,

Refer to the ASF Source Header and Copyright Notice Policy[1], code
directly submitted to ASF should include the Apache license header
without any additional copyright notice.


Kent Yao

[1] https://www.apache.org/legal/src-headers.html#headers

Sean Owen  于2023年7月25日周二 07:22写道：

>
> When contributing to an ASF project, it's governed by the terms of the ASF 
> ICLA: https://www.apache.org/licenses/icla.pdf or CCLA: 
> https://www.apache.org/licenses/cla-corporate.pdf
>
> I don't believe ASF projects ever retain an original author copyright 
> statement, but rather source files have a statement like:
>
> ...
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
> ...
>
> While it's conceivable that such a statement could live in a NOTICE file, I 
> don't believe that's been done for any of the thousands of other 
> contributors. That's really more for noting the license of 
> non-Apache-licensed code. Code directly contributed to the project is assumed 
> to have been licensed per above already.
>
> It might be wise to review the CCLA with Twilio and consider establishing 
> that to govern contributions.
>
> On Mon, Jul 24, 2023 at 6:10 PM Pavan Kotikalapudi 
>  wrote:
>>
>> Hi Spark Dev,
>>
>> My name is Pavan Kotikalapudi, I work at Twilio.
>>
>> I am looking to contribute to this spark issue 
>> https://issues.apache.org/jira/browse/SPARK-24815.
>>
>> There is a clause from the company's OSS saying
>>
>> - The proposed contribution is about 100 lines of code modification in the 
>> Spark project, involving two files - this is considered a large 
>> contribution. An appropriate Twilio copyright notice needs to be added for 
>> the portion of code that is newly added.
>>
>> Please let me know if that is acceptable?
>>
>> Thank you,
>>
>> Pavan
>>

-
To unsubscribe e-mail: user-unsubscr...@spark.apache.org

Re: Interested in contributing to SPARK-24815

[Sean Owen]

When contributing to an ASF project, it's governed by the terms of the ASF
ICLA: https://www.apache.org/licenses/icla.pdf or CCLA:
https://www.apache.org/licenses/cla-corporate.pdf

I don't believe ASF projects ever retain an original author copyright
statement, but rather source files have a statement like:

...
 * Licensed to the Apache Software Foundation (ASF) under one or more
 * contributor license agreements.  See the NOTICE file distributed with
 * this work for additional information regarding copyright ownership.
...

While it's conceivable that such a statement could live in a NOTICE file, I
don't believe that's been done for any of the thousands of other
contributors. That's really more for noting the license of
non-Apache-licensed code. Code directly contributed to the project is
assumed to have been licensed per above already.

It might be wise to review the CCLA with Twilio and consider establishing
that to govern contributions.

On Mon, Jul 24, 2023 at 6:10 PM Pavan Kotikalapudi
 wrote:

> Hi Spark Dev,
>
> My name is Pavan Kotikalapudi, I work at Twilio.
>
> I am looking to contribute to this spark issue
> https://issues.apache.org/jira/browse/SPARK-24815.
>
> There is a clause from the company's OSS saying
>
> - The proposed contribution is about 100 lines of code modification in the
> Spark project, involving two files - this is considered a large
> contribution. An appropriate Twilio copyright notice needs to be added for
> the portion of code that is newly added.
>
> Please let me know if that is acceptable?
>
> Thank you,
>
> Pavan
>
>

Fwd: Interested in contributing to SPARK-24815

[Pavan Kotikalapudi]

Hi Spark Dev,

My name is Pavan Kotikalapudi, I work at Twilio.

I am looking to contribute to this spark issue
https://issues.apache.org/jira/browse/SPARK-24815.

There is a clause from the company's OSS saying

- The proposed contribution is about 100 lines of code modification in the
Spark project, involving two files - this is considered a large
contribution. An appropriate Twilio copyright notice needs to be added for
the portion of code that is newly added.

Please let me know if that is acceptable?

Thank you,

Pavan

Re: Contributing to Spark MLLib

[Gourav Sengupta]

Hi,

Holden Karau has some fantastic videos in her channel which will be quite
helpful.

Thanks
Gourav

On Sun, 16 Jul 2023, 19:15 Brian Huynh,  wrote:

> Good morning Dipayan,
>
> Happy to see another contributor!
>
> Please go through this document for contributors. Please note the
> MLlib-specific contribution guidelines section in particular.
>
> https://spark.apache.org/contributing.html
>
> Since you are looking for something to start with, take a look at this
> Jira query for starter issues.
>
>
> https://issues.apache.org/jira/browse/SPARK-38719?jql=project%20%3D%20SPARK%20AND%20labels%20%3D%20%22starter%22%20AND%20status%20%3D%20Open
>
> Cheers,
> Brian
>
> On Sun, Jul 16, 2023 at 8:49 AM Dipayan Dev 
> wrote:
>
>> Hi Spark Community,
>>
>> A very good morning to you.
>>
>> I am using Spark from last few years now, and new to the community.
>>
>> I am very much interested to be a contributor.
>>
>> I am looking to contribute to Spark MLLib. Can anyone please suggest me
>> how to start with contributing to any new MLLib feature? Is there any new
>> features in line and the best way to explore this?
>> Looking forward to little guidance to start with.
>>
>>
>> Thanks
>> Dipayan
>> --
>>
>>
>>
>> With Best Regards,
>>
>> Dipayan Dev
>> Author of *Deep Learning with Hadoop
>> *
>> M.Tech (AI), IISc, Bangalore
>>
>
>
> --
> From Brian H.
>

Re: Contributing to Spark MLLib

[Brian Huynh]

Good morning Dipayan,

Happy to see another contributor!

Please go through this document for contributors. Please note the
MLlib-specific contribution guidelines section in particular.

https://spark.apache.org/contributing.html

Since you are looking for something to start with, take a look at this Jira
query for starter issues.

https://issues.apache.org/jira/browse/SPARK-38719?jql=project%20%3D%20SPARK%20AND%20labels%20%3D%20%22starter%22%20AND%20status%20%3D%20Open

Cheers,
Brian

On Sun, Jul 16, 2023 at 8:49 AM Dipayan Dev  wrote:

> Hi Spark Community,
>
> A very good morning to you.
>
> I am using Spark from last few years now, and new to the community.
>
> I am very much interested to be a contributor.
>
> I am looking to contribute to Spark MLLib. Can anyone please suggest me
> how to start with contributing to any new MLLib feature? Is there any new
> features in line and the best way to explore this?
> Looking forward to little guidance to start with.
>
>
> Thanks
> Dipayan
> --
>
>
>
> With Best Regards,
>
> Dipayan Dev
> Author of *Deep Learning with Hadoop
> *
> M.Tech (AI), IISc, Bangalore
>


-- 
>From Brian H.

Contributing to Spark MLLib

[Dipayan Dev]

Hi Spark Community,

A very good morning to you.

I am using Spark from last few years now, and new to the community.

I am very much interested to be a contributor.

I am looking to contribute to Spark MLLib. Can anyone please suggest me how
to start with contributing to any new MLLib feature? Is there any new
features in line and the best way to explore this?
Looking forward to little guidance to start with.


Thanks
Dipayan
-- 



With Best Regards,

Dipayan Dev
Author of *Deep Learning with Hadoop
*
M.Tech (AI), IISc, Bangalore

Re: Contributing to Spark

[cht liu]

Hi Sam
A great way to contribute to Spark is to help answer user questions on the
user@spark.apache.org mailing list or on StackOverflow.

2017-03-20 11:50 GMT+08:00 Nick Pentreath <nick.pentre...@gmail.com>:

> If you have experience and interest in Python then PySpark is a good area
> to look into.
>
> Yes, adding things like tests & documentation is a good starting point.
> Start out relatively small and go from there. Adding new wrappers to python
> for ML is useful for slightly larger tasks.
>
>
>
>
> On Mon, 20 Mar 2017 at 02:39, Sam Elamin <hussam.ela...@gmail.com> wrote:
>
>> Hi All,
>>
>> I would like to start contributing to Spark if possible, its an amazing
>> technology and I would love to get involved
>>
>>
>> The contributing page <http://spark.apache.org/contributing.html> states
>> this "consult the list of starter tasks in JIRA, or ask the
>> user@spark.apache.org mailing list."
>>
>>
>> Can anyone guide me on where is best to start? What are these "starter
>> tasks"?
>>
>> I was thinking adding tests would be a good place to begin when dealing
>> with any new code base, perhaps to Pyspark since Scala seems a bit more
>> stable
>>
>>
>> Also - if at all possible - I would really appreciate if any of the
>> contributors or PMC members would be willing to mentor or guide me in this.
>> Any help would be greatly appreciated!
>>
>>
>> Regards
>> Sam
>>
>>
>>

Re: Contributing to Spark

[Nick Pentreath]

If you have experience and interest in Python then PySpark is a good area
to look into.

Yes, adding things like tests & documentation is a good starting point.
Start out relatively small and go from there. Adding new wrappers to python
for ML is useful for slightly larger tasks.




On Mon, 20 Mar 2017 at 02:39, Sam Elamin <hussam.ela...@gmail.com> wrote:

> Hi All,
>
> I would like to start contributing to Spark if possible, its an amazing
> technology and I would love to get involved
>
>
> The contributing page <http://spark.apache.org/contributing.html> states
> this "consult the list of starter tasks in JIRA, or ask the
> user@spark.apache.org mailing list."
>
>
> Can anyone guide me on where is best to start? What are these "starter
> tasks"?
>
> I was thinking adding tests would be a good place to begin when dealing
> with any new code base, perhaps to Pyspark since Scala seems a bit more
> stable
>
>
> Also - if at all possible - I would really appreciate if any of the
> contributors or PMC members would be willing to mentor or guide me in this.
> Any help would be greatly appreciated!
>
>
> Regards
> Sam
>
>
>

Contributing to Spark

[Sam Elamin]

Hi All,

I would like to start contributing to Spark if possible, its an amazing
technology and I would love to get involved


The contributing page <http://spark.apache.org/contributing.html> states
this "consult the list of starter tasks in JIRA, or ask the
user@spark.apache.org mailing list."


Can anyone guide me on where is best to start? What are these "starter
tasks"?

I was thinking adding tests would be a good place to begin when dealing
with any new code base, perhaps to Pyspark since Scala seems a bit more
stable


Also - if at all possible - I would really appreciate if any of the
contributors or PMC members would be willing to mentor or guide me in this.
Any help would be greatly appreciated!


Regards
Sam

Contributors, read me! Updated Contributing to Spark wiki

[Sean Owen]

Following several discussions about how to improve the contribution
process in Spark, I've overhauled the guide to contributing. Anyone
who is going to contribute needs to read it, as it has more formal
guidance about the process:

https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark

We may push back harder now on pull requests and JIRAs that don't
follow this guidance. It will help everyone spend less time to get
changes in, and spend less time on duplicated effort, or changes that
won't.

A summary of key points is found in CONTRIBUTING.md, a prompt
presented before opening pull requests
(https://github.com/apache/spark/blob/master/CONTRIBUTING.md):

- Is the change important and ready enough to ask the community to
spend time reviewing?
- Have you searched for existing, related JIRAs and pull requests?
- Is this a new feature that can stand alone as a package on
http://spark-packages.org ?
- Is the change being proposed clearly explained and motivated?

-
To unsubscribe, e-mail: user-unsubscr...@spark.apache.org
For additional commands, e-mail: user-h...@spark.apache.org