Skip to content

Comments

Add Go example for schema-transform nested field access#37543

Open
MemonaAmirAbdulHaq wants to merge 2 commits intoapache:masterfrom
MemonaAmirAbdulHaq:beam-21184-go-schema-transform
Open

Add Go example for schema-transform nested field access#37543
MemonaAmirAbdulHaq wants to merge 2 commits intoapache:masterfrom
MemonaAmirAbdulHaq:beam-21184-go-schema-transform

Conversation

@MemonaAmirAbdulHaq
Copy link

  1. Description:
    This PR adds a Go example demonstrating how to access nested fields using the schema-transform feature in Apache Beam. It updates the documentation in programming-guide.md with a practical example for Go developers.

  2. Changes included
    - Added a Go code snippet showing nested field access.
    - Improved explanations for clarity in the Go section of the schema-transform guide.

  3. Why this is useful

    • Helps Go developers understand and use nested schema transformations.
    • Complements existing documentation with a working, practical example.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @MemonaAmirAbdulHaq, 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 enhances the Apache Beam documentation for Go developers by providing a concrete example of how to utilize schema-transform features for nested field access. The update clarifies the process of working with schema-aware PCollections in Go, making the documentation more practical and up-to-date.

Highlights

  • Go Schema Example Added: Introduced a new Go code example demonstrating how to access nested fields within schema-aware PCollections, specifically extracting a post code from a nested shipping address struct.
  • Documentation Update: The programming-guide.md file has been updated to include this practical Go example, replacing a previous statement that indicated a lack of native Go support for Schema transforms.
  • Clarity Improvement: Enhanced the introductory explanation for Go developers on using schema-aware PCollections, guiding them on defining structs for schema inference and direct field access.

🧠 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
  • website/www/site/content/en/documentation/programming-guide.md
    • Removed an outdated statement indicating that Beam did not yet support Schema transforms natively in Go.
    • Added a Go code snippet demonstrating the definition of nested structs (ShippingAddress, Purchase) and the extraction of a nested field (PostCode) using beam.ParDo.
    • Updated the descriptive text for Go's schema usage to explain how schemas are inferred from struct types and how to access fields directly in transforms.
Activity
  • No human activity has been recorded on this pull request yet.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 7, 2026

Assigning reviewers:

R: @Abacn for label website.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

@MemonaAmirAbdulHaq
Copy link
Author

Hi @Abacn Can you review it
Regards !!

@MemonaAmirAbdulHaq
Copy link
Author

Hi @damccorm, please have a look at this PR, if you got some time, thanks.


A schema on a `PCollection` enables a rich variety of relational transforms. The fact that each record is composed of
named fields allows for simple and readable aggregations that reference fields by name, similar to the aggregations in
a SQL expression.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you remove this?

postCodes := beam.ParDo(s, func(p Purchase) string {
return p.ShippingAddress.PostCode
}, purchases)
{{< /highlight >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of dropping this into the top level section, we should follow the same pattern used by the other languages

Comment on lines 4184 to 4187
},
)
postCodes := beam.ParDo(s, func(p Purchase) string {
return p.ShippingAddress.PostCode
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This just shows how you can access fields of a Go object, it seems unrelated to schemas

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the feedback. I've restored the original schema description .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants