Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6545#issuecomment-114570582
sorry for the delay, I'm just looking at this again. @steveloughran I want
to make sure I understand what you are proposing -- that fix would be totally
independent of the ATS work for SPARK-1537, right? I see the relationship, but
think they are best tackled in separate PRs (i think that is what you are
describing, just want to double check).
Just thinking aloud here -- my only concern with adding an expiry time is
that you never know what to set it to, and it might be a little confusing to
users. I was thinking we could add another query param `?refresh=true` to
avoid the performance hit all the time, but I suppose that will just lead to
users always setting that param, so it probably doesn't help. So the cache
expiry time seems like the way to go.
@XuTingjun how about you help take a look at what @steveloughran comes up
with and see if it addresses your concerns?
---
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]
