Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18622
Thanks! Might you please resolve the JIRA as "Won't Fix" then?
Yes, of course I am interested, thanks @holdenk, if I can help and
contribute I am very happy!
---
If your project is set up for
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18622
That would be good yes. Let me know if you're interested take a look at the
PySpark ML API since we're actively working on improving that and would be
great to have more interested folks there as
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18622
Thank @holdenk, should I close this PR then?
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/18622
Oh wait sorry I misread that code, it looks like we have this already
wrapped behind in the Spark ML API.
Since we aren't actively working on the Spark MLlib APIs right now I
probably
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18622
So while we are trying to limit the changes in mllib, we are currently
exposing BinaryClassificationMetrics in the ML models so this makes sense to
expose.
---
If your project is set up for it,
Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/18622
@srowen any comment on this PR?
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18622
**[Test build #3879 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3879/testReport)**
for PR 18622 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18622
**[Test build #3879 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3879/testReport)**
for PR 18622 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18622
@jakecharland that's just an automated message asking if it's OK to test.
I'll kick it off
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user jakecharland commented on the issue:
https://github.com/apache/spark/pull/18622
+1 on getting this verified.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18622
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
11 matches
Mail list logo