Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18488
**[Test build #79105 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79105/testReport)**
for PR 18488 at commit
[`637daa4`](https://github.com/apache/spark/commit/63
Github user mike0sv commented on the issue:
https://github.com/apache/spark/pull/18488
I reworked the code to ser/de enums into ints (according to declaring
order). However, I recreate mapping for each object, which is very bad
obviously. I need to create mapping once (for each partit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18488
**[Test build #79104 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79104/testReport)**
for PR 18488 at commit
[`2cb0834`](https://github.com/apache/spark/commit/2
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18488
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79104/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18488
Merged build finished. Test FAILed.
---
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/18488
**[Test build #79104 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79104/testReport)**
for PR 18488 at commit
[`2cb0834`](https://github.com/apache/spark/commit/2c
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18488
Hm, backing up, this shouldn't actually work, should it? enums aren't
beans, and this newer error that gets uncovered more directly demonstrates that.
Do you need to define an encoder to use
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18488
Merged build finished. Test FAILed.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18488
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79070/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18488
**[Test build #79070 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79070/testReport)**
for PR 18488 at commit
[`120bb32`](https://github.com/apache/spark/commit/1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18488
**[Test build #79070 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79070/testReport)**
for PR 18488 at commit
[`120bb32`](https://github.com/apache/spark/commit/12
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18488
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18488
The reproducer in the JIRA used `show()` with rows and it was fine but it
looks a problem with type specific operations of dataset.
---
If your project is set up for it, you can reply to this e
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18488
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 f
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18488
@mike0sv looks good, thanks. It would help us for ease of understanding in
the future.
---
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 mike0sv commented on the issue:
https://github.com/apache/spark/pull/18488
@kiszk check it out
---
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,
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18488
This fix looks good. Would it be possible to put details on why this
problem happens and how it is fixed in the description of this PR, as written
in JIRA entry?
---
If your project is set up for it
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18488
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
18 matches
Mail list logo
