[ckan-dev] What's the future of DataPusher?

Tue Jan 30 07:32:09 UTC 2018

Hey Florian,

I have used Datastore a lot without the datapusher because it gives me a
nice HTTP API over the data table entries.

Although the new feature of correcting column types via the data dictionary
was in my opinion a major improvement, it's also a bit cumbersome and feels
like a plaster.

Best,
Matt

On 30 January 2018 at 08:28, <Florian.Brucker at it.karlsruhe.de> wrote:

> Hi everyone,
>
> after running into yet another problem* with DataPusher I was wondering if
> there are any plans to replace it with a more modern solution? In my
> experience, one reason why working with DataPusher is often cumbersome is
> its implementation as a separate service. As far as I understand, the same
> functionality could nowadays be implemented easily as a CKAN extension
> based on background jobs. In my opinion, this functionality should even be
> incorporated directly into the DataStore extension (honest question: are
> there many people using DataStore without the DataPusher, and if so, why?).
>
>
> Best regards,
> Florian
>
>
> * after adding a resource with an uploaded CSV file to an existing
> dataset, DataPusher not only failed to push the data into DataStore
> automatically but also somehow managed to break the DataStore-entries for
> the dataset's existing resources so that all of them had to be re-uploaded
> to the DataStore "manually" by clicking the button in the UI.
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20180130/b28b46e1/attachment-0003.html>