Conversation
Summary of ChangesHello @ahmedabu98, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the Apache Beam website by introducing extensive documentation for SQL Data Definition Language (DDL) commands, making it easier for users to understand and utilize SQL for managing Catalogs, Databases, and Tables. Concurrently, it refines the Iceberg SQL connector's ability to handle table properties, including a new convention for Beam-specific configurations, and updates existing documentation to reflect these capabilities and new table types. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
f2675e8 to
257cd5a
Compare
|
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
…erg_getting_started
|
Assigning reviewers: R: @kennknowles for label java. Note: If you would like to opt out of this review, comment Available commands:
The PR bot will only process comments in the main thread (not review comments). |
| 'uri' = 'https://biglake.googleapis.com/iceberg/v1/restcatalog', | ||
| 'warehouse' = 'gs://my-company-bucket/warehouse', | ||
| 'header.x-goog-user-project' = 'my_prod_project', | ||
| 'rest.auth.type' = 'org.apache.iceberg.gcp.auth.GoogleAuthManager', |
There was a problem hiding this comment.
We can use rest.auth.type='google' We dont need to give fullname of class.
| # Beam SQL DDL Overview | ||
|
|
||
| Beam SQL provides a robust hierarchy for managing metadata for external data sources. Instead of treating all tables as flat objects, Beam SQL utilizes a three-tier namespace system: | ||
| 1. Catalog: The highest level container (e.g. a Glue Catalog connected to S3 or a BigLake Catalog connected to GCS). |
There was a problem hiding this comment.
Maybe you should mentioned Hive too ?
| 2. Database: A logical namespace within a Catalog (often maps to "namespace" in systems like Iceberg). | ||
| 3. Table: The actual data entity containing schema and rows. | ||
|
|
||
| This structure allows users to connect to multiple disparate systems (e.g., a production BigQuery catalog and a dev Iceberg catalog) simultaneously and switch contexts seamlessly. |
There was a problem hiding this comment.
Can users join two tables from different catalog such as a table from Hive and another from Biglake ?
Adding some SQL DDL documentation to the Beam website.
Specifically the following commands for Catalogs, Databases, Tables: