Skip to content

fix: Document missing file_format parameter for SharePoint connector#1532

Closed
claudespice wants to merge 9 commits intotrunkfrom
fix/docs-sharepoint-file-format
Closed

fix: Document missing file_format parameter for SharePoint connector#1532
claudespice wants to merge 9 commits intotrunkfrom
fix/docs-sharepoint-file-format

Conversation

@claudespice
Copy link
Copy Markdown
Collaborator

Summary

  • The SharePoint connector defines a file_format runtime parameter in its ParameterSpec but the parameter was not documented
  • Other file-based connectors (S3, ABFS, NFS, SMB, FTP) already document this parameter

Changes

  • Added file_format to the SharePoint connector parameter table across all 8 doc versions (vNext + 1.5.x through 1.11.x)

Reference

Verified against spiceai/spiceai at trunkcrates/data-connectors/connector-sharepoint/src/lib.rs (line 134: ParameterSpec::runtime("file_format"))

Also verified present at tags v1.5.0 through v1.11.5.

Claude added 6 commits April 18, 2026 03:11
…rsioned docs

Commit d5341c4 documented the Arrow nanosecond timestamp range
limitation (~1677–2262) for MSSQL and Oracle connectors, but only
in website/docs/ (vNext). The limitation existed in all prior versions
too — in versions 1.5.x–1.11.x, out-of-range timestamps silently
returned 1970-01-01 UTC instead of erroring.

Propagate the limitation note to all 7 versioned doc directories
(14 files total) with version-appropriate wording.
…d defaults

The docs listed pg_connection_pool_min_idle (default 1) and connection_pool_size
(default 5), but the code uses pg_connection_pool_min (default 5) and
connection_pool_size (default 10).
The docs stated the default ssl_mode is tls, but the code has always
used auto as the default since at least v1.5.0.
The docs showed the default time format as 2006-01-02T15:04:05Z07:00
but the code uses 2006-01-02T15:04:05.000Z07:00 (with .000 milliseconds).
This matters because Go format strings are exact patterns — without .000,
timestamps with millisecond precision would not parse correctly.
The PostgreSQL connector added logical replication (WAL streaming) support
in PR #10364 with 5 new parameters (pg_replication_slot, pg_publication,
pg_replication_initial_snapshot, pg_replication_temporary_slot,
pg_replication_status_interval) that were not yet documented.
The SharePoint connector defines a file_format runtime parameter in its
ParameterSpec that was not documented. Other file-based connectors (S3,
ABFS, NFS, SMB, FTP) already document this parameter.
@claudespice claudespice added the bug Something isn't working label Apr 19, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 19, 2026

✅ Pull with Spice Passed

Passing checks:

  • ✅ Title meets minimum length requirement (10 characters)
  • ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
  • ✅ No banned labels detected
  • ✅ Has at least one assignee: lukekim

@lukekim lukekim self-assigned this Apr 20, 2026
@lukekim lukekim enabled auto-merge (squash) April 20, 2026 17:12
@lukekim lukekim closed this Apr 27, 2026
auto-merge was automatically disabled April 27, 2026 00:44

Pull request was closed

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

Labels

area/docs bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants