US 12,339,869 B2
Migration and validation of data from tabular structures to non-relational data stores
Jeremy Green, Manassas, VA (US); Jee Won Kang, Reston, VA (US); Christopher Zimmerman, Rochester, NY (US); and Brady Murphy, Burke, VA (US)
Assigned to Capital One Services, LLC, McLean, VA (US)
Filed by Capital One Services, LLC, McLean, VA (US)
Filed on Aug. 19, 2022, as Appl. No. 17/820,970.
Prior Publication US 2024/0061857 A1, Feb. 22, 2024
Int. Cl. G06F 16/25 (2019.01); G06F 16/21 (2019.01); G06F 16/22 (2019.01)
CPC G06F 16/258 (2019.01) [G06F 16/214 (2019.01); G06F 16/2282 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A system, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
receive a command to initiate transfer from a relational data store to a non-relational data store;
transmit, to an application programming interface (API) in communication with the relational data store and the non-relational data store, a request for metadata associated with a tabular data structure in the relational data store, wherein the command includes an override header indicating that the command is associated with the relational data store;
receive, from the relational data store via the API and based on transmitting the request for the metadata, an asset identifier associated with a metadata item;
initiate, based on receiving the asset identifier, a state machine, associated with migration of the relational data store to the non-relational data store, comprising a plurality of processing threads and a plurality of states, wherein the metadata item is associated with a particular processing thread of the plurality of processing threads and a corresponding state of the plurality of states;
execute, according to the particular processing thread, to advance the state of the metadata item, a transformation on the metadata to generate, based on the metadata, adapted metadata for the non-relational data store,
wherein the transformation on the metadata is executed by converting the metadata from a first format to a second format;
transmit, to the API and according to the particular processing thread to advance the state of the metadata item, a request for storing the adapted metadata in the non-relational data store;
transmit, to the API and according to the particular processing thread to advance the state of the metadata item, a request for particular metadata associated with the non-relational data store;
receive, from the non-relational data store via the API and based on the request for the particular metadata, the particular metadata;
verify, according to the particular processing thread to advance the state of the metadata item, the particular metadata against the adapted metadata by verifying that data included in each field of the adapted metadata matches data is included in a corresponding field of the particular metadata;
determine, based on verifying the particular metadata against the adapted metadata, that there is an error with specific metadata of the particular metadata;
execute, based on determining that there is the error with the specific metadata and by converting the specific metadata from the first format to the second format, a transformation on the specific metadata to generate specific adapted metadata for the non-relational data store; and
transmit, to the API, a request for storing the specific adapted metadata in the non-relational data store.