Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18658
**[Test build #79683 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79683/testReport)**
for PR 18658 at commit
[`52b20f3`](https://github.com/apache/spark/commit/52
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/18658
FYI for future reviewers as well, we've been running an [extremely similar
patch](https://github.com/palantir/spark/pull/181) to PJ's on our distribution
of Spark for the past several months and had
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18658
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79677/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18658
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/18658
**[Test build #79677 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79677/testReport)**
for PR 18658 at commit
[`803166c`](https://github.com/apache/spark/commit/8
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/18658
That seems reasonable. I'm kind of pro-truncation for very very large
code. Even though its not great to have something truncated, outputting GBs of
logs is also pretty bad for downstream consume
Github user pjfanning commented on the issue:
https://github.com/apache/spark/pull/18658
@marmbrus How about something like?:
`
val msg = s"failed to compile: $e"
logError(msg, e)
logInfo(formatted)
throw new JaninoRuntimeException(msg
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/18658
I don't have super strong opinions here, but in my experience its not
always easy to get users to rerun a failed query with a different logging
level. Have we considered truncating or special casi
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18658
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