Hooks to respond to changes in underlying data #466
Replies: 3 comments 4 replies
-
|
Just to note that you can already manually run queries against the database to clear indexes etc. You will also want to clear the caches on the server and browser (ideally not wiping it entirely but selectively flush only what is not consistent anymore). |
Beta Was this translation helpful? Give feedback.
-
|
What is the best way to run queries such that indices are reset? I think adding this is and marrying it to selections to a degree would be really nice. In practice that would allow for progressive visualization from a backend, and not needing to redraw points intermittently. |
Beta Was this translation helpful? Give feedback.
-
|
If you are updating the backing table that is being queried, you need to reset both data cube indexes and (in general) also Mosaic client stats gathered via field info. To reset the clients, you can disconnect and reconnect them all: const clients = Array.from(coordinator.clients); // extract current client set
coordinator.clear(); // disconnect clients and clear query cache
clients.forEach(client => coordinator.connect(client)); // reconnect clients, pulling new field infoFor the data cubes, all Mosaic data cube indexes include the same table prefix ( Hope that helps! If the above is not what you're asking about, please share more specifics of your use case, so we know a bit more precisely what is changing and what is not. |
|
Thanks Jeff - that makes sense. I'll give this is a whirl. |
Beta Was this translation helpful? Give feedback.
-
|
Mind sharing any code for this @willium ? We need the same feature :) |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
We @onefact need this as well @willium ! Specifically, to work with https://openvoicenetwork.org/interoperability-initiative/ and re-validation of the data every time a transcript changes (e.g. using https://github.com/ggerganov/whisper.cpp/tree/master/examples/whisper.wasm). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We currently use Mosaic's selections for interaction, but we also allow users to change the query defining the underlying view (synced with a remote data warehouse). This approach is necessary because it is infeasible for us to load all the data into the browser.
There is no clear way to trigger Mosaic to refresh the coordinator, indices, and clients.
Proposal
Short Term: Expose Endpoints for Resetting Indices:
Long Term: Support for Live Data Updates:
Stretch Goal: Support Calculating Data Differences:
Beta Was this translation helpful? Give feedback.
All reactions