talatuyarer commented on issue #13990:
URL: https://github.com/apache/iceberg/issues/13990#issuecomment-3259469771

   Hi @ramesh-aqfer 
   
   Great question! It can be a bit confusing since there are two parallel paths 
for this.
   
   You're spot on about the limitations of the Big Lake Metastore RESTCatalog 
right now. Since it's still in Preview, tables managed through it are treated 
as external, read-only tables by BigQuery, and they don't show up automatically 
in the UI. However you can query them. You can find [more details 
here](https://cloud.google.com/bigquery/docs/blms-rest-catalog#query_a_table).
   
   The BigQueryMetastoreCatalog is the GA (General Availability) solution 
designed to solve these exact problems. It's meant for BigQuery-managed Iceberg 
tables.
   
   Here’s the breakdown:
   
   **BigQueryMetastoreCatalog (GA)**: This is your best bet for now, if you are 
going to use Managed Iceberg Tables. The workflow is to create and manage your 
Iceberg tables directly within BigQuery using standard SQL DDL. These tables 
are fully read/write, show up in the UI, and get all the native BigQuery 
features like fine-grained access control. You then use the 
BigQueryMetastoreCatalog from open-source engines like Spark or Flink to read 
these BigQuery-managed tables.
   
   **BigLake RESTCatalog (Preview)**: This is the newer path and aligns with 
the open-source Iceberg REST API standard. It's the recommended direction for 
the future, and it will eventually have deep integration with BigQuery. For 
now, it's best for use cases where you're managing tables outside BQ and just 
want to query them from there.
   
   For specific roadmap questions or further technical questions, please email 
biglake-h...@google.com


-- 
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: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to