Hello all. We’re experiencing a bug with the GoodData Python SDK. The

sdk.catalog_data_source.scan_data_source

method is throwing a 500 Internal Server Error, and the corresponding GoodData API request

https://{{domain}}/api/v1/actions/dataSources/{{data_source_id}}/scan

is also throwing the same error. I have evaluated this against one of our non-prod GoodData instances, for an available data_source (i.e. configured correctly with the connection tested). Using the latest version of the Python SDK (v1.34) and with a properly configured sdk, the following:

sdk.catalog_data_source.scan_data_source(
        data_source_id,
        CatalogScanModelRequest(scan_tables=False, scan_views=True),
    )

returns

ServiceException: Status Code: 500
Reason: Internal Server Error
HTTP response headers: HTTPHeaderDict({'Date': 'Wed, 15 Jan 2025 10:09:02 GMT', 'Content-Type': 'application/problem+json', 'Content-Length': '140', 'Connection': 'keep-alive', 'Vary': 'Origin, Access-Control-Request-Method, Access-Control-Request-Headers', 'X-GDC-TRACE-ID': 'fe45d4f454e1d254cb5909d6067df789', 'Cache-Control': 'no-cache, no-store, max-age=0, must-revalidate', 'Pragma': 'no-cache', 'Expires': '0', 'X-Content-Type-Options': 'nosniff', 'Strict-Transport-Security': 'max-age=63072000; includeSubDomains', 'X-XSS-Protection': '0', 'Referrer-Policy': 'no-referrer', 'set-cookie': 'SPRING_REDIRECT_URI=; Max-Age=0; Expires=Wed, 15 Jan 2025 10:09:02 GMT; Path=/; Secure; HTTPOnly; SameSite=None'})
HTTP response body: {"detail":"Server-side problem. Contact support.","status":500,"title":"Internal Server Error","traceId":"fe45d4f454e1d254cb5909d6067df789"}

Similarly, an authenticated POST to

https://{{domain}}/api/v1/actions/dataSources/{{data_source_id}}/scan

for the same data source and GD instance with this body:

{
  "scanTables": false,
  "scanViews": true,
  "separator": "__"
}

returns

{
  "detail": "Server-side problem. Contact support.",
  "status": 500,
  "title": "Internal Server Error",
  "traceId": "b66bf8b942259a5d22d4dc6807590d2a"
}

This is a critical issue for us - could GoodData support and engineering please look into this?

Hello! I’m sorry to hear about this issues. May I know if you have made any changes/updates on your redshift?

No we haven’t made any Redshift changes, and testing the data source connection in the GoodData UI returns successful.

Thanks for the confirmation Eoghan, we are currently checking with engineers

Thank you Daniela

We have found the issue, it is related to Redshift. And as we speak, we are about to fix it. I’ll let you know once the fix is in Production.

Great news, thank you all!

Hi @Eoghan Bonass, our engineers are still working on deploying the fix - we’ll keep you updated as we learn more!

Thank you Francisco!

Hi @Eoghan Bonass, the fix should be released now - are you still seeing the datasource scan errors?

Hello Francisco. The datasource scan errors look to be fixed - I’m verifying for each of our ETL runs that had failed, and so far all look to be corrected. If I notice any further related problems I’ll let you know. Thank you all for your help and the quick action to correct the issue!