see email below. reynold suggested i send it to dev instead of user
-- Forwarded message --
From: Koert Kuipers ko...@tresata.com
Date: Mon, Mar 23, 2015 at 4:36 PM
Subject: hadoop input/output format advanced control
To: u...@spark.apache.org u...@spark.apache.org
currently its
we are running this right now as root user and the folder /tmp/spark-events
was manually created and the Job has access to this folder
On Mon, Mar 23, 2015 at 3:38 PM, Denny Lee denny.g@gmail.com wrote:
It appears that you are running the thrift-server using the spark-events
account but
Yeah the fully realized #4, which gets back the ability to use it in
switch statements (? in Scala but not Java?) does end up being kind of
huge.
I confess I'm swayed a bit back to Java enums, seeing what it
involves. The hashCode() issue can be 'solved' with the hash of the
String
When you say the job has access, do you mean that when you run spark-submit
or spark-shell (for example), it is able to write to the /tmp/spark-events
folder?
On Mon, Mar 23, 2015 at 1:02 PM Neil Dev neilk...@gmail.com wrote:
we are running this right now as root user and the folder
When I start spark-shell (for example) it does not write to the
/tmp/spark-events folder. It remains empty. I have even tried it after
giving that folder rwx permission for user, group and others.
Neil's colleague,
Anu
On Mon, Mar 23, 2015 at 4:50 PM, Denny Lee denny.g@gmail.com wrote:
If scaladoc can show the Java enum types, I do think the best way is then
just Java enum types.
On Mon, Mar 23, 2015 at 2:11 PM, Patrick Wendell pwend...@gmail.com wrote:
If the official solution from the Scala community is to use Java
enums, then it seems strange they aren't generated in
It looks this is not the right place for this question, I have send the
question to user group.
thank you,
bijay
On Mon, Mar 23, 2015 at 2:25 PM, Bijay Pathak bijay.pat...@cloudwick.com
wrote:
Hello,
I am running TeraSort https://github.com/ehiggs/spark-terasort on
100GB of data. The final
well, perhaps I overstated things a little, I wouldn't call it the
official solution, just a recommendation in the never-ending debate (and
the recommendation from folks with their hands on scala itself).
Even if we do get this fixed in scaladoc eventually -- as its not in the
current versions,
The only issue I knew of with Java enums was that it does not appear in the
Scala documentation.
On Mon, Mar 23, 2015 at 1:46 PM, Sean Owen so...@cloudera.com wrote:
Yeah the fully realized #4, which gets back the ability to use it in
switch statements (? in Scala but not Java?) does end up
If the official solution from the Scala community is to use Java
enums, then it seems strange they aren't generated in scaldoc? Maybe
we can just fix that w/ Typesafe's help and then we can use them.
On Mon, Mar 23, 2015 at 1:46 PM, Sean Owen so...@cloudera.com wrote:
Yeah the fully realized #4,
Thanks Reynold,
Agree with you to open another JIRA to unify the block storage API. I have
upload the design doc to SPARK-6479 as well.
Thanks.
Zhan Zhang
On Mar 23, 2015, at 4:03 PM, Reynold Xin
r...@databricks.commailto:r...@databricks.com wrote:
I created a ticket to separate the API
I created a ticket to separate the API refactoring from the implementation.
Would be great to have these as two separate patches to make it easier to
review (similar to the way we are doing RPC refactoring -- first
introducing an internal RPC api, port akka to it, and then add an
alternative
12 matches
Mail list logo
