Ability to preserve source database keys for writing data back to the source databse

[ArthurKeen]

The ArangoDB PyG adapter version 1.1 has the ability to preserve source database keys, so that when writing back to the source database, the original keys are used. The adbpyg adapter generates identifiers appropriate to PyG and it is important not to use the :PyG id's as keys when writing back. FastGraphML has the ability to write embeddings back to the source database into user defined collections whose keys should correspond to the source collections the embeddings were derived from. FastGraphML needs to apply the source key dictionary resulting from using the preserve_keys option to the embeddings when writing back to the database, so that the resultant stored embeddings have the correct keys corresponding corresponding to the collection that the embeddings reference. FastGraphML should consider preserving keys by default.

[cw00dw0rd]

@sachinsharma9780 has this been resolved?

[sachinsharma9780]

@cw00dw0rd will be added in future iteration since it require additions in PyG Adapter