Avoid multiple transactions for a single request in DatasetService

Description

Currently, for example, each getDataset() request leads to at least three transactions in DatasetService: 1) to get the dataset spec 2) to get the type info, 3) to record the usage. This would better be done in a single transaction.

Release Notes

None

Activity

Show:

Ali Anwar August 3, 2018 at 6:19 PM

This isn't critical, but it would help improve performance, so we can prioritize it for 5.1.

Sreevatsan Raman August 3, 2018 at 1:23 PM

- should this be in 5.1?

 

Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Affects versions

Components

Priority

Created April 20, 2016 at 11:36 PM
Updated August 3, 2020 at 7:25 PM