-
Notifications
You must be signed in to change notification settings - Fork 52
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
Skip parse error #1583
Comments
@debayan Can you give an example of the kind of line you would like to skip? Roughly speaking, there are two sorts of errors in RDF input:
|
My log shows something like: INFO: By default, integers that cannot be represented by QLever will throw an exception I get this when parsing ttl files from https://downloads.dbpedia.org/repo/lts/wikidata/. This is not the first error I got. I fixed several such errors already (not just integer errors), and I do not know how many other errors exist in this data dump. Since this is a large amount of data, I would rather just skip all such errors and add the dump to my DB. |
@debayan Have you validated the files? Here is a command to do that. Does it only produce warnings or also errors?
And may I ask why you want to use DBpedia? It's old, not well maintained anymore, and of really doubtful quality. I don't think there is anything useful in DBpedia that is not contained in one of the more modern knowledge graphs, notably Wikidata. |
@hannahbast I have not validated the files, and I know it has erroneous lines. I am using DBpedia because we are working on a task where the queries from one KG need to be translated to queries that work on another KG. The only dataset we could find of a reasonable size is LC-QuAD 2.0 which has queries for both KGs for a given question. |
@debayan This has come up again in ad-freiburg/qlever-control#103 and I have looked at it again because I was working on the parser anyway. If it's still relevant for you (or will be again at some point), please join the conversation over there |
Is there an option in QLever to skip lines that produce parse errors during indexing?
The text was updated successfully, but these errors were encountered: