Repository navigation
SNOW-4522850: Make JDBC ingestion documentation self-contained - #4532
Open
sfc-gh-yuwang wants to merge 1 commit into
Open
sfc-gh-yuwang wants to merge 1 commit into
sfc-gh-yuwang wants to merge 1 commit into
Conversation
Document source setup, bounded examples, and current conversion and execution constraints so readers can configure ingestion without guessing driver or Snowflake behavior. Generated with [Snowflake CoCo](https://docs.snowflake.com/en/user-guide/cortex-code/cortex-code) Co-authored-by: Snowflake CoCo <noreply@snowflake.com>
sfc-gh-yuwang
requested review from
sfc-gh-aling,
sfc-gh-jzeng and
sfc-gh-mayliu
and removed request for
a team
November 18, 2026 23:51
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DataFrameReader.jdbc()previously offered placeholder examples and misleading advice aboutmax_workers, schema-inference bypass, and unlimited timeouts. Its docstring now provides a complete setup-to-persistence workflow and explains the behavior implemented by this stack.Stack and coordination
Based on exact commit
3e33f580a213954204018a3ce08aeb4cccb9ab63, with PR #4530 (yuwang/SNOW-4537767-jdbc-type-mapping) as the base. This is scoped to SNOW-4522850, not a GA declaration. Query string literals already work in this base, and Oracle timezone values no longer have the stale VARIANT behavior described in the original ticket.Before integrating the sibling binary/parity work, reconcile the docstring's current binary string-conversion warning (SNOW-4554440),
fetch_size=0/schema-inference and other parity semantics (SNOW-4554443). CI and release/preview changes remain with their separate owners. No internal account parameters are advertised as customer controls.Test plan
python3 -m sphinx -E -a -W --keep-going -q -b html -j 4 ...; no Sphinx warnings. Existing Snowpark pandas hybrid-mode Python UserWarning only.git diff --checkpassed.Live checks used the existing fixture connection after the preferred local
snowparkconnection failed with an expired OAuth token. They reused existing source credentials/EAI and uploaded repository JARs to a session stage; no external databases or persistent source tables were provisioned. The temporary persistence check substitutes for creating the documented permanent destination table.Production TLS certificate/trust configuration for PostgreSQL/MySQL/SQL Server and provisioning/grant SQL were not executed; these are documented against current public vendor/Snowflake references. Live tests used existing fixture connection settings (including SQL Server's test-only certificate bypass). Placeholder examples require deployment-specific hosts, certificates, roles, credentials, and paths.
Generated with Snowflake CoCo