Github user janplus commented on the issue:
https://github.com/apache/spark/pull/18376
Hi @srowen, @jiangxb1987. Thanks for quick response.
After further debug and consideration, this fix should be done in the
`spark-solr` project. Since this is a Solr specific issue.
I'll clos
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18376
IMO a port should always be a number, we should not accept the invalid port
format.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18376
This isn't a valid fix IMHO and I would close this
---
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 f
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18376
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