You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@avdata99 Just a heads up that this was originally implemented to increase performance with a large number of datasets. When you reach the dataset count that data.gov has, the default CKAN model wasn't designed to cope with it, specially with large number of datasets with many extras like the harvested ones in data.gov. This was done back in the CKAN 2.3 days so a lot of things might have changed in the meantime but just flagging that you should check the performance impact of removing this. IIRC this wiki page had details about it.
Thanks @amercader.
I couldn't understand why this was done and now I understand. We are going to have to make sure that this change does not have a bigger impact than expected.
Each time we save a new dataset we group almost any extras in a special extra called
extras_rollup
(we do this for CKAN 2.3 and for CKAN 2.8).We need to stop doing this and save extras as regular extras.
This will require:
spatial
extra. We already have Multi#332 for this.The text was updated successfully, but these errors were encountered: