Github user dmarcous commented on the issue:
https://github.com/apache/spark/pull/10945
Got it, thank you @MLnick and thank you @srowen for your inputs along the
way, is has been helpful!
Closing the request.
---
If your project is set up for it, you can reply to this email and h
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/10945
I'd only say it's worth putting in if it's something that users would
cross-validate against (in which case makes more sense to put it into the `ml`
evaluator). But I don't think that's a common case
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/10945
Paging ... @MLnick ? Usually I find people who have changed surrounding
code.
---
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 dmarcous commented on the issue:
https://github.com/apache/spark/pull/10945
Agreed that it should be resolved.
Is there a process where I can reach out for any committer for support?
I'm still in need of this and think those extra couple of lines goes a long
way in
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/10945
I believe we should resolve this as WontFix if there aren't other
committers supporting this change
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
