Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-52092408
Alright, I'll cherry-pick this into branch 1.0 as well.
Spark 1.1 is targeted for being released at the end of this month, and it
won't have Scala 2.11 support.
Github user critikaled commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-51789142
its just annoying, its ok, I have built spark form source and using it as
external lib. btw when would be aprox release date for 1.1 and I was reading
about it in
Github user critikaled commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-51718206
hey this change has not been included in 1.0.2 release. any heads up on the
version in which this will be reflected ?
---
If your project is set up for it, you can
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-51728995
It will be in 1.1. I guess we can also backport it to branch-1.0 -- how bad
is the issue, does it cause some problems or is it just annoying?
---
If your project is set
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1372
---
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 is
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-50182169
I've merged this, thanks. Will fix the style issue later.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-50182271
BTW @fireflyc please create an account on JIRA
(https://issues.apache.org/jira/browse/SPARK) and let me know its name so I can
assign this issue to you.
---
If your
Github user fireflyc commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-50223879
My account is fireflyc, please assign the issue to me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-49217835
There has been further comments regarding this. It would be great if you
address them as well.
---
If your project is set up for it, you can reply to this email and have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-49091169
@fireflyc will you have a chance to address the comments so we can merge
this?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user fireflyc commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-49125597
I modified 'info' into the 'debug' level.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-48804513
LGTM - I could see us maybe moving this to `logDebug` in the future... it
could get pretty chatty if you had an active stream. But seems reasonable to
start with this
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-48826210
Yikes, thats a oversight on my part. The ones related to storing a single
item, should be totally removed, and the other ones related to storing iterator
should be
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/1372#discussion_r14855743
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/receiver/ActorReceiver.scala
---
@@ -68,13 +68,13 @@ object ActorSupervisorStrategy {
*
GitHub user fireflyc opened a pull request:
https://github.com/apache/spark/pull/1372
replace println to log4j
Our program needs to receive a large amount of data and run for a long
time.
We set the log level to WARN but Storing iterator received single
as such message
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-48708875
Can one of the admins verify this 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
Github user fireflyc commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-48739929
I have verified, the log level is set to Info right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-48781760
Jenkins, test this please
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-48782138
QA tests have started for PR 1372. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16574/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1372#issuecomment-48790589
QA results for PR 1372:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds the following public classes
(experimental):brtrait ActorHelper
20 matches
Mail list logo
