[
https://issues.apache.org/jira/browse/SPARK-29099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932922#comment-16932922
]
Hyukjin Kwon commented on SPARK-29099:
--------------------------------------
Seems like we use "UNKNOWN" in that case:
1.
https://github.com/apache/spark/commit/d4a277f0ce2d6e1832d87cae8faec38c5bc730f4
2.
https://github.com/apache/spark/commit/4559a82a1de289093064490ef2d39c3c535fb3d4
> org.apache.spark.sql.catalyst.catalog.CatalogTable.lastAccessTime is not set
> ----------------------------------------------------------------------------
>
> Key: SPARK-29099
> URL: https://issues.apache.org/jira/browse/SPARK-29099
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.4.4
> Reporter: Shixiong Zhu
> Priority: Major
>
> I noticed that
> "org.apache.spark.sql.catalyst.catalog.CatalogTable.lastAccessTime" is always
> 0 in my environment. Looks like Spark never updates this field in metastore
> when reading a table. This is fine considering the cost to update it when
> reading a table is high.
> However, "Last Access" in "describe extended" always shows "Thu Jan 01
> 00:00:00 UTC 1970" and this is confusing. Can we show something alternative
> to indicate it's not set?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
