-
Notifications
You must be signed in to change notification settings - Fork 4.4k
[Java]Fix Neo4jIO WriteUnwindWithResultsFn for Statistics Emission #35949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @Suvrat1629, 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 Neo4jIO connector for Apache Beam by enabling the emission of detailed write statistics from UNWIND operations. It introduces a new Neo4jWriteStats
class to encapsulate these metrics and modifies the WriteUnwindWithResultsFn
to correctly output them. This update resolves a critical compilation blocker, improving the connector's functionality and providing valuable insights into write performance.
Highlights
- Introduction of Neo4jWriteStats Class: A new serializable class,
Neo4jWriteStats
, has been added to capture comprehensive metrics from Neo4j write operations, including counts for created/deleted nodes, relationships, properties, and labels. - New WriteUnwindWithResults API: A new API method,
writeUnwindWithResults()
, is now available inNeo4jIO
, allowing users to perform UNWIND write operations and receive aPCollection
containing theNeo4jWriteStats
for each batch. - Implementation of WriteUnwindWithResultsFn: The core logic for processing batched data, executing UNWIND Cypher queries, and emitting the
Neo4jWriteStats
is implemented within the newWriteUnwindWithResultsFn
DoFn. - Resolution of Compilation Errors: The changes directly resolve compilation errors related to the
WriteUnwindWithResultsFn
, addressing a critical blocker for the Neo4jIO connector.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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
-
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. ↩
@fbiville I have taken an attempt at getting started with your issue(#33041) would be nice if you could guide me for improving this pr further. These are the things I need help addressing:
|
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
assign set of reviewers |
Assigning reviewers: R: @Abacn 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). |
Reminder, please take a look at this pr: @Abacn |
Please add a meaningful description for your change here
This PR addresses #33041, a blocker for Neo4jIO in the Neo4j Flex template. It fixes WriteUnwindWithResultsFn to emit Neo4jWriteStats, resolving compilation errors. Further work is needed to enhance WriteUnwind and improve timestamp accuracy.
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.