Brunno Araujo
09/25/2023, 9:00 PM{
"title": "Bad Request",
"status": 400,
"detail": "A result cache error has occurred during the calculation of the result",
"resultId": "bcd191c43fb797451bed42c1a68bc07b3f6bba2d",
"reason": "The table path must be non-empty.",
"traceId": "b44bc817cca26a13b5a6c885cc599b61"
}
Michael Ullock
09/25/2023, 9:33 PMJakub Sterba
09/26/2023, 4:37 AMCam Findlay
09/29/2023, 3:49 AMCam Findlay
09/29/2023, 3:57 AMPavel Cerny
09/29/2023, 10:50 AMdataSourceTableId.path
in LDM definition of dataset. Starting by 11.09.2023 LDM models require this key to compute report.
Based on logs on our side, you are using python SDK in version 1.4.0 to maintain workspace definitions. Unfortunately, support for above mentioned key was introduced in version 1.5.0 of python SDK. With 1.4.0 python SDK will not store key dataSourceTableId.path
into your LDM definition. It disappears. As the result, reports computation fails.
When you upgrade to 1.5.0 or newer, dataSourceTableId.path
is going to be handled correctly. Be aware that your current LDM models do not have dataSourceTableId.path
so you need to add it first into LDM definition, e.g. by python SDK or in LDM modeler. The key is list of strings pointing to the table in database. For example ["schema_name", "table1"]
says that dataset is backed by table schema_name.table1
in given data source.
cc: @Cam FindlayCam Findlay
10/02/2023, 11:10 PMPavel Cerny
10/03/2023, 7:39 AMpath
key already, you need to set it back. Plus you need to upgrade pySDK at least to version 1.5.0 to make sure it will not be removed again by pySDK operations.Brunno Araujo
10/03/2023, 3:11 PM