Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/17893
Pending. I am formatting the pull name~
---
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
GitHub user lshmouse opened a pull request:
https://github.com/apache/spark/pull/17893
FileFormatWriter wrap the FetchFailedException which breaks job's failover
## What changes were proposed in this pull request?
Handle the fetch failed exception separately in FileFormatW
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/16602
@srowen
After checking the implements of timsort, it has been optimized for sorted
array.
Just ignore this PR. Thanks for your time.
---
If your project is set up for it, you can reply
Github user lshmouse closed the pull request at:
https://github.com/apache/spark/pull/16602
---
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 feature is
GitHub user lshmouse opened a pull request:
https://github.com/apache/spark/pull/16602
SPARK-19238: Ignore sorting the edges if edges are sorted when building
edge partition
## What changes were proposed in this pull request?
Ignore sorting the edges if edges are sorted
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/13706
@lianhuiwang
I think the problem is that no need to check if macroFunction is resolved.
Data type may be cast dynamically according the sql data type.
---
If your project is set up for
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/13706
@lianhuiwang
Just a feedback. With this patch, creating a MACRO throws the following
exception.
Any suggestion? I am trying to debug it.
```
16/11/30 16:59:18 INFO
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/14561
@jerryshao
The patch doesn't just change the code structure. It distinguish the
responsibility of these two classes.
What's more, it's the first step to refactor the schedul
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/14561
@zsxwing @srowen
Could you please help to review this patch? Thanks~
---
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
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/14561
@srowen Please help to trigger the Jenkins test, Thanks~
---
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
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/14561
Jenkins test this please
---
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
Github user lshmouse commented on the issue:
https://github.com/apache/spark/pull/14561
Jenkins test this please
---
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
GitHub user lshmouse opened a pull request:
https://github.com/apache/spark/pull/14561
SPARK-16972: Move DriverEndpoint out of CoarseGrainedSchedulerBackend
## What changes were proposed in this pull request?
Move DriverEndpoint out of CoarseGrainedSchedulerBackend and make the
13 matches
Mail list logo