Skip to content

feat(firestore): add DML stages, literals source, and atomic execution option to Android SDK pipelines - #8524

Open
wu-hui wants to merge 3 commits into
mainfrom
feat-android-pipeline-dml
Open

feat(firestore): add DML stages, literals source, and atomic execution option to Android SDK pipelines#8524
wu-hui wants to merge 3 commits into
mainfrom
feat-android-pipeline-dml

Conversation

@wu-hui

@wu-hui wu-hui commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds full DML stages (Delete, Update, Insert, Upsert), Literals source, and atomic execution option to the Android SDK (firebase-android-sdk) Firestore Pipelines subsystem to achieve parity with Web and Node SDKs.

Key Changes

  • stage.kt: Added DeleteStage, UpdateStage, InsertStage, UpsertStage, and LiteralsSource.
  • options.kt: Added hasAtomic() helper method to InternalOptions.
  • Pipeline.kt:
    • Added withAtomic(atomic: Boolean) method to ExecuteOptions.
    • Updated toExecutePipelineRequest to configure newTransaction (readWrite) and autoCommitTransaction = true when atomic is enabled.
    • Added literals(vararg data: Map<String, Any?>) source builder method to PipelineSource.
    • Added delete(), update(...), insert(...), and upsert(...) stage builder methods to Pipeline.
  • Unit & Integration Tests:
    • Added unit test suite in DmlTests.kt verifying proto generation and options encoding for all stages.
    • Added integration test methods in PipelineTest.java.

Buganizer Ticket

Fixes http://b/545136695 (under umbrella http://b/500350942)

…erals source, and atomic execution option to Android SDK pipelines

- Implement DeleteStage, UpdateStage, InsertStage, UpsertStage, and LiteralsSource in stage.kt
- Add literals() source method to PipelineSource and delete(), update(), insert(), upsert() to Pipeline in Pipeline.kt
- Add withAtomic() execution option to ExecuteOptions and wire proto request (newTransaction + autoCommitTransaction)
- Add DmlTests.kt unit test suite verifying proto generation for all stages
- Add integration test methods in PipelineTest.java

BUG=b/545136695
TAG=agy
@gemini-code-assist

Copy link
Copy Markdown
Contributor
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 the 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 counterproductive. 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.

@google-oss-bot

Copy link
Copy Markdown
Collaborator

Did you forget to add a changelog entry? (Add the 'no-changelog' label to the PR or 'NO_RELEASE_CHANGE' to the description to silence this warning.)

@github-actions

Copy link
Copy Markdown
Contributor

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.

@google-oss-bot

Copy link
Copy Markdown
Collaborator

The public api surface has changed for the subproject firebase-firestore:
error: Added method com.google.firebase.firestore.Pipeline.delete() [AddedMethod]
error: Added method com.google.firebase.firestore.Pipeline.insert(String,com.google.firebase.firestore.pipeline.Expression) [AddedMethod]
error: Added method com.google.firebase.firestore.Pipeline.update(com.google.firebase.firestore.pipeline.Selectable...) [AddedMethod]
error: Added method com.google.firebase.firestore.Pipeline.upsert(com.google.firebase.firestore.pipeline.Selectable[],String,com.google.firebase.firestore.pipeline.Expression) [AddedMethod]
error: Added method com.google.firebase.firestore.Pipeline.ExecuteOptions.withAtomic(boolean) [AddedMethod]
error: Added method com.google.firebase.firestore.PipelineSource.literals(java.util.List>) [AddedMethod]
error: Added method com.google.firebase.firestore.PipelineSource.literals(java.util.Map<java.lang.String,?>...) [AddedMethod]
error: Added class com.google.firebase.firestore.pipeline.LiteralsSource [AddedClass]

Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly.

@google-oss-bot

Copy link
Copy Markdown
Collaborator

The public api surface has changed for the subproject firebase-firestore:
error: Added class com.google.firebase.firestore.pipeline.LiteralsSource [AddedClass]

Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly.

@google-oss-bot

Copy link
Copy Markdown
Collaborator

The public api surface has changed for the subproject firebase-firestore:
error: Added class com.google.firebase.firestore.pipeline.LiteralsSource [AddedClass]

Please update the api.txt files for the subprojects being affected by this change by running ./gradlew ${subproject}:generateApiTxtFile. Also perform a major/minor bump accordingly.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants