Changes to Raw Data Export on June 20th

Unity Services
,
1

We are planning to make some infrastructure changes to our Raw Data Export service and we want to get feedback on how these changes might affect our customers.

  • Currently, if a field does not contain any data, we simply add ‘null’ or ‘false’ to the field. We are proposing that for JSON files, we will simply not include the field if it does not contain any data. The benefit of this change is a reduction to JSON file size. (This change will not affect TSV files).
  • We are changing the expiration date of Raw Data Export files from 30 days to 14 days. (i.e. Once you make a request, the resulting file will be available to download for 14 days. To access the data after 14 days has elapsed, you can make a new request.)

These changes are scheduled to go into effect on June 20th. This is part of larger changes we are planning to increase the long term sustainability of our service.

If this will majorly impact your workflow around Raw Data Export, please post here and let us know.

~~ Update ~~

Edit: The changes to Raw Data Export were made this week, however, we ended up not modifying much about the json files, including empty fields. The only exception is nested fields. This only happens with transaction event and the receipt field (which would contain an empty signature.)

2

Would it be possible to get a test data set with the proposed changes (dropped fields) above to run through our analytics data processing pipeline? This would help us estimate how much it will impact our pipeline with more accuracy.

3

@executor12 It might make more sense for you to take one of your existing data exports and remove those elements that have null values. This would be closer to what you would expect to see, rather than us randomly removing some fields in test data.