Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16021
@dongjoon-hyun Thanks for letting me know! I'm not familiar with a backport
policy in spark though, if we can, I think it'd be better to do because it
seems there are still some of users use spark 1.6.x. By the way, do we need to
remove the added spaces of PostgreSQL `CHAR` in `JdbcDialect` or something when
loading these data into Spark? ISTM that this PostgreSQL-specific behaivor
makes users confused when processing the loaded data in Spark.
---
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 and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
