Skip to content

Conversation

@dantengsky
Copy link
Member

@dantengsky dantengsky commented Oct 23, 2025

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

to be detailed

Tests

  • Unit Test
  • Logic Test
  • Benchmark Test
  • No Test - Explain why

Type of change

  • Bug Fix (non-breaking change which fixes an issue)
  • New Feature (non-breaking change which adds functionality)
  • Breaking Change (fix or feature that could cause existing functionality not to work as expected)
  • Documentation Update
  • Refactoring
  • Performance Improvement
  • Other (please describe):

This change is Reviewable

Implements database-level default storage connection configuration allowing databases to specify default connection settings that tables automatically inherit during creation.

Key features:
- CREATE DATABASE OPTIONS syntax with DEFAULT_STORAGE_CONNECTION and DEFAULT_STORAGE_PATH
- ALTER DATABASE SET OPTIONS for updating connection defaults
- Automatic table inheritance of database defaults during CREATE TABLE
- Paired validation requiring both connection and path options together
- Tables can override database defaults with explicit table-level connection options
This commit completes the database-level default connection configuration feature
allowing databases to specify default storage connection settings for FUSE tables.

Key changes:
- Fix table inheritance logic: FUSE tables inherit database defaults
- Add ALTER DATABASE SET OPTIONS with paired validation
- Implement privilege checking for ALTER DATABASE operations
- Add comprehensive SQL logic tests for feature validation

The feature enables:
- CREATE DATABASE OPTIONS (DEFAULT_STORAGE_CONNECTION = '...', DEFAULT_STORAGE_PATH = '...')
- ALTER DATABASE SET OPTIONS with paired validation (both options required)
- FUSE tables automatically inherit database connection defaults for external storage

Corrected inheritance logic where FUSE tables (external storage capable) inherit
database defaults, while other engines use their own connection mechanisms.
@github-actions github-actions bot added the pr-feature this PR introduces a new feature to the codebase label Oct 23, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 23, 2025

🤖 CI Job Analysis

Workflow: 18741804425

📊 Summary

  • Total Jobs: 83
  • Failed Jobs: 5
  • Retryable: 0
  • Code Issues: 5

NO RETRY NEEDED

All failures appear to be code/test issues requiring manual fixes.

🔍 Job Details

  • linux / test_compat_meta_query: Not retryable (Code/Test)
  • linux / sqllogic / standalone (base, 2c8g, hybrid): Not retryable (Code/Test)
  • linux / sqllogic / standalone (base, 2c8g, http): Not retryable (Code/Test)
  • linux / sqllogic / cluster (base, 2c8g, 2, http): Not retryable (Code/Test)
  • linux / sqllogic / cluster (base, 2c8g, 2, hybrid): Not retryable (Code/Test)

🤖 About

Automated analysis using job annotations to distinguish infrastructure issues (auto-retried) from code/test issues (manual fixes needed).

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

Labels

pr-feature this PR introduces a new feature to the codebase

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature Request: Database level default connection configuration

1 participant