Re: Build completed: spark 866-master

[Shivaram Venkataraman]

Thanks for investigating. We should file an INFRA jira about this.

Shivaram

On Mar 4, 2017 16:20, "Reynold Xin"  wrote:

> Most of the previous notifications were caught as spam. We should really
> disable this.
>
>
> On Sat, Mar 4, 2017 at 4:17 PM Hyukjin Kwon  wrote:
>
>> Oh BTW, I was asked about this by Reynold. Few month ago and I said the
>> similar answer.
>>
>> I think I am not supposed to don't recieve the emails (not sure but I
>> have not recieved) so I am not too sure if this has happened so far or
>> occationally.
>>
>>
>>
>> On 5 Mar 2017 9:08 a.m., "Hyukjin Kwon"  wrote:
>>
>> I think we should ask to disable this within Web UI configuration. In
>> this JIRA, https://issues.apache.org/jira/browse/INFRA-12590, Daniel said
>>
>> > ... configured to send build results to dev@spark.apache.org.
>>
>> In the case of my accounts, I manually went to https://ci.appveyor.com/
>> notifications and configured them all as  "Do not send" and it does not
>> send me any email.
>>
>> However, in case of AFS account, this turns out an assumption because I
>> don't know how it is defined as I can't access.
>>
>> This might be defined in account - https://ci.appveyor.com/notifications
>> or in project - https://ci.appveyor.com/project/ApacheSoftwareFoundation/
>> spark/settings
>>
>> I'd like to note that I disabled the notification in the appveyor.yml but
>> it seems the configurations are merged in Web UI,
>> according to the documentation (https://www.appveyor.com/
>> docs/notifications/#global-email-notifications).
>>
>> > Warning: Notifications defined on project settings UI are merged with
>> notifications defined in appveyor.yml.
>>
>> Should we maybe an INFRA JIRA to check and ask this?
>>
>>
>>
>> 2017-03-05 8:31 GMT+09:00 Shivaram Venkataraman <
>> shiva...@eecs.berkeley.edu>:
>>
>> I'm not sure why the AppVeyor updates are coming to the dev list.
>> Hyukjin -- Do you know if we made any recent changes that might have caused
>> this ?
>>
>> Thanks
>> Shivaram
>>
>> -- Forwarded message --
>> From: *AppVeyor* 
>> Date: Sat, Mar 4, 2017 at 2:46 PM
>> Subject: Build completed: spark 866-master
>> To: dev@spark.apache.org
>>
>>
>> Build spark 866-master completed
>> 
>>
>> Commit ccf54f64d9  by Xiao
>> Li  on 3/4/2017 9:50 PM:
>> fix.
>>
>> Configure your notification preferences
>> 
>> - To
>> unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>
>>
>>

Re: Build completed: spark 866-master

[Reynold Xin]

Most of the previous notifications were caught as spam. We should really
disable this.


On Sat, Mar 4, 2017 at 4:17 PM Hyukjin Kwon  wrote:

> Oh BTW, I was asked about this by Reynold. Few month ago and I said the
> similar answer.
>
> I think I am not supposed to don't recieve the emails (not sure but I have
> not recieved) so I am not too sure if this has happened so far or
> occationally.
>
>
>
> On 5 Mar 2017 9:08 a.m., "Hyukjin Kwon"  wrote:
>
> I think we should ask to disable this within Web UI configuration. In this
> JIRA, https://issues.apache.org/jira/browse/INFRA-12590, Daniel said
>
> > ... configured to send build results to dev@spark.apache.org.
>
> In the case of my accounts, I manually went to
> https://ci.appveyor.com/notifications and configured them all as  "Do not
> send" and it does not send me any email.
>
> However, in case of AFS account, this turns out an assumption because I
> don't know how it is defined as I can't access.
>
> This might be defined in account - https://ci.appveyor.com/notifications
> or in project -
> https://ci.appveyor.com/project/ApacheSoftwareFoundation/spark/settings
>
> I'd like to note that I disabled the notification in the appveyor.yml but
> it seems the configurations are merged in Web UI,
> according to the documentation (
> https://www.appveyor.com/docs/notifications/#global-email-notifications).
>
> > Warning: Notifications defined on project settings UI are merged with
> notifications defined in appveyor.yml.
>
> Should we maybe an INFRA JIRA to check and ask this?
>
>
>
> 2017-03-05 8:31 GMT+09:00 Shivaram Venkataraman <
> shiva...@eecs.berkeley.edu>:
>
> I'm not sure why the AppVeyor updates are coming to the dev list.  Hyukjin
> -- Do you know if we made any recent changes that might have caused this ?
>
> Thanks
> Shivaram
>
> -- Forwarded message --
> From: *AppVeyor* 
> Date: Sat, Mar 4, 2017 at 2:46 PM
> Subject: Build completed: spark 866-master
> To: dev@spark.apache.org
>
>
> Build spark 866-master completed
> 
>
> Commit ccf54f64d9  by Xiao
> Li  on 3/4/2017 9:50 PM:
> fix.
>
> Configure your notification preferences
> 
> - To
> unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>
>
>

Re: Build completed: spark 866-master

[Hyukjin Kwon]

Oh BTW, I was asked about this by Reynold. Few month ago and I said the
similar answer.

I think I am not supposed to don't recieve the emails (not sure but I have
not recieved) so I am not too sure if this has happened so far or
occationally.



On 5 Mar 2017 9:08 a.m., "Hyukjin Kwon"  wrote:

> I think we should ask to disable this within Web UI configuration. In this
> JIRA, https://issues.apache.org/jira/browse/INFRA-12590, Daniel said
>
> > ... configured to send build results to dev@spark.apache.org.
>
> In the case of my accounts, I manually went to https://ci.appveyor.com/not
> ifications and configured them all as  "Do not send" and it does not send
> me any email.
>
> However, in case of AFS account, this turns out an assumption because I
> don't know how it is defined as I can't access.
>
> This might be defined in account - https://ci.appveyor.com/notifications
> or in project - https://ci.appveyor.com/projec
> t/ApacheSoftwareFoundation/spark/settings
>
> I'd like to note that I disabled the notification in the appveyor.yml but
> it seems the configurations are merged in Web UI,
> according to the documentation (https://www.appveyor.com/docs
> /notifications/#global-email-notifications).
>
> > Warning: Notifications defined on project settings UI are merged with
> notifications defined in appveyor.yml.
>
> Should we maybe an INFRA JIRA to check and ask this?
>
>
>
> 2017-03-05 8:31 GMT+09:00 Shivaram Venkataraman <
> shiva...@eecs.berkeley.edu>:
>
>> I'm not sure why the AppVeyor updates are coming to the dev list.
>> Hyukjin -- Do you know if we made any recent changes that might have caused
>> this ?
>>
>> Thanks
>> Shivaram
>>
>> -- Forwarded message --
>> From: AppVeyor 
>> Date: Sat, Mar 4, 2017 at 2:46 PM
>> Subject: Build completed: spark 866-master
>> To: dev@spark.apache.org
>>
>>
>> Build spark 866-master completed
>> 
>>
>> Commit ccf54f64d9  by Xiao
>> Li  on 3/4/2017 9:50 PM:
>> fix.
>>
>> Configure your notification preferences
>> 
>> - To
>> unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>>
>>
>

Re: Build completed: spark 866-master

[Hyukjin Kwon]

I think we should ask to disable this within Web UI configuration. In this
JIRA, https://issues.apache.org/jira/browse/INFRA-12590, Daniel said

> ... configured to send build results to dev@spark.apache.org.

In the case of my accounts, I manually went to https://ci.appveyor.com/
notifications and configured them all as  "Do not send" and it does not
send me any email.

However, in case of AFS account, this turns out an assumption because I
don't know how it is defined as I can't access.

This might be defined in account - https://ci.appveyor.com/notifications
or in project - https://ci.appveyor.com/project/ApacheSoftwareFoundation/
spark/settings

I'd like to note that I disabled the notification in the appveyor.yml but
it seems the configurations are merged in Web UI,
according to the documentation (https://www.appveyor.com/
docs/notifications/#global-email-notifications).

> Warning: Notifications defined on project settings UI are merged with
notifications defined in appveyor.yml.

Should we maybe an INFRA JIRA to check and ask this?



2017-03-05 8:31 GMT+09:00 Shivaram Venkataraman 
:

> I'm not sure why the AppVeyor updates are coming to the dev list.  Hyukjin
> -- Do you know if we made any recent changes that might have caused this ?
>
> Thanks
> Shivaram
>
> -- Forwarded message --
> From: AppVeyor 
> Date: Sat, Mar 4, 2017 at 2:46 PM
> Subject: Build completed: spark 866-master
> To: dev@spark.apache.org
>
>
> Build spark 866-master completed
> 
>
> Commit ccf54f64d9  by Xiao
> Li  on 3/4/2017 9:50 PM:
> fix.
>
> Configure your notification preferences
> 
> - To
> unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>
>

Fwd: Build completed: spark 866-master

[Shivaram Venkataraman]

I'm not sure why the AppVeyor updates are coming to the dev list.  Hyukjin
-- Do you know if we made any recent changes that might have caused this ?

Thanks
Shivaram

-- Forwarded message --
From: AppVeyor 
Date: Sat, Mar 4, 2017 at 2:46 PM
Subject: Build completed: spark 866-master
To: dev@spark.apache.org


Build spark 866-master completed


Commit ccf54f64d9  by Xiao
Li  on 3/4/2017 9:50 PM:
fix.

Configure your notification preferences

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

Build completed: spark 866-master

[AppVeyor]

Build spark 866-master completed



Commit ccf54f64d9 by Xiao Li on 3/4/2017 9:50 PM:

fix.


Configure your notification preferences


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

Re: [Spark Namespace]: Expanding Spark ML under Different Namespace?

[Nick Pentreath]

Also, note https://issues.apache.org/jira/browse/SPARK-7146 is linked from
SPARK-19498 specifically to discuss opening up sharedParams traits.


On Fri, 3 Mar 2017 at 23:17 Shouheng Yi 
wrote:

> Hi Spark dev list,
>
>
>
> Thank you guys so much for all your inputs. We really appreciated those
> suggestions. After some discussions in the team, we decided to stay under
> apache’s namespace for now, and attach some comments to explain what we did
> and why we did this.
>
>
>
> As the Spark dev list kindly pointed out, this is an existing issue that
> was documented in the JIRA ticket [Spark-19498] [0]. We can follow the JIRA
> ticket to see if there are any new suggested practices that should be
> adopted in the future and make corresponding fixes.
>
>
>
> Best,
>
> Shouheng
>
>
>
> [0] https://issues.apache.org/jira/browse/SPARK-19498
>
>
>
> *From:* Tim Hunter [mailto:timhun...@databricks.com
> ]
> *Sent:* Friday, February 24, 2017 9:08 AM
> *To:* Joseph Bradley 
> *Cc:* Steve Loughran ; Shouheng Yi <
> sho...@microsoft.com.invalid>; Apache Spark Dev ;
> Markus Weimer ; Rogan Carr ;
> Pei Jiang ; Miruna Oprescu 
> *Subject:* Re: [Spark Namespace]: Expanding Spark ML under Different
> Namespace?
>
>
>
> Regarding logging, Graphframes makes a simple wrapper this way:
>
>
>
>
> https://github.com/graphframes/graphframes/blob/master/src/main/scala/org/graphframes/Logging.scala
> 
>
>
>
> Regarding the UDTs, they have been hidden to be reworked for Datasets, the
> reasons being detailed here [1]. Can you describe your use case in more
> details? You may be better off copy/pasting the UDT code outside of Spark,
> depending on your use case.
>
>
>
> [1] https://issues.apache.org/jira/browse/SPARK-14155
> 
>
>
>
> On Thu, Feb 23, 2017 at 3:42 PM, Joseph Bradley 
> wrote:
>
> +1 for Nick's comment about discussing APIs which need to be made public
> in https://issues.apache.org/jira/browse/SPARK-19498
> 
> !
>
>
>
> On Thu, Feb 23, 2017 at 2:36 AM, Steve Loughran 
> wrote:
>
>
>
> On 22 Feb 2017, at 20:51, Shouheng Yi 
> wrote:
>
>
>
> Hi Spark developers,
>
>
>
> Currently my team at Microsoft is extending Spark’s machine learning
> functionalities to include new learners and transformers. We would like
> users to use these within spark pipelines so that they can mix and match
> with existing Spark learners/transformers, and overall have a native spark
> experience. We cannot accomplish this using a non-“org.apache” namespace
> with the current implementation, and we don’t want to release code inside
> the apache namespace because it’s confusing and there could be naming
> rights issues.
>
>
>
> This isn't actually the ASF has a strong stance against, more left to
> projects themselves. After all: the source is licensed by the ASF, and the
> license doesn't say you can't.
>
>
>
> Indeed, there's a bit of org.apache.hive in the Spark codebase where the
> hive team kept stuff package private. Though that's really a sign that
> things could be improved there.
>
>
>
> Where is problematic is that stack traces end up blaming the wrong group;
> nobody likes getting a bug report which doesn't actually exist in your
> codebase., not least because you have to waste time to even work it out.
>
>
>
> You also have to expect absolutely no stability guarantees, so you'd
> better set your nightly build to work against trunk
>
>
>
> Apache Bahir does put some stuff into org.apache.spark.stream, but they've
> sort of inherited that right.when they picked up the code from spark. new
> stuff is going into org.apache.bahir
>
>
>
>
>
> We need to extend several classes from spark which happen to have
> “private[spark].” For example, one of our class extends VectorUDT[0] which
> has private[spark] class