Project: datamanagement
Issue DM-5434: Ensure that new object loads are added to secondary index
L3 users might be generating new objectIds that are not in the DR Object table. If that is the case, ad-hoc L3 analysis would be triggering updates to secondary index. It is possible that L3 users will be bringing data from other surveys and might partition it DR-way and cross match. We need some mechanism to mark the secondary index dirty when something new gets added to the Object table, and trigger refresh.
Story points: 10