Hello Team, I am facing some weird issue while ov...
# ingestion
a
Hello Team, I am facing some weird issue while overriding data. in v0.8.1 Tried ingesting one dataset with urn - urnlidataset:(urnlidataPlatform:kafka,SampleKafkaDataset,PROD) using pushed based architecture, everything worked fine (proper entry in es and mysql) now added one new searchable aspect in the same urn and then tried to ingest expected -> new aspect should present in mysql and es actual result -> new aspect in only in es but not in mysql Same case if we delete any aspect - expected -> deleted aspect should not be in mysql and es actual result -> removed aspect got deleted from es but still present in mysql I also verified above steps using quickstart and ingestion docker scripts Is this something expected or its an issue ?
e
Just to clarify, you created a new aspect that you added to the DatasetAspect union which has a @Searchable field right?
Can we get a bit more information here? We have never encountered this issue before and would like to better understand it.
Also how did you delete an aspect?
a
i removed that aspect from mce message for example if my entity have aspects A,B,C,D, and at first time ingestion if my mce message contains only A,B,C aspects. and next time mce message for same urn contans A,B,C,D aspects So ideally D should also have an entry in sql Same in case of removing aspect Fisrt time my mce message have asspect A,B,C and if next time if have only A,B So data of C aspect should not be in mysql Right ?
I will update the complete step to reproduce. With mce messages
e
The first should be the case. But the latter should not. For instance, ingesting one aspect doesn’t delete all other aspects.
Let me look into why the first case is happening
b
In the first case, you're righ t that ABCD should all be in there
If they are not, there is an issue here (though we haven't seen this in the wild before)
a
It went intermittent. May be i had done something wrong, i nuked containers and it worked. Sorry my bad 😶