Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18606
OK, but, I'm also about to remove 2.10 support anyway and change this
message in `master`. It'll never be published; 2.2.0 was already released. I
don't think it was worth changing and just makes a
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18606
@rxin
Thx!
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/18606
It's already merged.
https://github.com/apache/spark/commit/24367f23f77349a864da340573e39ab2168c5403
---
If your project is set up for it, you can reply to this email and have your
reply
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18606
@rxin
Hello,did you help me merge this PR?Why I found my PR only be closed but
isn't merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/18606
That's true. Merging in master.
---
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 liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18606
@srowen
But now,spark 2.2.0 released.we know exactly that Scala 2.10 isn't removed
in Spark 2.2.0,so we shouldn't give the user an inaccurate message.
---
If your project is set up for
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18606
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18606
No, the statement was correct. It said may be removed.
---
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