[ECODP-dev] Import SG package problem

John Glover john.glover at okfn.org
Wed Aug 21 10:01:54 UTC 2013


Hi Bert,

I believe that there may have been a bug with checking the encoding
(unicode or not) when trying to process RDF data. This would cause some
dataset imports to fail (with a Python error about ASCII or Unicode).

I'm not sure about other issues that Dimitrios is referring to here
regarding Solr and tomcat, we have still not noticed any problems here. But
yes, if Solr goes down then the import will fail.

Regards,
John


On 21 August 2013 11:40, Bert Van Nuffelen
<bert.van.nuffelen at tenforce.com>wrote:

> Hi John,
>
> can you give some details about what possibly went wrong? Then we can
> communicate better with PO.
>
> Bert
>
>
> 2013/8/21 John Glover <john.glover at okfn.org>
>
>> Hi Dimitrios,
>>
>> Following up on this issue, I believe that it should now be fixed in the
>> latest ckanext-ecportal which is deployed on the test server. Could you
>> please confirm when you get the chance?
>>
>> Thanks,
>> John
>>
>>
>> On 26 July 2013 12:51, Dimitrios Mexis <dimitrios.mexis at tenforce.com>wrote:
>>
>>> Hi David/John,
>>>
>>> we have a strange case. An SG package, that is not uploaded to the
>>> customer, but on our side it is uploaded on 8.
>>>
>>> The file of the output of process, shows something as immediate stop of
>>> communication. With no apparent reason.
>>>
>>> Attachments & Description:
>>> I attach you the rdf file.  Which is the same file, as in a previous
>>> message I had posted, and that gives problems to the customer as well.
>>> the error log of the ecodp, which signifies some possible problem with
>>> SOLR.
>>> The TENFORCE version 8 is the file generated from ourside trying to
>>> upload on 8 release, and it worked.
>>> Release 9, is interrupted messages I got from the latest version.
>>>
>>> Remarks: it seems at this installation of customer, tomcat6 and solr for
>>> version 8 to be...unstable. I don't follow why. As if it might stop on its
>>> own. So : if SOLR is down is the import failing too ?
>>> On 9, I notice strange behavior, that sometimes didn't want to import
>>> the package. Is the rdf valid one for upload ?
>>> I notice that even if I escape characters in bash and using curl I might
>>> have errors like No JSON Output on release 9, and that gives me internal
>>> server errors.
>>>
>>> also, I noticed that it failed to me, once when it was trying to import
>>> the data, when I had marked it as deleted. That happened once. At least
>>> that is what I understood. I didn't expect it so I can not tell for sure if
>>> that is problem.
>>>
>>> They don't claim to have problems with other packages.
>>>
>>> Is it possible to take a look also ?
>>>
>>> Thank you
>>> Dimitrios
>>>
>>
>>
>
>
> --
> Bert Van Nuffelen
>
> Semantic Technologies Software Architect at TenForce
> www.tenforce.be
>
> Bert.Van.Nuffelen at tenforce.com
> Office: +32 (0)16 31 48 60
> Mobile:+32 479 06 24 26
> skype: bert.van.nuffelen
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130821/796992b3/attachment.html>


More information about the ecodp-dev mailing list