This article lists maintenance fixes and updates for supported DataForge versions.
DataForge Version 8.1
- November 18, 2024
- Core csv parse breaks when column names contain invalid sql characters
- Spark ingestion fails when column names contain spaces or invalid SQL scharacters
- VOID type generates ingestion error in custom ingest
- November 4, 2024
- Enable postgres output connection
- November 1, 2024
- Inactive variables are still exported in project export causing issues on import
- Output marks all source channels failed if one has zero record inputs because there is no hub table
- New custom connection does not default private parameters to {}
- Cleanup not always deleting failed ingestions per Failed Ingestions Input Period parameter
- Connection does not load on source settings page without refreshing screen
- Delta output from custom_refresh source fails when source has 0 record inputs
- Required_hub_table_ids need to include hub tables referenced by sub-source query
- S3 connection ingestion attempting to use unity external location rather than saved IAM access keys
- Changing relation template expression triggers recalculate of inactive keep current rules using relation
- Refresh Data is failing from Full to Key to Full
- Pull Now doesn't show on Inputs page - processing type is NULL
- Job Run ID filter doesn't work on Job Runs page because of integer overflow in function
- Spark file sources and outputs (CSV,Text,Json) use bad line separator
- Full source with single input fails on attribute recalculation
- Add named parameters when using connection string with Agent
- Workflow waits don't work for active parse, sparky_parse and custom_parse processes
- Stream processing type should not be available on the sub-sources settings
- Refix deployment endless loop
- Invalid Databricks token cause API to stop working
- Renaming new rule may cause hub table drop
- Invalid raw attribute datatype_schema for sparky ingestion for short & byte datatypes
Updated