yasiryagi 1b6a250bb1 Storage documentation (#850) | 2 lat temu | |
---|---|---|
.. | ||
NodeSteup | 2 lat temu | |
Sumer-Giza-migration | 2 lat temu | |
bucketFamilies | 2 lat temu | |
img | 2 lat temu | |
Distribution_Concept.md | 2 lat temu | |
README.md | 2 lat temu | |
giza1.md | 2 lat temu | |
olympia.md | 2 lat temu | |
opening-template.json | 2 lat temu | |
skillshare.md | 2 lat temu |
Image source: https://telemetry.joystream.org/#/Joystream
Reports now on Notion
With release of the Giza Testnet selected channels were migrated from Sumer previous IPFS based storage system to complete in-house hosting with storage nodes for bigger portions of assets and local distribution nodes (read first).
Details about inception of the group are reported here (@freakstatic assigned this task to @l1dev who handed it @ilich).
distributionWorkingGroup
)Query nodes accept a specific syntax.
Each query takes optional offset
and limit
arguments (up to 10k depending on setup). When pasting a query he PRETTIFY
button in graphql expands it.
query { distributionBucketOperators (limit: 2, offset: 3) { workerId } }
This returns workers 4 and 7 (see sorting below). Note that features like advanced filtering are not in scope and need to be implemented client side.
For more details start a history lesson. Do not miss to try below queries.
orderBy: [DistributionBucketOperatorOrderByInput!]
enum DistributionBucketOperatorOrderByInput {
createdAt_ASC
createdAt_DESC
updatedAt_ASC
updatedAt_DESC
deletedAt_ASC
deletedAt_DESC
distributionBucket_ASC
distributionBucket_DESC
workerId_ASC
workerId_DESC
status_ASC
status_DESC
metadata_ASC
metadata_DESC
}
query { distributionBucketFamilies { id metadata{description} buckets {id distributing acceptingNewBags operators {workerId metadata{extra nodeEndpoint nodeLocation{countryCode,coordinates{latitude longitude}}}} } } }
query distributionBuckets { distributionBuckets { id createdAt distributing acceptingNewBags operators { id workerId metadata {nodeEndpoint} } bags { id } }}
Filters need to be applied to the first (or second) level (query node doesn't support nested queries:
query { storageDataObjects(where: { id_eq: "9506" }) {
id storageBag {
id
distributionBuckets {
id operators {
metadata { nodeEndpoint } } } } } }
For curators to review new entries - the lead can assign each offset to a worker:
query getDataObjectsByVideoId { storageDataObjects(limit: 100, offset: 1) { id size deletionPrize storageBagId ipfsHash videomedia { id description licenseId license { code } media { storageBag { id owner { __typename } storageBuckets { id operatorMetadata { nodeLocation { countryCode } nodeEndpoint } createdById operatorStatus { __typename } dataObjectsSize acceptingNewBags dataObjectsCount dataObjectsSizeLimit } distributionBuckets { id bucketIndex familyId distributing createdById acceptingNewBags } } } } } }