-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Port boostd-data #24
Comments
As far as I understood from my research, this task is somewhat blocked by #25 because the main entry point mechanism — importing files — requires files to be in the CAR format, as made evident in the This goes against the UML diagram in the Data Storage Workflow but the code seems to imply that it is not the Lotus daemon doing the conversion. While we don't need the creation of CAR files to be implemented to unblock this task, we do need the reader. Given that the upload is always done with CAR files, we can also consider how much we need to be able to write the CAR files ourselves. In other words, if we can get away with just using another tool to create the CAR files from arbitrary data. |
What I suggested during the meeting was to start scaffolding the interface serving the boostd-data client. A component that will be similar for use is the |
Created a separate issue #41 for that. |
@serg-temchenko EDIT(@jmg-duarte): we've decided to close this for now and use the current LID indexing as a library rather than a service for the time being. |
As described in the
piecestore
andpolka-index
sections of our guidelines, we need to port theboostd-data
functionality since it contains LID, which is a replacement for the DAGstore component.Related issues:
RPC implementation for the storage provider #52Is not a part of the scope of this issue.The text was updated successfully, but these errors were encountered: