Github user rajeshbalamohan commented on the pull request:
https://github.com/apache/spark/pull/10861#issuecomment-175584028
@JoshRosen - Please let me know if my latest comment on the usecase
addresses your question. Can you.
>>
may be worth a holistic design review because I think there are some hacks
in Spark SQL to address this problem there and it would be nice to have a
unified solution for this
>>
Can you plz provide more details/pointers on 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 feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
