Identity Service Flow Run Delay 'Datalake_to_UIS_Flow' has been processing for more than expected time.
What are the factors effecting this processing time? Any help would be greatly appreciated.
表示
返信
いいね!の合計
Dear @Indra ,
Sorry, I am not sure what is 'Datalake_to_UIS_Flow'. Can you explain the same so that I can help you?
Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics
Yes
表示
返信
いいね!の合計
Unified Identity Store
表示
返信
いいね!の合計
Please refer to the following digram which outlines the latency through each component.
Out of the box job runs every day to stitch Identities..
"You can use Identity Service to link identities and piece together a complete picture of your customer that might otherwise be scattered across different systems."
Dear @Indra ,
For streaming data, the Identity Store should update real-time/near real-time since the data is streamed directly into the Real-time Customer Profile (Profile Store).
For batch data, the Identity Store should update every day or during the batch ingestion timing because batch data is not part of the pipeline (should be updated from Data Lake).
@brekrut Correct me if there is any other understanding.
Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics
@Indra adding to other inputs suggest to consider below
- what is data size if it is large perform parallel process or incremental processing do not ingest all in one go
- revisit your transformation logic if any on the ingestion
@Indra Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!
表示
返信
いいね!の合計