Khoros Atlas Logo

%3CLINGO-SUB%20id%3D%22lingo-sub-278375%22%20slang%3D%22en-US%22%3EBulk%20Data%20API%20and%20Document%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278375%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20bulk%20data%20api%20users%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20using%20the%20bulk%20data%20api%20and%20in%20thread%20about%20fields%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.lithium.com%2Ft5%2FDevelopers-Discussion%2FBulk-Data-API-Too-Many-Fields-Error%2Fm-p%2F218114%23M10125%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcommunity.lithium.com%2Ft5%2FDevelopers-Discussion%2FBulk-Data-API-Too-Many-Fields-Error%2Fm-p%2F218114%23M10125%3C%2FA%3E%2C%20the%20PM%20recommended%26nbsp%3Bto%20use%20document%20ID%20as%20the%20key%20to%20match%20up%20data%20with%20updates.%20Our%20BI%20guy%20is%20wondering%20if%20others%20are%20using%20the%20document%20ID%20with%20success%20to%20merge%20data%20with%20bulk%20data%20updates%20(adds%20columns%2C%20backfills%20data).%20From%20what%20I%20understand%20the%20document.id%20as%20it%20not%20as%20efficient%20as%20a%20unique%20number%20or%20unique%20date.%20I%20asked%20about%20using%20the%20create%20date%2C%20but%20the%20BI%20concern%20is%20the%26nbsp%3Bunix%20datetime%20has%20the%20potential%20for%20the%20same%20date%2C%20and%20instead%20would%20like%20a%20unique%20date%20on%20database%20insert%20or%20a%20number.%20Are%20other%20bulk%20data%20api%20users%20successfully%20using%20document.id%20across%20millions%20of%20recording%20when%20updating%20that%20data%20with%20inserts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Valued Contributor
Valued Contributor

Bulk Data API and Document ID

Hi bulk data api users, 

 

We are using the bulk data api and in thread about fields, https://community.lithium.com/t5/Developers-Discussion/Bulk-Data-API-Too-Many-Fields-Error/m-p/21811..., the PM recommended to use document ID as the key to match up data with updates. Our BI guy is wondering if others are using the document ID with success to merge data with bulk data updates (adds columns, backfills data). From what I understand the document.id as it not as efficient as a unique number or unique date. I asked about using the create date, but the BI concern is the unix datetime has the potential for the same date, and instead would like a unique date on database insert or a number. Are other bulk data api users successfully using document.id across millions of recording when updating that data with inserts?

Tags (1)
0 Kudos