You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@opendal.apache.org by "benjaminpreiss (via GitHub)" <gi...@apache.org> on 2025/03/31 23:02:05 UTC
[I] new feature: irys.xyz service [opendal]
benjaminpreiss opened a new issue, #5920:
URL: https://github.com/apache/opendal/issues/5920
### Feature Description
An irys.xyz storage service for opendal.
### Problem and Solution
I understand opendal is a path based storage interface. The functions `read(path)` and `write(path, content)` have to be implemented.
After some research, it seems this is possible by doing 2 things:
1. Building a locally running irys TS SDK wrapper that exposes all necessary functions (upload, download, etc.) via an API
2. Writing the opendal irys service that utilizes this API to interact with Irys
#### Requirements check
- Irys offers the ability to set tags on an uploaded chunk: https://docs.irys.xyz/build/d/sdk/upload/uploadFile
- As all data on irys is public, one can use the graphQL interface to query chunks by the path tag: https://docs.irys.xyz/build/d/graphql#query-arguments
- Deletion does not exist on irys. So the `delete(path)` operation does not carry out any action. Instead, data just expires after the intended lifetime of the data is reached. Note - currently, the irys sdk only offers permanent / perpetual (forever) storage. So deletion is indeed not possible.
#### Path mapping in Irys
As briefly mentioned before, paths can be stored alongside chunks by setting them as tags.
So, how does one deal with updates to file paths? That would mean multiple chunks would exist with the same path tag.
It seems, that each upload on irys has a timestamp associated with it, by which the results could be sorted: https://docs.irys.xyz/build/d/graphql#results-fields
I am willing to implement this entirely on my own to not burden the opendal team and giving this feature request a fighting chance.
### Additional Context
_No response_
### Are you willing to contribute to the development of this feature?
- [x] Yes, I am willing to contribute to the development of this feature.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] new feature: irys.xyz service [opendal]
Posted by "Xuanwo (via GitHub)" <gi...@apache.org>.
Xuanwo commented on issue #5920:
URL: https://github.com/apache/opendal/issues/5920#issuecomment-2780181702
> 1. Building a locally running irys TS SDK wrapper that exposes all necessary functions (upload, download, etc.) via an API
Hi, one important requirement for OpenDAL is that it must interact with an **open** API—meaning the API must be publicly recognized and officially supported by the company or the upstream provider. In other words, unless the upstream explicitly accepts the API as part of its official interface, I don't believe OpenDAL can support it.
Sorry for this rule, but I hope you understand the reasoning: anyone can design their own API, and OpenDAL doesn't want to act as a judge in such cases.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] new feature: irys.xyz service [opendal]
Posted by "benjaminpreiss (via GitHub)" <gi...@apache.org>.
benjaminpreiss commented on issue #5920:
URL: https://github.com/apache/opendal/issues/5920#issuecomment-2780295413
Are dependencies in the source code to sdks okey then? Irys has a rust sdk, but I didn't know whether it's alright to include it in the source code.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org