This article is a placeholder to address open queries related to the Export V2. You will find answers to the below Questions here.
Q01. What is Export Version 2?
Q02. What are the benefits of Export Version 2?
Q03. Will this replace the existing Export Version 1?
Q04. Does this impact both Entity and Relationship exports?
Q05. Will my existing Export API endpoints continue to work?
Q06. Will my output file look the same?
Q07. Can I get a single file if I really need it?
Q08. Will I need to do anything to enable Export V2?
Q09. What happens if I use the
_dbscanendpoints for the existing export?
Q10. Do I need to tell Export to read from Primary or Secondary storage?
Q11. With multiple files, how do I know which ones are generated for this export?
Q12. Does this impact RDM exports?
What is Export Version 2?
Export Version 2 (Export V2) is the newest enhancement to Reltio’s Export Service. Export Version 2 provides you with a major performance improvement when exporting large amounts of data while also simplifying the REST API calls.
What are the benefits of Export Version 2?
The major benefits of Export Version 2 are stability and simplification. Export Version 2 is significantly more performant than the existing Export Version 1. The API interaction for Export Version 2 has also been simplified so that you no longer have to figure out how many task parts (
taskPartsCount) are needed to achieve your performance goals. Export Version 2 automatically calculates the cluster sizing based on the size of the export and the size of your tenant. This leads to a simpler, automated, and more consistent experience.
Will this replace the existing Export Version 1?
Yes! Export Version 2 will be the default export capability within Reltio Connected Customer 360 by the first week of July 2020. You will not have to make any changes to your tenant. The new Export Version 2 is being rolled out continuously and we expect to complete all customer tenant roll-out by the first week of July 2020.
Does this impact both Entity and Relationship exports?
Yes. Both entity and relationship exports will leverage Export Version 2.
Will my existing Export API endpoints continue to work?
Yes! Export Version 1 endpoints for entities and relationships will be automatically routed to Export Version 2.
Will my output file look the same?
The format of the file will be identical to the existing export, but one of the major behavior changes in this release is that export will now, by default, produce multiple output files. Previous exports (Export Version 1) consolidated all data for the export into a single file. But with Export Version 2, we leave these as separate files and compress them in order to provide more rapid access to the data. Your ETL or integration layer will need to take this into account to ensure that it processes all of the data exported from Reltio.
Note that if you want to continue to output a single file (not recommended), you must use the new Export Version 2 endpoints and pass the
skipPostprocessing parameter correctly. For more information, see Export Version 2.
Parameters specified at the end of Export Version 1 endpoints such as;
fileFormat, location of export (primary vs secondary storage), single vs multiple files and so on, will all be ignored when the request is routed automatically to Export Version 2 endpoints. These parameters will revert to their recommended values for optimal performance and stability.
Can I get a single file if I really need it?
Yes. There is an option called
skipPostprocessing for Export. By default, this parameter is set to
true and so it skips the file consolidation part of export. You can override this behavior by passing the parameter as
false, but the Reltio team would like to caution you against doing this. This will significantly impact the performance of your export and is not aligned with our Export best practices.
Will I need to do anything to enable Export V2?
No. Export Version 2 will become the default mechanism to export data. You do not have to take any action to enable Export Version 2.
What happens if I use the
_dbscan endpoints for the existing export?
These endpoints will still work, but they will redirect to Export Version 2. While these interactions will not fail, we would highly recommend that you change your interactions to make calls to the standard Export REST API.
Do I need to tell Export to read from Primary or Secondary storage?
No. Export Version 2 automatically identifies the appropriate location to read the data from based on the volume of the export and the size of your tenant. This ensures that performance remains consistent as your tenant grows, and it also simplifies the API interaction.
With multiple files, how do I know which ones are generated for this export?
Export Version 2 can produce a manifest file that outlines all of the files produced by the export. Your integration layer can leverage this manifest to make sure that you find and process all files generated by Export.
Does this impact RDM exports?
No. This change does not impact any RDM APIs.
Please sign in to leave a comment.