We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some c2d algorithms need infos about the filetype for working propoerly.
Call the /fileinfo endpoint of the provider (https://docs.oceanprotocol.com/developers/old-infrastructure/provider/general-endpoints#file-info) and fill the algocustomdata automatically for every compute job with the fileInfo.
/fileinfo
algocustomdata
fileInfo
The idea is the split the filename and only pass the fileExtension.
fileExtension
Example fileinfo response:
[ { "contentLength": "495331", "contentType": "application/json", "filename": "ptw-pt_1699348564105_901_copyof652.json", "index": 0, "type": "url", "valid": true } ]
Expected algocustomdata structure:
{ fileinfo: { contentLength: "495331", contentType: "application/json", fileExtension: "json" } ...otherAlgoCustomData }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Motivation / Problem
Some c2d algorithms need infos about the filetype for working propoerly.
Solution
Call the
/fileinfo
endpoint of the provider (https://docs.oceanprotocol.com/developers/old-infrastructure/provider/general-endpoints#file-info) and fill thealgocustomdata
automatically for every compute job with thefileInfo
.The idea is the split the filename and only pass the
fileExtension
.Example fileinfo response:
Expected
algocustomdata
structure:The text was updated successfully, but these errors were encountered: