https://github.com/apache/spark/blob/master/docs/quick-start.md in line
127. one spelling mistake found please correct it. (proogram to program)
On Fri, Mar 28, 2014 at 9:58 PM, Will Benton wi...@redhat.com wrote:
RC3 works with the applications I'm working on now and MLLib performance
is
Hi, all
The recovery with file input stream” in the Streaming.CheckpointSuite
sometimes failed even you are working on a totally irrelevant part, I met this
problem for 3+ times.
I assume this test case is likely to fail when the testing servers are very
busy?
Two cases from others:
Sean:
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954345#comment-13954345
]
ASF GitHub Bot commented on SPARK-732:
--
Github user AmplabJenkins commented on the
Guys I fixed this by adding j...@apache.org to the mailing list, no
more moderation required.
Cheers,
Chris
-Original Message-
From: ASF GitHub Bot (JIRA) j...@apache.org
Reply-To: dev@spark.apache.org dev@spark.apache.org
Date: Saturday, March 29, 2014 10:14 AM
To:
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954353#comment-13954353
]
ASF GitHub Bot commented on SPARK-732:
--
Github user AmplabJenkins commented on the
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954354#comment-13954354
]
ASF GitHub Bot commented on SPARK-732:
--
Github user AmplabJenkins commented on the
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954363#comment-13954363
]
ASF GitHub Bot commented on SPARK-732:
--
Github user mridulm commented on a diff in the
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954368#comment-13954368
]
ASF GitHub Bot commented on SPARK-732:
--
Github user mridulm commented on the pull
Hi,
So we are now receiving updates from three sources for each change to the PR.
While each of them handles a corner case which others might miss,
would be great if we could minimize the volume of duplicated
communication.
Regards,
Mridul
Mridul,
You can unsubscribe yourself from any of these sources, right?
- Patrick
On Sat, Mar 29, 2014 at 11:05 AM, Mridul Muralidharan mri...@gmail.comwrote:
Hi,
So we are now receiving updates from three sources for each change to
the PR.
While each of them handles a corner case which
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954379#comment-13954379
]
ASF GitHub Bot commented on SPARK-732:
--
Github user AmplabJenkins commented on the
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954384#comment-13954384
]
ASF GitHub Bot commented on SPARK-732:
--
Github user kayousterhout commented on the
Hey Chris,
I don't think our JIRA has been fully migrated to Apache infra, so it's
really confusing to send people e-mails referring to the new JIRA since we
haven't announced it yet. There is some content there because we've been
trying to do the migration, but I'm not sure it's entirely
With the speed of comments updates in Jira by Spark dev community +1 for
issues@ list
- Henry
On Saturday, March 29, 2014, Patrick Wendell pwend...@gmail.com wrote:
Ah sorry I see - Jira updates are going to the dev list. Maybe that's not
desirable. I think we should send them to the issues@
Okay I think I managed to revert this by just removing jira@a.o from our
dev list.
On Sat, Mar 29, 2014 at 11:37 AM, Patrick Wendell pwend...@gmail.comwrote:
Hey Chris,
I don't think our JIRA has been fully migrated to Apache infra, so it's
really confusing to send people e-mails referring
[
https://issues.apache.org/jira/browse/SPARK-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954423#comment-13954423
]
ASF GitHub Bot commented on SPARK-732:
--
Github user CodingCat commented on the pull
If the PR comments are going to be replicated into the jira's and they
are going to be set to dev@, then we could keep that and remove
[Github] updates ?
The last was added since discussions were happening off apache lists -
which should be handled by the jira updates ?
I dont mind the mails if
I'm working with infra to get the following set-up:
1. Don't post github updates to jira comments (they are too low level). If
users want these they can subscribe to commits@s.a.o.
2. Jira comment stream will go to issues@s.a.o so people can opt into that.
One thing YARN has set-up that might be
No worries, thanks Patrick, agreed.
-Original Message-
From: Patrick Wendell pwend...@gmail.com
Date: Saturday, March 29, 2014 1:47 PM
To: Chris Mattmann chris.a.mattm...@jpl.nasa.gov
Cc: Chris Mattmann mattm...@apache.org, dev@spark.apache.org
dev@spark.apache.org
Subject: Re: Could you
Hi,
Is the migration from Jenkins to Travis finished?
I think Travis is actually not stable based on the observations in these days
(and Jenkins becomes unstable too…… :-( ), I’m actively working on two PRs
related to DAGScheduler, I saw
Problem on Travis:
1. test “large number of
Is the migration from Jenkins to Travis finished?
It is not finished and really at this point it is only something we are
considering, not something that will happen for sure. We turned it on in
addition to Jenkins so that we could start finding issues exactly like the
ones you described
That’s great!
Andy, thank you for all your contributions to the community !
Best,
--
Nan Zhu
On Saturday, March 29, 2014 at 11:40 PM, Patrick Wendell wrote:
Hey All,
We've successfully migrated the Spark JIRA to the Apache infrastructure.
This turned out to be a huge effort, lead
Ah yes that should be and will be updated!
One more update in docs.
In the home page of spark streaming
http://spark.incubator.apache.org/streaming/.
Under
Deployment Options
It is mentioned that *Spark Streaming can read data from HDFS
23 matches
Mail list logo