SNOWFLAKE DOCS DIFF
総括は生成されていません（claude CLI が利用できなかった可能性があります）。
（この変更は要約対象外です。diff を参照してください）
変更内容: 追加行に「breaking change」を検出
--- ahttps://docs.snowflake.com/en/user-guide/tables-auto-reclustering+++ bhttps://docs.snowflake.com/en/user-guide/tables-auto-reclustering@@ -2,4 +2,13 @@ Automatic Clustering is the Snowflake service that seamlessly and continually manages all reclustering, as needed, of clustered tables.+Automatic Clustering includes two versions:++- **Optima Clustering**: Snowflake's next-generation autonomous table optimization engine. Optima Clustering optimizes tables for query+ performance with zero manual maintenance and predictable, ingestion-based billing.+- **Clustering Classic**: The previous Automatic Clustering behavior. Clustering Classic continues to run for tables that are already+ clustered.++Starting September 1, 2026, newly clustered tables use Optima Clustering. Tables that are already clustered remain on Clustering Classic. You don't need to take any action for the rollout. This change isn't a breaking change: tables continue to see equivalent or+better clustering performance. Note that, after a clustered table is defined, reclustering does not necessarily start immediately. Snowflake only reclusters a clustered table if it will benefit from the@@ -8,4 +17,27 @@ If manual reclustering is still available in your account, Automatic Clustering might not be enabled yet for your account. For more details, see [](/user-guide/tables-clustering-manual). +<a id="label-optima-clustering"></a>++## Optima Clustering++Compared with Clustering Classic, Optima Clustering offers the following advantages:++- Faster time to cluster new data, which can improve query performance on clustered tables.+- A smart clustering algorithm that prioritizes clustering the data that matters most for query performance.+- Highly predictable billing based on data volume ingested, not compute hours. For details, see [](#label-optima-clustering-cost).++### Identifying Optima Clustering or Clustering Classic++To determine whether a table uses Optima Clustering or Clustering Classic, call+[](/sql-reference/functions/system_clustering_information).++To compare costs for each version over time, query the `VERSION` column in+[](/sql-reference/account-usage/automatic_clustering_history). The column value is `OPTIMA` or `CLASSIC`.++### Moving a table from Clustering Classic to Optima Clustering++Tables that are already clustered remain on Clustering Classic indefinitely. Changing the clustering key with an ALTER TABLE statement+doesn't move a table to Optima Clustering, and there is no migrate command.+ ## Benefits of Automatic Clustering @@ -29,4 +61,8 @@ You can suspend and resume Automatic Clustering for a clustered table at any time using ALTER TABLE ... SUSPEND / RESUME RECLUSTER. While Automatic Clustering is suspended for a table, the table is never automatically reclustered, regardless of its clustering state and, therefore, does not incur any related credit charges.++For Optima Clustering, suspending immediately stops billing for newly ingested data. When you resume clustering, Snowflake applies a catch-up cost for data ingested while+clustering was suspended. Using suspend and resume primarily to control costs is generally not cost-effective under Optima Clustering. If you want to stop paying for+clustering permanently, drop the clustering key instead. You can also drop the clustering key on a clustered table at any time, which prevents all future reclustering on the table.@@ -140,5 +176,40 @@ ## Automatic Clustering costs -The cost of enabling Automatic Clustering can be broken down into compute costs and storage costs.+Automatic Clustering costs depend on whether a table uses Optima Clustering or Clustering Classic. Both versions bill under the same Auto+Clustering service type.++<a id="label-optima-clustering-cost"></a>++### Optima Clustering costs++Optima Clustering bills based on the volume of data you ingest, not on serverless compute hours. Snowflake calculates the cost as:++```text+Clustering cost = GB ingested × 0.007 credits per GB × overlap factor+```++The overlap factor is a value between `0` and `1` that represents the proportion of ingested data that requires active clustering:++- If all ingested data requires active clustering, the overlap factor is `1`, and the cost is at most 0.007 credits per ingested GB.+- If the data is naturally well clustered on arrival, the overlap factor approaches `0`, and the cost approaches zero.++The overlap factor isn't shown as a separate rebate on your bill. Your bill shows Optima Clustering credits only.++Examples:++- Append-only workloads clustered by an ingestion timestamp (for example, hourly loads clustered by+ `TO_DATE(ingestion_time)`) typically have an overlap factor near `0` and little or no clustering charge.+- Updates that change clustering key values usually have an overlap factor of `1` and are billed at the full rate.+- Data that partially overlaps existing micro-partitions has an overlap factor between `0` and `1`.++As with Clustering Classic, changing a clustering key triggers a one-time clustering cost. For Optima Clustering, that one-time cost is+based on the existing table size at the time of the key change. Snowflake applies the Overlap Factor as if the whole table were newly+written data, so a small key change that doesn't require rewriting much data results in minimal charges.++<a id="label-clustering-classic-cost"></a>++### Clustering Classic costs++For Clustering Classic, the cost of enabling Automatic Clustering can be broken down into compute costs and storage costs. <dl>@@ -169,4 +240,7 @@ Your account is billed only for the actual credits consumed by automatic clustering operations on your clustered tables. +For Clustering Classic credit rates per compute-hour, refer to the "Serverless Feature Credit Table" in the+[Snowflake Service Consumption Table](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf).+ After enabling or resuming Automatic Clustering on a clustered table, if it has been a while since the table was reclustered, you may experience reclustering activity (and corresponding credit charges) as Snowflake brings the table to an optimally-clustered state. Once@@ -188,12 +262,11 @@ the compute cost of changing the cluster key of a table. +For Optima Clustering, the function supports estimates for one-time costs (for example, enabling clustering or changing a clustering key).+It doesn't yet return a maintenance cost estimate for Optima Clustering. Optima Clustering maintenance costs are bounded at a maximum of+0.007 credits per ingested GB.+ The cost estimates returned by the SYSTEM$ESTIMATE_AUTOMATIC_CLUSTERING_COSTS function are best efforts. The actual realized costs can vary by up to 100% (or, in rare cases, several times) from the estimated costs. ### Viewing Automatic Clustering cost--Automatic clustering consumes credits as it uses [serverless compute resources](#label-serverless-credit-usage) for the-automated background maintenance of each clustered table, including initial clustering and reclustering as needed. To learn how many-credits per compute-hour are consumed by automatic clustering, refer to the "Serverless Feature Credit Table" in the-[Snowflake Service Consumption Table](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf). Users with the proper privileges can view the cost of automatic clustering using %sf-web-interface-link% or SQL:@@ -215,4 +288,7 @@ - [](/sql-reference/functions/automatic_clustering_history) table function (in the [](/sql-reference/info-schema)). - [](/sql-reference/account-usage/automatic_clustering_history) (in [](/sql-reference/account-usage)).++ Both Optima Clustering and Clustering Classic appear under the Auto Clustering service type. Use the `VERSION` column in+ AUTOMATIC_CLUSTERING_HISTORY to distinguish them (`OPTIMA` or `CLASSIC`). The following queries can be executed against t... (truncated)
差分が長いため、途中まで表示しています。
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（33行追加・7行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/cost+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-app-runtime/cost@@ -25,8 +25,30 @@ </div> -All App Runtime apps in an account share Snowflake-managed compute. Credit+All apps in an account share a single Snowflake-managed compute pool. Credit usage is billed at the account level under the `SNOWFLAKE_APP_RUNTIME` service type, separate from your warehouses and other compute. Per-app cost attribution isn't available.++### Credit rate++App Runtime credits are charged per compute-hour at the rate listed in the+[Snowflake Service Consumption Table](https://www.snowflake.com/legal-files/CreditConsumptionTable.pdf)+under "Serverless Feature Credit Table" for the `SNOWFLAKE_APP_RUNTIME` service+type. The managed compute pool uses `CPU_X64_S` nodes (3 vCPU, 13 GiB RAM).+This rate reflects a discount relative to the equivalent self-managed SPCS+compute pool node rate.++You are not billed per request or per concurrent user — cost depends on how+long the underlying compute nodes run, regardless of whether your app is+handling traffic.++### Billing lifecycle++App Runtime billing follows the same lifecycle as SPCS compute pools. For+details on how costs accrue in each state (ACTIVE, IDLE, SUSPENDED), see+[Compute pool cost](/developer-guide/snowpark-container-services/accounts-orgs-usage-views#label-compute-pool-cost).++Apps left running while idle still accrue credits. If you deploy an app for+testing or occasional use, suspend it when not needed. <a id="label-snowflake-app-runtime-cost-metering-history"></a>@@ -81,15 +103,19 @@ ## Reduce App Runtime cost -App Runtime bills compute only while apps are running. To reduce cost:+App Runtime apps run continuously once created. An app that is deployed but+not actively used still consumes compute until it is suspended or dropped. To+control cost: - **Suspend idle apps.** Use [`ALTER APPLICATION SERVICE ... SUSPEND`](/sql-reference/sql/alter-application-service)- to stop billing compute for apps that aren't in active use.-- **Monitor app state.** Use- [](/developer-guide/snowflake-app-runtime/observability) to find apps stuck- in unexpected states that may still consume compute.+ to release compute for apps not in active use. Resume them with+ [`ALTER APPLICATION SERVICE ... RESUME`](/sql-reference/sql/alter-application-service)+ when needed. - **Drop unused apps.** Use [`DROP APPLICATION SERVICE`](/sql-reference/sql/drop-application-service)- to remove apps you no longer need.+ to permanently remove apps you no longer need.+- **Monitor app state.** Use+ [Observability for Snowflake App Runtime](/developer-guide/snowflake-app-runtime/observability)+ to find apps stuck in unexpected states that may still be consuming compute. ## See also
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（24行追加・1行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/functions/system_clustering_information+++ bhttps://docs.snowflake.com/en/sql-reference/functions/system_clustering_information@@ -10,5 +10,5 @@ # SYSTEM$CLUSTERING_INFORMATION -Returns clustering information, including average clustering depth, for a table based on one or more columns in the table.+Returns clustering information, including average clustering depth and Automatic Clustering version, for a table based on one or more columns in the table. <dl>@@ -17,4 +17,6 @@ [](/sql-reference/functions/system_clustering_depth)++[](/user-guide/tables-auto-reclustering) </dd>@@ -65,4 +67,9 @@ in a single function call. - The table name, column name, and expression are strings, and should be enclosed in single quotes.+- For tables that use Optima Clustering, the following fields aren't available:+ - `total_constant_partition_count`+ - `partition_depth_histogram`++ For more information about Optima Clustering, see [](/user-guide/tables-auto-reclustering#label-optima-clustering). ## Returns@@ -77,4 +84,15 @@ Columns in table used to return clustering information; can be any columns in the table.++</dd>+<dt>`version`</dt>+<dd>++Version of Automatic Clustering for the table:++- `CLASSIC`: Clustering Classic+- `OPTIMA`: Optima Clustering++For more information, see [](/user-guide/tables-auto-reclustering#label-optima-clustering). </dd>@@ -103,4 +121,6 @@ corresponding impact on performance. +This field isn't available for tables that use Optima Clustering.+ </dd> <dt>`average_overlaps`</dt>@@ -125,4 +145,6 @@ - `0` to `16` with increments of `1`. - For buckets larger than `16`, increments of twice the width of the previous bucket (e.g. `32`, `64`, `128`, ...).++This field isn't available for tables that use Optima Clustering. </dd>@@ -167,4 +189,5 @@ | { | | "cluster_by_keys" : "LINEAR(COL1, COL3)", |+| "version" : "CLASSIC", | | "total_partition_count" : 1156, | | "total_constant_partition_count" : 0, |
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（11行追加・11行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/managed-settings+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/managed-settings@@ -24,5 +24,5 @@ - `ui.hideDangerousOptions` (boolean): hide the dangerous-options UI. -The managed-settings schema is shared with CoCo CLI, but some CLI-only keys have no effect in Desktop: `required.minimumVersion` (Desktop has its own auto-update), `settings.forceSandboxEnabled` / `settings.forceSandboxMode`, `files.connectionsFile` / `files.mcpFile`, and `defaults.*`. For the complete schema and pattern reference, see [Managed settings (organization policy)](/user-guide/cortex-code/managed-settings).+The managed-settings schema is shared with CoCo CLI, but some CLI-only keys have no effect in Desktop: `required.minimumVersion` (Desktop has its own auto-update), `settings.forceSandboxEnabled` / `settings.forceSandboxMode`, `files.connectionsFile` / `files.mcpFile`, `defaults.*`, and `account()` (Desktop reads the setting but does not enforce it; account restrictions are CLI-only). For the complete schema and pattern reference, see [Managed settings (organization policy)](/user-guide/cortex-code/managed-settings). ## Permission patterns@@ -30,14 +30,14 @@ Patterns in `onlyAllow` and `deny` are either a bare tool name or `type(filter)`, where `filter` is a case-insensitive glob (`*` and `?`). For `bash`, the filter matches the first token of the command. -| Pattern | What it controls |-| ------------------------------------------------------ | ------------------------------------------ |-| `read`, `write`, `edit` | The file read, write, and edit tools |-| `bash` | All shell commands |-| `bash(git:*)`, `bash(dbt:*)` | Shell restricted to `git` / `dbt` commands |-| `bash(rm:*)`, `bash(curl:*)` | Specific commands (commonly denied) |-| `sql_execute` | SQL execution against Snowflake |-| `mcp(*)`, `mcp(https://*.acme.com/*)` | MCP servers, all or by URL glob |-| `skill(bundled:*)`, `skill(user:*)`, `skill(remote:*)` | Skills by source |-| `account(myorg-*)` | Snowflake accounts by name |+| Pattern | What it controls |+| ------------------------------------------------------ | -------------------------------------------------------------------------------------- |+| `read`, `write`, `edit` | The file read, write, and edit tools |+| `bash` | All shell commands |+| `bash(git:*)`, `bash(dbt:*)` | Shell restricted to `git` / `dbt` commands |+| `bash(rm:*)`, `bash(curl:*)` | Specific commands (commonly denied) |+| `sql_execute` | SQL execution against Snowflake |+| `mcp(*)`, `mcp(https://*.acme.com/*)` | MCP servers, all or by URL glob |+| `skill(bundled:*)`, `skill(user:*)`, `skill(remote:*)` | Skills by source |+| `account(myorg-*)` | Snowflake accounts by name (CLI-only; Desktop reads but does not enforce this setting) | ## Examples
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（10行追加・1行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/organization-usage/automatic_clustering_history+++ bhttps://docs.snowflake.com/en/sql-reference/organization-usage/automatic_clustering_history@@ -20,5 +20,6 @@ your organization's tables within a specified date range. The information returned by the function includes the credits consumed, bytes updated, and rows-updated each time a table is reclustered.+updated each time a table is reclustered. Use the VERSION column to distinguish+Optima Clustering (`OPTIMA`) from Clustering Classic (`CLASSIC`). ## Columns@@ -109,4 +110,12 @@ <td>Name of the database that contains the table.</td> </tr>+ <tr>+ <td>VERSION</td>+ <td>VARCHAR</td>+ <td>+ Version of Automatic Clustering that produced the credits: `CLASSIC` for Clustering Classic, or `OPTIMA` for Optima Clustering.+ For more information, see [](/user-guide/tables-auto-reclustering#label-optima-clustering).+ </td>+ </tr> </tbody>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（9行追加・1行削除）
--- ahttps://docs.snowflake.com/en/sql-reference/account-usage/automatic_clustering_history+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage/automatic_clustering_history@@ -10,5 +10,5 @@ # AUTOMATIC_CLUSTERING_HISTORY view -This Account Usage view can be used to query the [](/user-guide/tables-auto-reclustering) history. The information returned by the view includes the credits consumed, bytes updated, and rows updated each time a table is reclustered.+This Account Usage view can be used to query the [](/user-guide/tables-auto-reclustering) history. The information returned by the view includes the credits consumed, bytes updated, and rows updated each time a table is reclustered. Use the VERSION column to distinguish Optima Clustering (`OPTIMA`) from Clustering Classic (`CLASSIC`). ## Columns@@ -89,4 +89,12 @@ <td>Internal/system-generated identifier for the instance that the object belongs to.</td> </tr>+ <tr>+ <td>VERSION</td>+ <td>VARCHAR</td>+ <td>+ Version of Automatic Clustering that produced the credits: `CLASSIC` for Clustering Classic, or `OPTIMA` for Optima Clustering.+ For more information, see [](/user-guide/tables-auto-reclustering#label-optima-clustering).+ </td>+ </tr> </tbody>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（7行追加・0行削除）
--- ahttps://docs.snowflake.com/en/release-notes/preview-features+++ bhttps://docs.snowflake.com/en/release-notes/preview-features@@ -79,4 +79,11 @@ <tbody> <tr>+ <td>Workday Live Data Query for Snowflake</td>+ <td>On Request</td>+ <td>August 2026</td>+ <td>[](/user-guide/data-integration/zero-copy/about-workday-ldq)</td>+ <td>Query Workday business data in real time from a Snowflake Notebook through a Python connector, with no ETL or data replication. In preview for Snowflake and Early Adopter for Workday; contact your Workday account representative to request access.</td>+ </tr>+ <tr> <td>Automations in %sf-intelligence%</td> <td>Open</td>
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・2行削除）
--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-ai-guardrails+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-ai-guardrails@@ -21,6 +21,8 @@ Cortex AI Guardrails provide the following protections: -- **Prompt injection detection**: Identifies and blocks attempts to override system instructions through- malicious prompts, including indirect prompt injections embedded in tool calls.+- **Prompt injection detection**: Scans each tool's outputs to detect and flag indirect+ prompt injections that attempt to override system instructions. Combined with the base model's+ built-in protections against known prompt injection and jailbreak techniques, this provides layered+ coverage to block direct and indirect attack paths. - **Jailbreak prevention**: Detects attempts to bypass the model's safety protocols and security boundaries. - **Zero-day style protection**: Uses advanced techniques to identify sophisticated, previously unknown
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（5行追加・0行削除）
--- ahttps://docs.snowflake.com/en/release-notes/bcr-bundles/2026_06/bcr-2376+++ bhttps://docs.snowflake.com/en/release-notes/bcr-bundles/2026_06/bcr-2376@@ -12,4 +12,9 @@ including [Cortex Code](/user-guide/cortex-code/cortex-code). All inference routing stays within your cloud provider. No data crosses to a different cloud provider.++During the opt-in and opt-out period for this bundle, Snowflake applies this+change in a weekly batch. Enabling the bundle doesn't+update the parameter immediately. To apply a value right away, or to stay+outside this BCR, set `CORTEX_ENABLED_CROSS_REGION` at the account level. If you have already set any explicit value for `CORTEX_ENABLED_CROSS_REGION`
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（4行追加・0行削除）
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/introduction/introduction+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/introduction/introduction@@ -62,2 +62,6 @@ Snowflake plans to continue enhancing %sf-cli% to provide developers a robust tool for leveraging all of the SnowSQL capabilities in a new open source CLI.++## Security considerations++Some %sf-cli% commands execute code from your project directory, including subdirectories, or fetch and execute content from remote URLs. Only run %sf-cli% commands on projects, packages, and SQL sources you trust.
（この変更は要約対象外です。diff を参照してください）
変更内容: 本文を更新（1行追加・3行削除）
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight@@ -181,5 +181,5 @@ ## Web search -An ACCOUNTADMIN role can configure CoCo CLI to search the web, and use the results in generating responses and+An ACCOUNTADMIN role can configure CoCo to search the web, and use the results in generating responses and planning tasks. To properly enable web search in an account, follow these steps: @@ -309,6 +309,4 @@ the root directory of your workspace for personalized instructions that apply to conversations with CoCo about your project. -Support for [Agent Skills](https://agentskills.io/) will be available soon.- ## Skills
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/overview+++ bhttps://docs.snowflake.com/en/migrations/aim-for-datawarehouses/data-migration-validation/overview@@ -29,5 +29,5 @@ Before you use AIM DMV, make sure the following are in place: -- **Snowflake access**: Connections for the Orchestrator and Workers in your Snowflake `config.toml` or `connections.toml`, using a role that can create the `SNOWCONVERT_AI` database and its objects.+- **Snowflake access**: Connections for the Orchestrator and Workers in your Snowflake `config.toml` or `connections.toml`, using a role that can create the `SNOWCONVERT_AI` database and its objects. See [Required privileges](./required-privileges) for the full list of grants that role needs. - **Source connectivity**: Platform-specific drivers on Workers. See the per-platform pages under [Data migration](./data-migration) and [Data validation](./data-validation). - **Hybrid Tables**: On bootstrap, AIM DMV probes whether Hybrid Tables are enabled and available in your Snowflake account and region. When they are, `SNOWCONVERT_AI` metadata objects (for example the task queue) are created as Hybrid Tables. When they are not, AIM DMV falls back to standard tables instead. Workflows still run in both cases, but metadata operations are slower without Hybrid Tables. Review [Hybrid Tables](https://docs.snowflake.com/en/user-guide/tables-hybrid) and [Hybrid Tables limitations](https://docs.snowflake.com/en/user-guide/tables-hybrid-limitations).@@ -57,4 +57,5 @@ - [Data migration](./data-migration) - [Data validation](./data-validation)+- [Required privileges](./required-privileges) - [The SNOWCONVERT_AI database](./snowconvert-ai-database) - [Deploying workers](./deploy-workers)
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/native-apps-commands/bundle-app+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/native-apps-commands/bundle-app@@ -173,4 +173,7 @@ - It executes those Python files in the sandboxed environment. - It collects all decorated functions from those files.++The Snowpark processor executes Python files from your project directory, including subdirectories. Only use `snow app bundle`, `snow app deploy`, and `snow app diff` with projects and Python files you trust.+ - With the collected information, %sf-cli% generates the necessary SQL statements and adds them to the setup script whose location is specified in your `manifest.yaml` file.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/dcm-projects/dcm-projects-supported-entities+++ bhttps://docs.snowflake.com/en/user-guide/dcm-projects/dcm-projects-supported-entities@@ -327,4 +327,6 @@ ### Share +Available to all accounts.+ %dcm% supports defining shares, which lets you manage the share object and all `GRANT` statements on it declaratively, controlling which objects are exposed to the share. All share properties supported by
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/snowpark/build+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/snowpark/build@@ -9,4 +9,6 @@ The `snow snowpark build` command builds the Snowpark project as one or more `.zip` archive files that can be used by the `deploy` command. The cp,,amd builds the archives using only the `src` directory specified in the project file.++`snow snowpark build` executes code from packages in your `requirements.txt` as part of the build process. Only build projects and dependencies you trust. ```snowcli
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/sql/execute-sql+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/sql/execute-sql@@ -275,4 +275,6 @@ - Evaluates variable substitutions and templates. - Reads the contents of all nested files to ensure that no recursion occurs.++`snow sql` can execute SQL from remote URLs. Only execute SQL from sources you trust. When the variables and templates are resolved and no recursion is detected, the command sends the code to Snowflake for execution.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/bundle-app+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/bundle-app@@ -147,4 +147,6 @@ While the Snowpark decorators in %sf-cli% work the same as regular Snowpark Python decorators, you should be aware of the following differences when writing Python code files specifically for a %native-app%: +The Snowpark processor executes Python files from your project directory, including subdirectories. Only use `snow app bundle`, `snow app deploy`, and `snow app diff` with projects and Python files you trust.+ - You can't use any `Session` objects in these files, as %sf-cli% executes these Python files in a sandbox environment with no connection to Snowflake. As a result, any reference of a Snowpark `Session` results in an error. - You can use only the `@udf`, `@sproc`, `@udaf` and `@udtf` Snowpark Python decorators.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/sql-reference/functions/automatic_clustering_history+++ bhttps://docs.snowflake.com/en/sql-reference/functions/automatic_clustering_history@@ -13,5 +13,5 @@ credits consumed, bytes updated, and rows updated each time a table is reclustered. -This function is generally deprecated in favor of the+This function does not include Optima Clustering data and is deprecated in favor of the [ACCOUNT_USAGE.AUTOMATIC_CLUSTERING_HISTORY view](/sql-reference/account-usage/automatic_clustering_history), which provides a more complete data set and supports longer date ranges.
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cli-reference+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cli-reference@@ -76,5 +76,5 @@ | `cortex mcp remove <server_name>` | Remove server | -See [](#extensibility-mcp) for details.+See [MCP (Model Context Protocol)](extensibility#extensibility-mcp) for details. ## Interactive mode
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-cli+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-cli@@ -69,5 +69,5 @@ Type natural-language requests (such as "find tables with PII tags" or "generate a Streamlit app for SALES_MART.REVENUE") and CoCo attempts to fulfill the request by orchestrating Snowflake-native skills and any-MCP tools you have configured. For more information on configuring MCP tools, see [](#extensibility-mcp).+MCP tools you have configured. For more information on configuring MCP tools, see [MCP (Model Context Protocol)](extensibility#extensibility-mcp). As it works on your request, CoCo CLI displays its reasoning steps and actions in the terminal. From time to
（この変更は要約対象外です。diff を参照してください）
変更内容: 3行以下の小規模な更新
--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/project-definitions+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/project-definitions@@ -166,4 +166,6 @@ These scripts are invoked by commands that create or update an entity. For example, running the `snow app deploy` command executes these scripts after creating or updating a package. They are also executed by `snow app run` if the application instance is not being directly installed from a version or release directive. +Post-deploy scripts execute SQL from your project directory and can access subdirectories of the current working directory. Only run `snow app deploy` and `snow app run` with projects and SQL scripts you trust.+ You can also use templates in the post-deploy SQL scripts as well, as shown in the following sample script content:
| セクション | S | A | B | C | 計 |
|---|---|---|---|---|---|
| Snowflake CLI | 0 | 0 | 1 | 5 | 6 |
| Cortex Code | 0 | 0 | 2 | 2 | 4 |
| User Guide | 1 | 0 | 0 | 1 | 2 |
| SQL Functions | 0 | 0 | 1 | 1 | 2 |
| Release Notes | 0 | 0 | 2 | 0 | 2 |
| Developer Guide | 0 | 0 | 1 | 0 | 1 |
| Organization Usage | 0 | 0 | 1 | 0 | 1 |
| Account Usage | 0 | 0 | 1 | 0 | 1 |
| Snowflake Cortex (AI & ML) | 0 | 0 | 1 | 0 | 1 |
| Migrations | 0 | 0 | 0 | 1 | 1 |