Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/13530
@chenghao-intel can you file a jira with the details on what you are doing
and link to the original jira?
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user chenghao-intel commented on the issue:
https://github.com/apache/spark/pull/13530
`spark-version-info.properties` cannot be found in my develop machine, and
will cause NPE while debugging with IDE, should we add the default version info
back for developers like me?
---
I
Github user dhruve commented on the issue:
https://github.com/apache/spark/pull/13530
@vanzin. Thanks for reviewing & merging the PR. Have closed 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 no
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13530
@dhruve could you close the PR? The bot doesn't do it automatically for
backports. thx
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/13530
Merging to 2.0.
---
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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13530
sounds good go ahead
---
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
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/13530
Personally I would like to see this go into branch-2.0 also. it doesn't
seem very risky but has benefits to both dev and end users. @rxin do you have
strong objections?
---
If your project is s
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13530
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60073/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13530
Merged build finished. Test PASSed.
---
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13530
**[Test build #60073 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60073/consoleFull)**
for PR 13530 at commit
[`9c14834`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13530
**[Test build #60073 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60073/consoleFull)**
for PR 13530 at commit
[`9c14834`](https://github.com/apache/spark/commit/9
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13530
ok to test
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13530
Dhruve points out above an instance where a previous release wasn't
properly changed and now Spark is printing the wrong version in branch-2.0; so
I think this change does help.
---
If your project
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13530
hm maybe no need to do this for branch-2.0, since it's pretty easy to do
this manually once or twice for 2.0.x.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13530
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 project does not have this feat
15 matches
Mail list logo