-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Correct Handling of Escape Sequences in the TurtleParser
- SPARQL also allows escape sequences in PrefixedNames like rdfs:l\,abel These were previously unsupported, which is now fixed. - We now also transform escape sequences in sparql literals to their correct form during index build. - Several changes to the Index class unit tests had to be made, because they used knowledge base elements like a instead of <a> which is no longer supported by any of the parsers. - Disable the CTRE parser for now, since it becomes awefully slow with the the fixes for the prefixed names. TODO: Maybe we want to reimplement the old and wrong behavior and make CTRE a general "WikidataUnsafe" parser. - Get rid of misleading warning in case of whitespace at the end of a TTL file. Previously there was a "parsing of ttl has failed, but there is still content left" warning, although the remainder of the ttl input was only whitespace. - Made the ad_utility::hash_set also use absl. now we have completely removed the dependency from google::sparsehash and migrated to absl.
- Loading branch information
Showing
15 changed files
with
409 additions
and
260 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
{ | ||
"num-triples-per-partial-vocab" : 40000, | ||
"parser-batch-size" : 1000, | ||
"ascii-prefixes-only":true | ||
"ascii-prefixes-only":false | ||
} |
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.