Symptom
When deploying Task chain, error occurs:
An internal error occurred
Status 400 is not accepted
Environment
SAP Datasphere
Reproducing the Issue
The error occurs when the space, in which the remote table resides, has a large number of remote tables
Cause
The URL sent to repository to get data is too long.
error: [REPO_HTTP_REMOTE_CLIENT] <XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX> Repository http request failed. Error: Deepsea response status 400 is not accepted. Reponse body: <html><body><h1>400 Bad request</h1> Your browser sent an invalid request. </body></html> .; Request: GET: /repository/objects?folderIds=0D9CAB405D200F1C1800D28269EA6F30&details=id%2Cspace_id%2CremoteSourceName%2CtypeId%2Cname%2CcredentialMode%2Ccsn&filters...&inSpaceManagement=true&kinds=repository.remote.; Response:400 Bad request. Info: {"deepsea-http-client":null,"deepsea-http-client-catch":null
/dwaas-core/tf/<space_name>/<remote_table_name>/chainable?applicationId=REMOTE_TABLES
Resolution
The fix is planned to be included in wave 2023.11, see SAP Note 2984828 - SAP Datasphere Release & Delivery Schedule
The workaround is to replicate the remote table separately.
Keywords
dwc, data warehouse cloud, taskchain, deploy, import, add , KBA , DS-DI-RT , Remote Tables , Problem