Users have no indication of the downloaded/imported size of chunks. Neither is there any indication of number of records and tables. So we have no feel of what size the data set are.
Suggested resolution
Get size of fetched data through API call. Size of imported data (to db) is near impossible, but a report of total records would be natural. Our specs mentinues the abstract use of 'channels' and 'attributes', but as DB tables are considered our final product, this is what sinks should report back.
Problem / Motivation
Users have no indication of the downloaded/imported size of chunks. Neither is there any indication of number of records and tables. So we have no feel of what size the data set are.
Suggested resolution
Get size of fetched data through API call. Size of imported data (to db) is near impossible, but a report of total records would be natural. Our specs mentinues the abstract use of 'channels' and 'attributes', but as DB tables are considered our final product, this is what sinks should report back.
Related to #15