wypoon commented on a change in pull request #4255:
URL: https://github.com/apache/iceberg/pull/4255#discussion_r828335443



##########
File path: docs/spark/spark-queries.md
##########
@@ -168,7 +168,9 @@ To inspect a table's history, snapshots, and other 
metadata, Iceberg supports me
 Metadata tables are identified by adding the metadata table name after the 
original table name. For example, history for `db.table` is read using 
`db.table.history`.
 
 {{< hint info >}}
-As of Spark 3.0, the format of the table name for inspection 
(`catalog.database.table.metadata`) doesn't work with Spark's default catalog 
(`spark_catalog`). If you've replaced the default catalog, you may want to use 
`DataFrameReader` API to inspect the table. 
+For Spark 2.4, use the `DataFrameReader` API to [inspect 
tables](#inspecting-with-dataframes).
+
+For Spark 3, prior to 3.2, the Spark session catalog (`spark_catalog`) does 
not support table names with multipart identifiers such as 
`catalog.database.table.metadata`. To work around this, for querying metadata 
tables, configure a different catalog that uses the Iceberg `SparkCatalog` 
class, or use the Spark `DataFrameReader` API. From Spark 3.2 onwards, the 
session catalog supports table names with multipart identifiers.

Review comment:
       @szehon-ho thanks for the review.
   I think that to be correct, one should say "configure a catalog that uses 
`org.apache.iceberg.spark.SparkCatalog`". The catalog is `prod` or 
`iceberg_catalog` or whatever one names it. Otherwise, I have adopted your 
suggestion.
   
   Note: If you don't feel that the link for "session catalog" (in my update) 
is necessary, I'm fine with removing it.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to