AEP schema reusing and entity relationship | Community
Skip to main content
New Participant
March 14, 2022
Solved

AEP schema reusing and entity relationship

  • March 14, 2022
  • 2 replies
  • 1465 views

AEP document says one schema can be reused by multiple datasets. It also says we can define lookup relationship between schemas by setting a lookup field in the source schema to refer to destination schema's primary identity field.

My question is when the destination schema is reused by two datasets, which dataset the source schema's lookup field will refer to?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kishore_Reddy

Hey @kevinclcn 

Hope you are doing well!

In my opinion, re-using schemas is all about enabling modular-data-infrastructure. So, if you have created one schema and used it in two data sets. And say that you have enabled batch ingestion to both data sets. Then, when a data ingestion occurs, Adobe would utilize same schema for both the data sets separately while receiving and storing the data.

 

So, there shouldn't be any conflict in looking up the fields or fields groups while ingesting data, as long as schema is intact and source connection is unchanged!

 

Best,

Kishore

2 replies

Kishore_Reddy
Kishore_ReddyAccepted solution
New Participant
March 17, 2022

Hey @kevinclcn 

Hope you are doing well!

In my opinion, re-using schemas is all about enabling modular-data-infrastructure. So, if you have created one schema and used it in two data sets. And say that you have enabled batch ingestion to both data sets. Then, when a data ingestion occurs, Adobe would utilize same schema for both the data sets separately while receiving and storing the data.

 

So, there shouldn't be any conflict in looking up the fields or fields groups while ingesting data, as long as schema is intact and source connection is unchanged!

 

Best,

Kishore

Employee
March 16, 2022

@kevinclcn Could you please elaborate a little more on your usecase.

 

Regards,

Karan