Skip to content

feat(firestore): 16MB docs support#8219

Draft
dlarocque wants to merge 1 commit into
mainfrom
dl/large-docs
Draft

feat(firestore): 16MB docs support#8219
dlarocque wants to merge 1 commit into
mainfrom
dl/large-docs

Conversation

@dlarocque
Copy link
Copy Markdown
Contributor

WIP

Adds support for 16MB docs in Firestore.

Changes:

  • Increases the gRPC message receive size limit from 4MB to 17MB (16MB doc + overhead).
  • Implements a workaround for the CursorWindow 2MB row read limit for reading large docs from local storage. If a row's content is larger than 1MB, executes a seperate query that reads the content in chunks using SUBSTR with a chunk size smaller than the row read limit. This is a slow operation for 16MB docs, taking ~200ms in my testing on the local emulator.
  • Debug logs are now truncated if they exceed 128KB. Formatting proto responses with large documents to strings consumed a huge amount of memory. In one extreme case, formatting a response containing a doc with a field containing 16MB of emojis caused an OOM on emulators.
  • Adds tests explicitly for large documents.

WIP

Adds support for 16MB docs in Firestore.

Changes:
- Increases the gRPC message receive size limit from 4MB to 17MB (16MB
  doc + overhead).
- Implements a workaround for the `CursorWindow` 2MB row read limit for
  reading large docs from local storage. If a row's content is larger
  than 1MB, executes a seperate query that reads the content in chunks
  using `SUBSTR` with a chunk size smaller than the row read limit. This
  is a slow operation for 16MB docs, taking ~200ms in my testing on
  the local emulator.
- Debug logs are now truncated if they exceed 128KB. Formatting proto
  responses with large documents to strings consumed a huge amount of
  memory. In one extreme case, formatting a response containing a doc
  with a field containing 16MB of emojis caused an OOM on emulators.
- Adds tests explicitly for large documents.
@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.

@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

1 Warning
⚠️ Did you forget to add a changelog entry? (Add the 'no-changelog' label to the PR to silence this warning.)

Generated by 🚫 Danger

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