forked from ad-freiburg/qlever
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Turtle parser: better code, bug fixes, and new unit tests (ad-freibur…
…g#1039) 1. There is now a common base class for our Turtle parsers. That way, methods involed in index building no longer have be be templated with the parser class. 2. The parallel parser now accepts an arbitrary sequence of `\n` and `\r` as newline, and there may be arbitrary whitespace after the final dot in a line. So far, only `\n` was accepted as newline, and a `\t` after the final dot did not work. 3. There is now a Boolean option `parallel-parsing` in the `settings.json` configuration file. It is `true` by default, which is consistent with the behavior so far. 4. Add unit tests for the Turtle parser (both parallel and not parallel). So far, there were unit tests for individual rules, but not for the parser as a whole. In particular, the batching and parallelization were untested so far. 5. Remove the mmap parser becuse it was no longer needed (and probably also not working any longer).
- Loading branch information
Showing
21 changed files
with
629 additions
and
593 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.