Current Known Issues
This article contains information on any current known issues that might affect your use of our product.
Known System Issues for Safe Haven
There are no current known issues for Safe Haven.
The past issues listed below have been resolved.
PySpark Upgrade Code Changes
Note
This issue is not a Safe Haven Analytics Environment product issue and has more to do with how to use third-party PySpark packages. If you have not upgraded your tools, it may still be an issue.
If you are using the following package and its function calls in Analytics Environment, update your code to be compatible with the new PySpark 2.4.8:
Python Package | From | To |
|---|---|---|
pyspark.ml.fpm.prefixSpan | prefixSpan.getMaxLocalProjDBSize() | prefixSpan.getOrDefault("maxLocalProjDBSize") |
For more details, see the Apache PySpark Upgrade Guide.
Apache Log4j Vulnerability
The Apache log4j utility security vulnerability is resolved.
Tableau Log4j Updates Resolved (2022-01-06)
For EU Analytics Environment users: Tableau Log4j patching was performed on January 6, 2022, from 6-9 PM UTC.
For U.S. Tableau users: Log4j patching was performed on January 3, 2022.
File Processing Delays for File-Based Recognition Workflow Files Resolved (9/2/21)
The past issues listed below have been resolved.
File Processing Delays for File-Based Recognition Workflow Files Resolved (9/2/21)
As of August 20, the previous processing delays for File-Based Recognition (FBR) workflows have been fully resolved.
Please note that there is no need for you to re-upload any files or take any further actions.
We apologize for any inconvenience the delay may have caused. Based on a post-mortem analysis conducted by our Product and Engineering teams, they concluded the following:
On August 3 and 4, the FBR pipeline received a sudden, unexpected volume of files that overwhelmed our backend file processing, resulting in processing delays. While FBR has successfully managed all previous instances of large file influxes, this sudden volume was so large that it resulted in a temporary system processing failure.
Our Engineering teams immediately adjusted and monitored processing resource allocations to resolve the issue. As the issue persisted, Engineering teams moved processing to a secondary, redundant system.
On August 10, files began processing through the alternate pipeline successfully, and shared multiple broad communications to impacted customers.
By August 17, all pending files had been processed, with the exception of a few files that leverage features of the main file processing system that were not available on the secondary system; these files completed successfully through the main system on August 19.
Our Engineering teams have added multiple new control points throughout the FBR pipeline to better allocate resources for processing and are preparing to enable additional pipelines to successfully address higher volumes.
For any questions or requests regarding these file processing delays, create a case in the LiveRamp Community portal .