Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
okay! I'll make a JIRA later and thanks!
---
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
ena
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16030
This was the behavior change your PR proposed before, I think it makes
sense, you can send a PR to fix it in Spark 2.2
---
If your project is set up for it, you can reply to this email and have y
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
Thanks! I found another wired behaviour related to this issue. Is this
expected? or, should we fix?
```
scala> import org.apache.spark.sql.types._
scala> val schema = new StructType(
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16030
thanks, merging to master/2.1!
---
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 an
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
oh, I wrongly wrote in an opposite way..., okay, fixed cc: @cloud-fan
---
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
