On this page

    When remote documents are fetched over HTTP, a Comunica engine can cache documents to optimize future reuse. If your application works over volatile resources, then you may want to invalidate this cache, which can be done as follows:

    // Invalidate the full cache
    // Invalidate a single document

    Optionally, you can also pass the noCache: true flag to your context to invalidate the cache before query execution starts:

    const bindingsStream = await myEngine.queryBindings(`SELECT * WHERE { ?s ?p ?o }`, {
      sources: [''],
      noCache: true,