In my pipeline, I have materialisations that I transform then have an output datasource which is associated to an object type (object storage v2). I can see the datasource is updating upon object creation but this is not feeding into the object type. I have looked at the configuration and pretty sure everything is set correctly to live update so keen to get some insight into how to resolve this. AIP Assist suggested I need to rebuild due to potential changes to the pipeline etc but unsure how to do this either.
Any tips on how to resolve this and what has caused this unsyncing of the 2 to avoid it in future?
Also, if I changed the object from storage v2 to storage v1 so I can modify the objects, will new objects coming in from the datasource still populated the object type?
Thank you!
Hey @amhall, can you please share a screenshot of the “Object Storage V2” section of the “Datasources” tab in Ontology Manager for the object that isn’t syncing?
Hi @bfrancis , there are 2 that are not syncing but have set them up identically. See below a screenshot as requested - just deployed so pipeline is showing as running.
Hi there, yes that’s correct.
Updates reliably filter: dataset A → object A → materialisation → dataset B
There is some disconnect: dataset B → dataset C → object C
Primary issue: dataset C → object C
Dataset B → dataset C is transformations in pipeline builder including a union and a join.
I currently go into app “Builds” to manually rebuild the datasets/objects in question.
Hi @bfrancis, I see now. Thank you! In the datasource tab of my object it says “up to date” which was confusing me as I thought it auto set up to live update but I need to set the build schedule for whenever my input dataset updates.