Re: test failed due to OOME

Looks like SparkListenerSuite doesn't OOM on QA runs compared to Jenkins builds. I wonder if this is due to difference between machines running QA tests vs machines running Jenkins builds. On Fri, Oct 30, 2015 at 1:19 PM, Ted Yu wrote: > I noticed that the SparkContext

Re: Ability to offer initial coefficients in ml.LogisticRegression

Hi Tsai, Is it proper if I create a jira and try to work on it? 2015-10-23 10:40 GMT+08:00 YiZhi Liu : > Thank you Tsai. > > Holden, would you mind posting the JIRA issue id here? I searched but > found nothing. Thanks. > > 2015-10-23 1:36 GMT+08:00 DB Tsai

Re: Downloading Hadoop from s3://spark-related-packages/

I am getting the same results using closer.lua versus close.cgi, which seems to be downloading a page where the user can choose the closest mirror. I tried to add parameters to follow redirect without much success. There seems to be already a jira for a similar request with infra:

[BUILD SYSTEM] quick jenkins downtime, november 5th 7am

i'd like to take jenkins down briefly thursday morning to install some plugin updates. this will hopefully be short (~1hr), but could easily become longer as the jenkins plugin ecosystem is fragile and updates like this are known to cause things to explode. the only reason why i'm contemplating

Re: test failed due to OOME

I believe this is some bug in our tests. For some reason we are using way more memory than necessary. We'll probably need to log into Jenkins and heap dump some running tests and figure out what is going on. On Mon, Nov 2, 2015 at 7:42 AM, Ted Yu wrote: > Looks like

Re: Getting Started

https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark *Romi Kuntsman*, *Big Data Engineer* http://www.totango.com On Fri, Oct 30, 2015 at 1:25 PM, Saurabh Shah wrote: > Hello, my name is Saurabh Shah and I am a second year undergraduate > student at

Re: Lead operator not working as aggregation operator

I was referring to this jira issue : https://issues.apache.org/jira/browse/TAJO-919 On Mon, Nov 2, 2015 at 4:03 PM, Shagun Sodhani wrote: > Hi! I was trying out window functions in SparkSql (using hive context) > and I noticed that while this >

Re: Lead operator not working as aggregation operator

Hi, This is more a question for the User list. Lead and Lag imply ordering of the whole dataset, and this is not supported. You can use Lead/Lag in an ordered window function and you'll be fine: *select lead(max(expenses)) over (order by customerId) from tbl group by customerId* HTH Met

Lead operator not working as aggregation operator

Hi! I was trying out window functions in SparkSql (using hive context) and I noticed that while this mentions that *lead* is implemented as an aggregate operator, it seems not to be the case. I am using the

Re: Lead operator not working as aggregation operator

I get the part about using it with window, but most other window operators also work as aggregator operator and in this case, it is specifically mentioned in the jira issue as well. I asked on dev list and not user list as it was already mentioned in the issue. On Mon, Nov 2, 2015 at 4:15 PM,