Github user oza commented on the issue:
https://github.com/apache/spark/pull/16570
Thanks Sean for your review!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
GitHub user oza opened a pull request:
https://github.com/apache/spark/pull/16570
[SPARK-19207][SQL] LocalSparkSession should use Slf4JLoggerFactory.INSTANCE
## What changes were proposed in this pull request?
Using Slf4JLoggerFactory.INSTANCE instead of creating
Github user oza closed the pull request at:
https://github.com/apache/spark/pull/15806
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15806
This was my mistake of configuration. After clearing the configuration
about Hadoop, it works well. Closing this as not a problem. Thanks all for
helping me, reviewing patch!
---
If your project
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15806
I'm sorry, but I had a hadoop configuration on my local: I noticed it on PR
about SPARK-18345. I will check whether it happens after clearing
configuration.
---
If your project is set up for it, you
Github user oza closed the pull request at:
https://github.com/apache/spark/pull/15841
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15841
I'm sorry, it's completely
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15841
@srowen it makes sense to me. In that case, we can update our documentation
to avoid the problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15841
Thanks a lot for your comments! I see, in fact, I had the problem on Mac
OS. Okay, I will try it on your VM, and on my local linux. Please wait a moment.
---
If your project is set up for it, you can
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/15841#discussion_r87399578
--- Diff:
examples/src/main/scala/org/apache/spark/examples/sql/SparkSQLExample.scala ---
@@ -60,7 +60,8 @@ object SparkSQLExample {
private def
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/15841#discussion_r87397730
--- Diff:
examples/src/main/scala/org/apache/spark/examples/sql/SparkSQLExample.scala ---
@@ -60,7 +60,8 @@ object SparkSQLExample {
private def
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/15841#discussion_r87396970
--- Diff:
examples/src/main/scala/org/apache/spark/examples/sql/SparkSQLExample.scala ---
@@ -60,7 +60,8 @@ object SparkSQLExample {
private def
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15806
Updating patch based on kiszk's comment:
https://github.com/apache/spark/pull/15806#discussion_r87393524
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/15806#discussion_r87394293
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/StreamingQueryManager.scala
---
@@ -209,7 +209,7 @@ class StreamingQueryManager private[sql
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15841
Before the patch:
```
scala> val df = spark.read.json("examples/src/main/resources/people.json")
16/11/10 21:02:59 WARN datasources.DataSource: Error while looking for
metad
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15841
I found that my previous PR has a bug(forgot to add "/" before example).
Resending PR with the fix.
---
If your project is set up for it, you can reply to this email and have your
re
GitHub user oza opened a pull request:
https://github.com/apache/spark/pull/15841
[SPARK-18399][SQL][DOCUMENTATION] Examples in SparkSQL/DataFrame/DataSets
guide fails with default configuration
## What changes were proposed in this pull request?
With default configuration
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15806
@brkyvz @srowen could you check the latest PR? I added prefix "file:///"
before the result of Utils.createTempDir, since Utils.createTempDir only
creates local directory via java.io.File.
-
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15806
@brkyvz thanks for explanation, I will fix the line to work it on local
mode without any breakage.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user oza commented on the issue:
https://github.com/apache/spark/pull/13758
@kiszk it looks that this PR needs rebasing. Could you rebase it on master?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15806
Now I understanding the behaviour. Based on this, I would like to suggest
to add an option to disable checkpoint for the testing or quick start example.
What do you think?
---
If your project is set
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/15806#discussion_r86993123
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/StreamingQueryManager.scala
---
@@ -219,10 +219,11 @@ class StreamingQueryManager private[sql
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/15806#discussion_r86991525
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/StreamingQueryManager.scala
---
@@ -219,10 +219,11 @@ class StreamingQueryManager private[sql
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/15806#discussion_r86987111
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/StreamingQueryManager.scala
---
@@ -219,10 +219,11 @@ class StreamingQueryManager private[sql
Github user oza commented on the issue:
https://github.com/apache/spark/pull/15806
@brkyvz Thanks for taking a look. The problem I faced is: without HDFS
configuration, the [quick
example](https://spark.apache.org/docs/latest/structured-streaming-programming-guide.html#quick-example
GitHub user oza opened a pull request:
https://github.com/apache/spark/pull/15806
[SPARK-18345][STRUCTURED STREAMING] Structured Streaming quick examples
fails with default configuration
## What changes were proposed in this pull request?
This PR fixes failure of a quick
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3757#issuecomment-67895012
Thanks for your review, andrewor14!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
GitHub user oza opened a pull request:
https://github.com/apache/spark/pull/3757
[SPARK-4915] Fix classname to be specified for external shuffle service.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/oza/spark SPARK-4915
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3757#issuecomment-67804178
@andrewor14 could you take a look?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3731#issuecomment-67725428
@andrewor14 good job, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/3731#discussion_r22055469
--- Diff: docs/job-scheduling.md ---
@@ -56,6 +56,112 @@ the same RDDs. For example, the
[Shark](http://shark.cs.berkeley.edu) JDBC serve
queries. In future
Github user oza commented on a diff in the pull request:
https://github.com/apache/spark/pull/3731#discussion_r22081115
--- Diff: docs/job-scheduling.md ---
@@ -56,6 +56,112 @@ the same RDDs. For example, the
[Shark](http://shark.cs.berkeley.edu) JDBC serve
queries. In future
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3689#issuecomment-67195311
Updated a description of dynamic resource allocation based on a comment by
@ash211.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3689#issuecomment-67278755
@andrewor14 OK, feel free to use this PR. Closing this as duplicated one.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user oza closed the pull request at:
https://github.com/apache/spark/pull/3689
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3689#issuecomment-67105316
Thanks for your comment, I'm updating it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user oza opened a pull request:
https://github.com/apache/spark/pull/3689
[SPARK-4839] Adding a documentation about dynamic resource allocation.
Signed-off-by: Tsuyoshi Ozawa ozawa.tsuyo...@gmail.com
You can merge this pull request into a Git repository by running
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3507#issuecomment-64945204
```
org.apache.spark.streaming.CheckpointSuite.recovery with file input stream
```
Confirmed that the test failure looks not related to the patch
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3508#issuecomment-64945372
@SaintBacchus I see, I got it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3512#issuecomment-64977105
Make sense. Closing this ticket. Thanks for your comments, Patrick, Sandy,
and Sean!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user oza closed the pull request at:
https://github.com/apache/spark/pull/3512
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user oza opened a pull request:
https://github.com/apache/spark/pull/3512
[SPARK-4651] Adding -Phadoop-2.5 and -Phadoop-2.6 to compile Spark with
newer versions of Hadoop
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3512#issuecomment-64936933
@srowen Oh, my bad. I'm rebasing the patch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3512#issuecomment-64937113
@srowen Updated. I ran Spark on YARN with Hadoop 2.5.2 by compiling this
option.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user oza commented on the pull request:
https://github.com/apache/spark/pull/3508#issuecomment-64941638
Please note that YARN-2091 changed the error code:
https://issues.apache.org/jira/browse/YARN-2091
---
If your project is set up for it, you can reply to this email
45 matches
Mail list logo
