afs commented on issue #1557: URL: https://github.com/apache/jena/issues/1557#issuecomment-1260790261
This is not a good idea. There is no guarantee the downstream query engine does support dynamic datasets. Just because the main implementations do is not a contract. For example, union graph handling is different. Putting all transformation in one place is better. That is what clearing the query is doing - signalling that here is no further work. The correct way is to add a custom SPARQL_Processor (inherit from SPARQL_QueryDataset) if you want different behaviour. I don't see why you want to intercept the query - why send the wrong query in the first place? -- 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]
