afs commented on issue #1324: URL: https://github.com/apache/jena/issues/1324#issuecomment-1133226505
Does quite explain why there is a 100Mb literal in a query but no matter. SPARQL parsing is central so any changes need to be done carefully, and be proven and mature. Like javacc, I'm thinking about unforeseen consequences. The parser to use is (surprise!) controlled by a registry `SPARQLParserRegistry` so extension code can change the parser for an experimental one. Also -- The jaavcc issue suggests a different approach which is also more efficient - lexical states and lexical actions. The string for token image can be created directly without going through the javacc buffering. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
