-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with read-only resources #59
Comments
+1 |
@anibalpacheco @ilkosta What version of CKAN and the datastorer are you using? |
@amercader master branch on both |
@amercader master branch on both, just pulled from git and recreated databases |
I don't think that this extension works any more with current CKAN master. Its functionality is being moved to the datapusher, see here for details: https://github.com/okfn/ckan/wiki/Viewing-Resource-Data#current-plans |
This should be a simple fix to the extension, by adding force=True here. i.e could someone with a working setup test this for me? |
@kindly Didn't work for me, same errors. |
@amercader Tried the datapusher but it's not clear how it works, I could post a job perfectly, ¿but then? |
This has been fixed in ckanext-datastorer master now cd68d60. Nonetheless, we are trying to convert people over to the datapusher for the next release. New docs for this are here. |
Every task related to datastore raises an error regarding to read-only resources, where is that read-only set?
example:
$ paster datastore_upload test5 -c ../ckan/development.ini
2013-10-30 16:41:43,036 DEBUG [ckanext.archiver.plugin] Notified of resource event: 2eaa3568-8442-4228-923e-1af417dd869e
2013-10-30 16:41:43,036 DEBUG [ckanext.archiver.plugin] Ignoring resource event because operation is: changed
2013-10-30 16:41:44,260 WARNI [root] Resource downloaded: id=2eaa3568-8442-4228-923e-1af417dd869e url=u'http://localhost:5000/storage/f/2013-10-30T18%3A40%3A50.898Z/201212-1.csv' cache_filename=/tmp/tmp_wm11j length=4112 hash=bd185413696e07808f20e8d0a03c5fadd4d42977
2013-10-30 16:41:44,312 ERROR [root] {'read-only': ['Cannot edit read-only resource. Either pass"force=True" or change url-type to "datastore"']}
The text was updated successfully, but these errors were encountered: