Besides performance, there aren’t any user-visible functional changes when pinning content. That said, testing should cover invalid configurations (e.g. pinning a table that isn’t tiered), and pinning a table with more content than will fit in the cache. Eventually there will be scenarios combining pinning with persistent and excluded content, which will be covered as part of those milestones.

Please include enough context to make triage and story pointing simple. We have a guide about what to include here, tl;dr include:

• A summary from the consumers' point of view,
• A definition of done,
• The reproducing steps, and
• Links to other relevant tickets/resources.