Re: Return binary mode in ThriftServer

Thanks for the email. Things like this (and bugs) are exactly the reason the preview releases exist. It seems like enough people have run into problem with this one that maybe we should just bring it back for backward compatibility. On Monday, June 13, 2016, Egor Pahomov

Return binary mode in ThriftServer

In May due to the SPARK-15095 binary mode was "removed" (code is there, but you can not turn it on) from Spark-2.0. In 1.6.1 binary was default and in 2.0.0-preview it was removed. It's really annoying: - I can not use Tableau+Spark anymore - I need to change connection URL in SQL client

Utilizing YARN AM RPC port field

Hi all, YARN provides a way for AppilcationMaster to register a RPC port so that a client outside the YARN cluster can reach the application for any RPCs, but Spark’s YARN AMs simply register a dummy port number of 0. (See

Re: tpcds q1 - java.lang.NegativeArraySizeException

I'm unfortunately not able to reproduce this on master. Does the query always fail deterministically? On Mon, Jun 13, 2016 at 12:54 PM, Ovidiu-Cristian MARCU < ovidiu-cristian.ma...@inria.fr> wrote: > Yes, commit ad102af > > On 13 Jun 2016, at 21:25, Reynold Xin wrote: > >

Re: tpcds q1 - java.lang.NegativeArraySizeException

Yes, commit ad102af > On 13 Jun 2016, at 21:25, Reynold Xin wrote: > > Did you try this on master? > > > On Mon, Jun 13, 2016 at 11:26 AM, Ovidiu-Cristian MARCU > > > wrote: > Hi, > > Running the

Re: tpcds q1 - java.lang.NegativeArraySizeException

Did you try this on master? On Mon, Jun 13, 2016 at 11:26 AM, Ovidiu-Cristian MARCU < ovidiu-cristian.ma...@inria.fr> wrote: > Hi, > > Running the first query of tpcds on a standalone setup (4 nodes, tpcds2 > generated for scale 10 and transformed in parquet under hdfs) it results > in one

Re: [YARN] Small fix for yarn.Client to use buildPath (not Path.SEPARATOR)

Yeah it does the same thing anyway. It's fine to consistently use the method. I think there's an instance in ClientSuite that can use it. On Mon, Jun 13, 2016 at 6:50 PM, Jacek Laskowski wrote: > Hi, > > Just noticed that yarn.Client#populateClasspath uses Path.SEPARATOR > [1]

tpcds q1 - java.lang.NegativeArraySizeException

Hi, Running the first query of tpcds on a standalone setup (4 nodes, tpcds2 generated for scale 10 and transformed in parquet under hdfs) it results in one exception [1]. Close to this problem I found this issue https://issues.apache.org/jira/browse/SPARK-12089

[YARN] Small fix for yarn.Client to use buildPath (not Path.SEPARATOR)

Hi, Just noticed that yarn.Client#populateClasspath uses Path.SEPARATOR [1] to build a CLASSPATH entry while another similar-looking line uses buildPath method [2]. Could a pull request with a change to use buildPath at [1] be accepted? I'm always confused how to fix such small changes. [1]