-
Notifications
You must be signed in to change notification settings - Fork 0
Description
A single asset can be indexed in multiple portals and we use that index for faster loading on Portal engine/editor, and for simple search.
Today, the asset gets indexed once with it's metadata, but when the asset is updated, only the portal that it's updated on gets re-indexed with new metadata.
One idea was to keep a list of portals the asset is indexed on in the asset itself, and have that kick off updates on the portal indexes when it's updated. It could be a good stop gap until a wider indexing solution is in place, and especially that indexing is currently mostly an opt in type of behavior. But eventually anyone will be able to index any content in a portal, so we may not want to write random portals to someone's asset. Maybe a sidecar would be better to track all that?