Jsonl feed file not uploading via PUT method

We integrated bloomreach content search in our site. we are trying to do PUT method as part of bulk update with jsonl file which we already uploaded via sftp.

https://api-staging.connect.bloomreach.com/dataconnect/api/v1/accounts//catalogs//items

request body(application/json):

[
“content/bulk-publish/20201102-101618-catalog-full.jsonl”
]

when we call the above API with feed file path in the body it gives the jobid. When we check the job status it gives the below error.

----------------------------------job status--------------------------------------
{
“account_id”: 0000,
“attempts”: 1,
“created_at”: “1604485708488”,
“id”: “e394a1dd-95e8-4e72-acd7-39e813542029”,
“queuename”: “DataConnect.Jobs.staging”,
“started_at”: “1604485711882”,
“status”: “failed”,
“stopped_at”: “1604485711909”,
“job_type”: null,
“event_log”: {
“messages”: [
“java.util.LinkedHashMap cannot be cast to java.lang.String”
]
}
}

------------------------------------jsonl file uploaded to bloomreach------------------------------------------
[
{
“op”: “add”,
“path”: “/items/item1”,
“value”: {
“attributes”: {
“title”: “Hello Product Sheet”,
“description”: “Brief overview of product with photography and messaging.”,
“resource_path”: “34543543”,
“url”: “url”,
“thumbnail”: “thumbnail path”,
“mime_type”: “”,
“publication_date”: “2020-06-16T04:40:40.939Z”,
“xmp_designer”: [
“CSD Studio”
],
“asset_group”: “downloads”,
“dc_subject”: “null”,
“xmp_asset_type”: “assettype”
}
}
},
{
“op”: “add”,
“path”: “/items/item2”,
“value”: {
“attributes”: {
“title”: “Hello Product Sheet”,
“description”: “Brief overview of product with photography and messaging.”,
“resource_path”: “34543543”,
“url”: “url”,
“thumbnail”: “thumbnail path”,
“mime_type”: “”,
“publication_date”: “2020-06-16T04:40:40.939Z”,
“xmp_designer”: [
“CSD Studio”
],
“asset_group”: “downloads”,
“dc_subject”: “null”,
“xmp_asset_type”: “assettype”
}
}
}
]

Am I not following the feed file format, what this error means and where we can check the solution for these kind of errors.

I recommend that you contact Bloomreach Support to follow-up on this issue for the enterprise brSM Content Search service. This community support forum isn’t the best place for a customer-specific support request. I suspect that this relates to the specific attribute configuration for this catalog, so it would be best to talk with someone who can check the config.