External stage clone should have directory table if it is enabled in source stage (Pending)¶

When the 2026_06 behavior change bundle is enabled in your account, cloning a database or schema that contains an external stage with a directory table preserves the directory table on the cloned stage. The cloned directory table is populated with the same file metadata as the source.

Before the change:

When you clone a database or schema containing an external stage that has a directory table enabled, the cloned external stage does not have a functioning directory table. SHOW STAGES may report directory_enabled = Y on the cloned stage, but querying the directory table with SELECT or refreshing it with ALTER STAGE ... REFRESH fails with an error such as “Target table not found for refreshing”.

After the change:

When you clone a database or schema containing an external stage that has a directory table enabled, the cloned external stage includes a fully functioning directory table. The directory table is reconstructed from the source stage’s file metadata (no file copy is needed because both stages reference the same cloud storage location).

Auto-refresh is disabled on the cloned directory table, consistent with internal stage clone semantics. To re-enable auto-refresh on the cloned stage, see Automated directory table metadata refreshes.

Ref: 2352