The revert looks fine to me for keeping the compatibility.
Also, I think the different orders between the systems easily lead to
mistakes, so
, as Wenchen suggested, it looks nice to make these (two parameters) trim
functions
unrecommended in future releases:
https://github.com/apache/spark/pull/27
Hi,
Never mind. Found this [1]:
> This config is deprecated and it will be removed in 3.0.0.
And so it has :) Thanks and sorry for the trouble.
[1]
https://github.com/apache/spark/blob/830a4ec59b86253f18eb7dfd6ed0bbe0d7920e5b/sql/catalyst/src/main/scala/org/apache/spark/sql/internal/SQLConf.sca
Thanks for checking it, Jacek.
2020년 2월 16일 (일) 오후 7:23, Jacek Laskowski 님이 작성:
> Hi,
>
> Never mind. Found this [1]:
>
> > This config is deprecated and it will be removed in 3.0.0.
>
> And so it has :) Thanks and sorry for the trouble.
>
> [1]
> https://github.com/apache/spark/blob/830a4ec59b86
Hi Team,
I am using Spark in our projects. Now, I would like to contribute to spark
development. Kindly help me to get the newbie issues which I can start
contributing and get familiar with Apache Spark contribution process.
Regards,
Prakash Gopalsamy.
