Dear Andy, ajs6f and Conal, Thanks for all the help and guidance, RIOT turned out to be an invaluable tool especially while bulk loading.
The error was indeed a case of bad encoding, I've since modified my parser to encode my *.ttl correctly in UTF-8. Best, Trevor. On 20 August 2017 at 23:24, Andy Seaborne <[email protected]> wrote: > It's probably a binary file - it fails at character 2 of a UTF-8 decode > block which are 128K chunks. RIOT converts from UTF-8 to chars in large > chunks for speed. > > The downside is that the error message is less readable as it is generated > by the Java runtime. Similarly with character encoding issue with SPARQL > except here it is javacc's reader that is involved. > > Andy > > > On 19/08/17 23:51, Conal Tuohy wrote: > >> If it turns out that the problem actually is that your Turtle file is >> incorrectly encoded, then Fuseki should return an HTTP 400 (Bad Request) >> rather than a 500. Could you log this as a bug, if so? >> >> On 18 Aug 2017 21:19, "Trevor Lazarus" <[email protected]> wrote: >> >> Thanks Andy, >>> >>> This is what I get when I run s-post >>> >>> uploading /LD/data/TTL/papers/faia243-1313.ttl... >>> 500 java.nio.charset.MalformedInputException: Input length = 2 >>> http://localhost:3030/ds/data?default >>> >>> Trevor. >>> >>> >>> >>> On 18 August 2017 at 15:28, Andy Seaborne <[email protected]> wrote: >>> >>> What's the stacktrace? >>>> >>>> s-post doe snot touch the file at all so if the Turtle file has bad >>>> characters in it (e.g. it's ISO-8859-1 abut Turtle is UTF-8) then the >>>> problem arises at the server. >>>> >>>> Do the files parse from the command line? Run "riot" on them. >>>> >>>> Andy >>>> >>>> >>>> On 18/08/17 08:18, Trevor Lazarus wrote: >>>> >>>> Hello, >>>>> >>>>> While using SOH to S-POST *.ttl files, I've been getting errors when >>>>> the >>>>> triples contain a accented characters, is this something to do with >>>>> Fuseki ? >>>>> >>>>> Thanks, >>>>> Trevor. >>>>> >>>>> >>>>> >>> -- >>> >>> >>> The information in this email and attachments is privileged and >>> confidential and may not be disclosed without the express permission of >>> the >>> sender. This information is intended only for the use of the individual >>> to >>> whom it is addressed. If you have received this communication in error, >>> your review, dissemination, or copying of this information is prohibited. >>> Please reply to alert me of the error and then delete this email. Thank >>> you. >>> >>> >> -- The information in this email and attachments is privileged and confidential and may not be disclosed without the express permission of the sender. This information is intended only for the use of the individual to whom it is addressed. If you have received this communication in error, your review, dissemination, or copying of this information is prohibited. Please reply to alert me of the error and then delete this email. Thank you.
