Graphql data type

[alexcos20]

So far, we supported 'url ' and 'ipfs' types for data storage Since https://github.com/oceanprotocol/provider/pull/537, there is a new one, called 'graphql'. This allows publishers to publish datasets and use graphql querys as datasource.

Format for graphql type is as follows:

• type: graphql
• url : server endpoint url
• query: the actual query to be executed

Example:

[
        {
            "type": "graphql",
            "url": "http://172.15.0.15:8000/subgraphs/name/oceanprotocol/ocean-subgraph",
            "query": """
                    query{
                        nfts(orderBy: createdTimestamp,orderDirection:desc){
                            id
                            symbol
                            createdTimestamp
                        }
                    }
                    """,
        }
    ]

Sometimes, it's not enough to have one simple query, you need some input from user. This can be achieved with something like:

• prepare asset with graphql storage

  [
      {
          "type": "graphql",
          "url": "http://172.15.0.15:8000/subgraphs/name/oceanprotocol/ocean-subgraph",
          "query": """
                  query nfts($nftAddress: String){
                      nfts(where: {id:$nftAddress},orderBy: createdTimestamp,orderDirection:desc){
                          id
                          symbol
                          createdTimestamp
                      }
                  }
                  """,
      }
  ]

  as you can see, there is a query parameter called nftAddress.

• add consumerParameters to ddo.service as

  [
          {
              "name": "nftAddress",
              "type": "text",
              "label": "nftAddress",
              "required": True,
              "description": "Nft to search for",
          }
      ]

When downloading the dataset, user has to pass userdata to provider request

[LoznianuAnamaria]

@alexcos20 Do we need to do something else on this or can we close it?