Dbnd

Latest version: v1.0.27.2

Safety actively analyzes 681775 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 6

0.53.0

Breaking changes
* \1200944564541400: The final state of sub-pipeline tasks that have failed child tasks is now called "Failed" instead of "Upstream Failed".

New features
* \1200875727993229: Observe metric trends over time: missing charts, run state charts, state metrics charts, schema change metric trends, etc.

Improvements
* \1201110693029241: Operations merged from the SDK and BigQuery logged with `log_dataset_op` are now recognized and displayed accordingly (with BigQuery ID) in the Dataset Operations tab, including with stateful issues.
* \1201314083672982: Resolved notifications are no longer the default configuration for Slack receivers.
* \1201141157594482: Alert dialog loads promptly and displays the correct state.
* \1201257264431636: Added support for tracking specific DAGs.
* \1201226401826259: Syncer memory guard limit is now configurable.
* \1201266020003308: Pipelines with zero associated runs are hidden in the Databand UI.
* \1201260807813998: Resolved notifications are now correctly delivered to the update/validate receivers.
* \1201036807083630: In the Alert Definitions' editor, individual tasks can be addressed when DAG has multiple tasks with the same name.
* \1200991140831460: `COPY INTO` queries are now supported for Snowflake.
* \1201154986480578: Operations section on the Datasets tab notifies of unusual activity in an operation (schema change or failed operation).
* \1201080247459590: Operations are now tracked with BigQuery even when no SDK is installed.
* \1201080247459582: Dataset Overview section combines the data from SDK and from BigQuery.

Bug fixes
* \1201160985639176: Solved a bug that emerged when deleting a DAG.

0.50.0

New features
* \1200764884086970: Added SDK Client for Metadata (basic access API endpoint for collecting all errors in a Run).

Improvements
* \1201013784336315: Improved behavior of Reset Selection in Affected Datasets.
* \1200766175220432: Now you can create alerts directly from the redesigned Metrics tab.

Bug fixes
* \1200964944935744: Each step on the X-axis in Dataset Overview now equals 24 hours from the previous point.
* \1200964944935725: "Reported from" and "Dataset Type" columns in the Datasets tab follow the same logic as elsewhere in the Databand UI.

0.49.0

New features
* \1200638623009192: Datasets can be archived now.
* \1200713291030116: Added empty state clickable component.
* \1200920981691825: Default operation is pre-selected on the Alert definition screen.

Improvements
* \1200948790296167: Dropped all `python 2.7` support.
* \1200766175220434: All alerted metrics that are being reported are now visible.
* \1200892336582865: Reviewed documentation links in the code.

0.48.0

Improvements

- \1200876485130367: Drop py27 support for dbnd-examples.
- \1200854192669862: Drop support for tensorflow <2.4 and py27 in dbnd-tensorflow plugin.

New features

- \1200463416979272: Run metrics in the list of metrics are now selected by default and are available from the filters in the Databand UI.
- \1200794953399592: A new look for the Dataset page.
- \1200667723456248: Metrics page added - see all the metrics, alerts, and trends for numeric values in one place (coming in a later minor release).​

Improvements

- \1200876485130367: Dropped py27 support for dbnd-examples.
- \1200854192669862: Dropped support for tensorflow <2.4 and py27 in dbnd-tensorflow plugin.
- \1200495012906365: Defined and implemented Network Policy to isolate workloads in namespaces.
- \1200845451577692: Delete alert definitions in bulk using the “Delete” button.
- \1200791698233717: Trigger value of Missing Operation alert now reflects the total number of missing operations in the run.
- \1200667315624593: Tooltip in schema change now opens on click.

Bug fixes

- \1200587432732541: Text in the UI now aligns to the left after a line break.
- \1200785050007987: Fixed a bug where the “last modified” field returned an empty value.
- \1200847984199269: Fixed a “type change” reporting bug in schema change alerts.

0.47.0

New features

- \1200526324086051: BigQuery connector - Databand can now sync with your BigQuery tables.
- \1200667621364917: Databand Dashboard can now be shared and will include filters, metrics, and aggregations.

Improvements

- \1200700177752978: Airflow Monitor V1 is deprecated.
- \1200618993918094: Improved visibility of missing operations in Affected Datasets.
- \1200721895327001: Updated the UI on the Integrations page.
- \1200624166545000: Full table path in the Affected Datasets tab is now a tooltip.

Bug fixes

- \1200654355859365: Source and project names are displayed correctly.
- \1200670021315930: Missing operations are now properly represented in the History Trend chart in the Affected Datasets tab.
- \1200655482328132: Fixed the dropdown table column in the 'Add new alert' page.

0.46.0

New features

- \1200619480835694: Pipeline and run lists optimized for tracking.
- \1200597628980930: Now you can choose whether to have alerts fire on historical runs by editing alert definitions.
- \1200347108016370: Range alerts added. Now it’s possible to add an alert if the metric's value is in a predefined range or out of range.
- \1200700419038963: New schema Alert flow changes in Affected Datasets: schema changes in a data operation are now shown in the Affected Datasets screen. Now you'll know when a column is added, removed, or when its type changes. Some minor cosmetic changes in the UI were also implemented.

Improvements

- \1200610543227298: Simplified usage of `in_cluster` in cases where `in_cluster` is None.

Bug fixes

- \1200629604891227: Run view performance improvements.

Page 1 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.