Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15671
@jkbradley Updated
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
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/15671
**[Test build #68101 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68101/consoleFull)**
for PR 15671 at commit
[`880ae3f`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68101/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #68101 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68101/consoleFull)**
for PR 15671 at commit
[`880ae3f`](https://github.com/apache/spark/commit/8
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15671
@jkbradley Thanks for bringing that up. I'm ok with alternate solutions
provided they don't require someone to remember to manually add or manually
except a new param, and that we can ensure that we
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/15671
I don't want to truncate Param strings because it would create invalid JSON
in case people want to try to catch and parse the logs. I like the idea of
allowing exceptions and possibly adding unit
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15671
I created [SPARK-18253](https://issues.apache.org/jira/browse/SPARK-18253)
to track it. We may have to get to it after 2.1 QA period.
---
If your project is set up for it, you can reply to this emai
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68039/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
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/15671
**[Test build #68039 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68039/consoleFull)**
for PR 15671 at commit
[`e77bdc4`](https://github.com/apache/spark/commit/
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15671
@sethah I agree that manually listing traceable params is prone to mistake.
I think we can log all params expect some params which are labeled `dont-log`
in the individual algorithms. Or we can
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #68039 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68039/consoleFull)**
for PR 15671 at commit
[`e77bdc4`](https://github.com/apache/spark/commit/e
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15671
@sethah I have make changes according to the comments. Thanks for your
reviewing.
---
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 sethah commented on the issue:
https://github.com/apache/spark/pull/15671
IMO, the way we're doing this logging right now is unsustainable. It
requires too much manual work. We can leave this discussion for a different
JIRA, but what we could do is modify the `Instrumentat
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67947/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15671
**[Test build #67947 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67947/consoleFull)**
for PR 15671 at commit
[`6d2d13f`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15671
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/15671
**[Test build #67947 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67947/consoleFull)**
for PR 15671 at commit
[`6d2d13f`](https://github.com/apache/spark/commit/6
19 matches
Mail list logo
