Within Neebo, what is data caching and how can it benefit my workflow?
When downstream sources connect to Neebo to query the latest results from a Dataset, a chain of events is kicked off within Neebo to source this data. Neebo crawls through the sources that feed and build the targeted Dataset and returns a current representation of the requested data.
In order to limit the amount of hops required to access your data, the full set can be cached directly on the Neebo server providing a one stop shop for your curated Dataset.
I have pieced together a collection of data within a Neebo Dataset with the goal of populating Tableau. When refreshing the data from my Tableau Workbook I notice a degree of latency. If I were interested in reducing this query latency, I could return to Neebo, cache the Dataset, and then have direct access to the complete set from Tableau.
Another thought exercise would be if I wanted to control the state of my data when performing downstream activities against it. Let us assume the feeding streams of data within my Dataset are updated every hour. It is important that my downstream process execute against the data as it was during the 0700 hour. In this case, I would instruct Neebo to cache the data on a schedule to reflect the window I am looking to target.
In order to cache your data, please do the following:
- Open a Workbench for the Workspace containing the target Dataset
- Select the Dataset from within the Workbench
- Locate and press the "Cache Disabled" button located on the righthand side
- Configure for a single cache now, or scheduled caching in the future
In order to stop caching simply work through the above steps and disable the slide responsible for enabling caching.