dataageek commented on issue #4798:
URL: https://github.com/apache/gravitino/issues/4798#issuecomment-2564703982

   hi @FANNG1 
   This is my use case: After creating lakehouse-iceberg catalogs (jdbc) in 
Gravitino Metalake, I was able to pull the catalogs into Spark (v 3.5.4) and 
query the Iceberg tables. However, when I tried to query the Iceberg metadata 
tables, I encountered the following error: 
   
   ./spark-sql -v \
        --conf 
spark.plugins="org.apache.gravitino.spark.connector.plugin.GravitinoSparkPlugin"
 \
        --conf spark.sql.gravitino.uri=http://127.0.0.1:8090 \
        --conf spark.sql.gravitino.metalake=datalake_dev \
        --conf spark.sql.gravitino.enableIcebergSupport=true
   ```
   spark-sql (default)> set;
   spark.master    local[*]
   spark.plugins   
org.apache.gravitino.spark.connector.plugin.GravitinoSparkPlugin
   spark.sql.catalog.iceberg_jdbc_catalog  
org.apache.gravitino.spark.connector.iceberg.GravitinoIcebergCatalogSpark35
   spark.sql.catalog.managed_iceberg_jdbc_catalog  
org.apache.gravitino.spark.connector.iceberg.GravitinoIcebergCatalogSpark35
   spark.sql.catalog.managed_iceberg_jdbc_catalog_2        
org.apache.gravitino.spark.connector.iceberg.GravitinoIcebergCatalogSpark35
   spark.sql.catalog.managed_iceberg_jdbc_catalog_3        
org.apache.gravitino.spark.connector.iceberg.GravitinoIcebergCatalogSpark35
   spark.sql.catalogImplementation hive
   spark.sql.datetime.java8API.enabled     true
   spark.sql.extensions    
org.apache.gravitino.spark.connector.iceberg.extensions.GravitinoIcebergSparkSessionExtensions,org.apache.iceberg.spark.extensions.IcebergSparkSessionExtensions
   spark.sql.gravitino.enableIcebergSupport        true
   spark.sql.gravitino.metalake    datalake_dev
   spark.sql.gravitino.uri http://127.0.0.1:8090
   spark.sql.hive.version  2.3.9
   
   spark-sql (default)> select * from 
managed_iceberg_jdbc_catalog_3.managed_db1.managed_table1;
   a
   b
   c
   Time taken: 13.246 seconds, Fetched 3 row(s)
   spark-sql (default)> select * from 
managed_iceberg_jdbc_catalog_3.managed_db1.managed_table1.snapshots;
   select * from 
managed_iceberg_jdbc_catalog_3.managed_db1.managed_table1.snapshots
   [TABLE_OR_VIEW_NOT_FOUND] The table or view 
`managed_iceberg_jdbc_catalog_3`.`managed_db1`.`managed_table1`.`snapshots` 
cannot be found. Verify the spelling and correctness of the schema and catalog.
   If you did not qualify the name with a schema, verify the current_schema() 
output, or qualify the name with the correct schema and catalog.
   To tolerate the error on drop use DROP VIEW IF EXISTS or DROP TABLE IF 
EXISTS.; line 1 pos 14;
   'Project [*]
   +- 'UnresolvedRelation [managed_iceberg_jdbc_catalog_3, managed_db1, 
managed_table1, snapshots], [], false
   
   ```
   Viewing the details of Iceberg metadata tables is crucial. It would be great 
if this could be prioritized.


-- 
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]

Reply via email to