Github user rxin commented on the issue:
https://github.com/apache/spark/pull/22889
Yea good idea (prefer Array over Seq for short lists)
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22889
I think the problem is real, maybe we should not use `Seq` in the end-user
API, but always use Array to be more Java-friendly. This can also avoid bugs
like
Github user arman1371 commented on the issue:
https://github.com/apache/spark/pull/22889
@dongjoon-hyun . yes
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail:
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/22889
Thank you for the advice, @gatorsmile and @cloud-fan .
@arman1371 . It's a trade-off issue and the benefit looks smaller than the
benefit. If you don't mind, could you close this PR?
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22889
So we introduce a new API just to save typing `Seq(...)`? Maintaining an
API has cost.
---
-
To unsubscribe, e-mail:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22889
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22889
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22889
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
