How do we access Raw Data using Data Access API - for other internal ML applications? | Community
Skip to main content
Adobe Employee
October 7, 2023
Solved

How do we access Raw Data using Data Access API - for other internal ML applications?

  • October 7, 2023
  • 1 reply
  • 1161 views

How do we access Raw Data/ Data feeds (not XDM) using Data Access API - for other internal ML applications?

The diagram clearly speaks about Raw Data access - https://experienceleague.adobe.com/docs/experience-platform/data-access/home.html?lang=en

But couldn't find any links to access raw data feeds (previously setup used via Adobe Analytics UI) while using Data streams and accessing data via datalake.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arpan-garg

Hi @akonch1 - These are the formats in which data can we exported

  • When exporting compressed JSON files, the exported file format is json.gz
  • When exporting compressed parquet files, the exported file format is gz.parquet

Parquet can easily be understood by datalake and should not be an issue.

1 reply

arpan-garg
Community Advisor
Community Advisor
October 8, 2023

Hi @akonch1 - If you want to export raw data to datalake , why don't you use the export dataset functionality which was introduced recently 

https://experienceleague.adobe.com/docs/experience-platform/destinations/ui/activate/export-datasets.html?lang=en 

 

Hope this helps,

Arpan

akonch1Adobe EmployeeAuthor
Adobe Employee
October 9, 2023

Thank you, Arpan.

I'm not sure but when we export from a dataset, will the data format exported be in XDM or raw gzip format as before?

 

 

arpan-garg
Community Advisor
arpan-gargCommunity AdvisorAccepted solution
Community Advisor
October 9, 2023

Hi @akonch1 - These are the formats in which data can we exported

  • When exporting compressed JSON files, the exported file format is json.gz
  • When exporting compressed parquet files, the exported file format is gz.parquet

Parquet can easily be understood by datalake and should not be an issue.