Is there a way to view ontology edits separately from the backing datasets in OSv2?

Hey all,

Is there a way to view what ontology edits have been made to a specific object versus the backing dataset? I’d like to debug why certain changes I’m making to the backing dataset are not reflected in the materialized object. I assume it’s because at some point those properties were edited but it’d be nice to know this for a fact.

I’d almost like a “git diff” view that makes it easy to see just the changes (ontology edits) that have been made directly in OSv2, instead of seeing the sum of backing dataset + changes.

Unfortunately I do not create history/log objects for the object types I’m interested in.

I’m sure I could build out a one-off pipeline to diff the backing datasets and the materialized object dataset but this is a very expensive way to try and reverse engineer the state that I assume is already persisted in OSv2 somewhere. I believe there would also be certain limitations that approach would hit, such as it being impossible to tell if an object was constructed initially through a backing dataset or through an ontology edit.

The main way to enable this workflow in OSv2 is by enabling history tracking:
https://www.palantir.com/docs/foundry/object-edits/user-edit-history/

Since you mention that you didn’t configure history, your options are likely:

  • going through the latest transactions of the materialization dataset to check what changes were appended to it
  • diffing the dataset and the materialization

By looking through the edits resolution mechanism https://www.palantir.com/docs/foundry/object-edits/how-edits-applied/#strategy-1-apply-user-edits-default it should be possible to piece together whether an object was created via an edit or through the pipeline (e.g. if an object doesn’t in the backing dataset but still exists in the materialization, then it was likely created via a user edit because it would otherwise also disappear from the materialization)

Hi Simon maybe you would like to says “if an object does not exist via the pipeline …” ? It would make more sens.

1 Like

Ah yes, thanks! I’ve made edit to correct this

Ack, thank you. Sounds like the answer is that I should be turning on user edit history early and often.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.