Create UDF version
Consumes a source archive, assigns a version, and starts the UDF build. Optional configuration fields omitted from the request use the defaults documented in the request schema; values are not inherited from the previous version. Retry by requesting a new upload URL and re-uploading.
Permission
control-plane:organization:manage permission.Autorizaciones
Use key ID and key secret obtained in ClickHouse Cloud console: https://clickhouse.com/docs/cloud/manage/openapi
Parámetros de ruta
ID of the requested organization.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$Name of the UDF.
^[A-Za-z][A-Za-z0-9_]*$Cuerpo
- Option 1
- Option 2
Identifier of the uploaded source archive.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$python3.11, native "executable"^[A-Za-z][A-Za-z0-9_]*$1 <= x <= 1048576Marks the UDF as deterministic so ClickHouse can reuse cached query results. Only set this when the UDF always returns the same result for the same arguments.
basic, netenable v1, v2, v3 Always null — an executable UDF has no command pool.
x > 0Respuesta
UDF version created and building.