cf-basic-sinks
cf-basic-sinks provides sink-step manifests and the native plugin implementation for pipeline outputs.
Steps
| Step | Category | Description |
|---|---|---|
cfsink:DataHiveParquetSinkStep |
sink | Commit a canonical Data Hive write through the injected CfDataHiveSinkContractV1 owner surface |
Published distribution name:
pip install cf-basic-sinks
Package role
cf_basic_sinks ships both the step manifest and the native plugin artifact.
- the package publishes a loadable plugin under
cf_basic_sinks/bin cfsink:DataHiveParquetSinkStepexecutes through that plugin, not an engine built-in path- backend-specific Data Hive write behavior remains owned by
cf_datahive - the plugin consumes the injected
CfDataHiveSinkContractV1surface instead of linking storage policy directly
Publishing
cf_basic_sinks is published with the dedicated Windows workflow:
- Workflow:
.github/workflows/cf_basic_sinks_windows_publish.yml - Package directory:
sandcastle/cf_basic_steps/cf_basic_sinks - PyPI tag:
cf-basic-sinks-v<version> - TestPyPI tag:
cf-basic-sinks-v<version>-test
Workflow note:
- test/build jobs publish the step manifest together with the native plugin artifact
- backend-specific native configuration and runtime staging remain owned in
sandcastle/cf_datahive/README.md
Local preflight:
powershell -ExecutionPolicy Bypass -File scripts/mimic_windows_python_publish_workflow.ps1 `
-WorkflowFile .github/workflows/cf_basic_sinks_windows_publish.yml `
-PackageDir sandcastle/cf_basic_steps/cf_basic_sinks `
-PythonExe py `
-PythonVersion 3.14
Queue a dry-run dispatch:
powershell -ExecutionPolicy Bypass -File scripts/queue_windows_python_publish_workflow.ps1 `
-WorkflowFile .github/workflows/cf_basic_sinks_windows_publish.yml `
-PackageDir sandcastle/cf_basic_steps/cf_basic_sinks `
-PublishTarget testpypi `
-Ref main `
-RequireLocalPass `
-DryRun
Metadata
Release files for cf-basic-sinks 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cf_basic_sinks-0.2.4.tar.gz | 13.7 kB | Without provenance | Details for cf_basic_sinks-0.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cf_basic_sinks-0.2.4-cp314-cp314-win_amd64.whl | CPython 3.14 | CPython 3.14 | Windows x86-64 | Details for cf_basic_sinks-0.2.4-cp314-cp314-win_amd64.whl |
Total release size: 26.2 kB
Release files / cf_basic_sinks-0.2.4.tar.gz
| Download URL | cf_basic_sinks-0.2.4.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7190c46c8f4a208b38a6e2e260c7516852772ae3628f12929171d606d2f29f48
|
|
BLAKE2b-256 checksum How to use checksums |
bb2f51281a8bc5eac7246622dc7f0e5e6b5649893d1082158dbb5d0139bfb374
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / cf_basic_sinks-0.2.4-cp314-cp314-win_amd64.whl
| Download URL | cf_basic_sinks-0.2.4-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 12.5 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f7ab0777b2fdd4ab2ff282c57199e34444c75cebb4facc6cd37b39e39d2c8b0b
|
|
BLAKE2b-256 checksum How to use checksums |
2b00747c8fc7ab4787254442cffcc392be4d09b3e219985d823480eff77ec3e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for cf-basic-sinks 0.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.