Github user Myasuka commented on a diff in the pull request:
https://github.com/apache/spark/pull/18452#discussion_r124988257
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/rdd/WriteAheadLogBackedBlockRDD.scala
---
@@ -135,8 +135,11 @@ class
Github user Myasuka commented on a diff in the pull request:
https://github.com/apache/spark/pull/18452#discussion_r124955168
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/rdd/WriteAheadLogBackedBlockRDD.scala
---
@@ -135,8 +135,11 @@ class
GitHub user Myasuka opened a pull request:
https://github.com/apache/spark/pull/18452
Support WAL recover in windows
## What changes were proposed in this pull request?
When driver failed over, it will read WAL from HDFS by calling
Github user Myasuka commented on the issue:
https://github.com/apache/spark/pull/15078
@jodersky Actually, BashOnWindows only exists on Windows10 Anniversary
Update. Moreover, this feature needs to be manually enabled to take effects.
And I don't think this bash environment
GitHub user Myasuka opened a pull request:
https://github.com/apache/spark/pull/15078
[SPARK-17523] Support to generate build info file when building Spark in
Windows
## What changes were proposed in this pull request?
Currently, if we build Spark, it will generate
Github user Myasuka commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-121966507
hi, @avulanov , I have forked your repository about ann-benchmark
https://github.com/avulanov/ann-benchmark/blob/master/spark/spark.scala . I
feel a little confused
Github user Myasuka commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-122158225
@avulanov I try to run test on minist data with SGD optimizer, however, I
cannot reproduce the result in
https://github.com/apache/spark/pull/1290#issuecomment-67262281
Github user Myasuka commented on the pull request:
https://github.com/apache/spark/pull/3222#issuecomment-63170337
Why there are no any annotation or readme in your code?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
