Skip to content

Conversation

@aguest-kc
Copy link
Contributor

@aguest-kc aguest-kc commented Nov 20, 2025

Description:

Add DuckDB as an option for File B Custom Account downloads.

Technical Details:

DuckDB's Spark implementation doesn't implement every Spark/PySpark function so some substitutions had to be made when using DuckDB.

Requirements for PR Merge:

  1. Unit & integration tests updated
  2. Data validation completed (examples listed below)
  3. Appropriate Operations ticket(s) created
  4. Jira Ticket(s)
    1. DEV-13726

Explain N/A in above checklist:

  1. API documentation updated (examples listed below)
    No API documentation is affected by this change.

@aguest-kc aguest-kc added the do not merge [PR] shouldn't be merged label Nov 20, 2025
@aguest-kc aguest-kc removed the do not merge [PR] shouldn't be merged label Dec 8, 2025
Copy link
Contributor

@sethstoudenmier sethstoudenmier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few more comments on use of CONFIG I noticed and then some questions about error handling, but mostly looking good. Still outstanding thought on if we want to include a new Dockerfile to breakout install of DuckDB.

@aguest-kc aguest-kc merged commit e63e52d into qat Dec 15, 2025
36 of 37 checks passed
@aguest-kc aguest-kc deleted the ftr/dev-13726-duckdb-file-b-downloads branch December 16, 2025 20:28
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.

3 participants