I've been experimenting with importing SPARQL endpoints via Import > Create Connection File For SPARQL Endpoint. This works great for smaller datasets, and having the endpoint wrapped as a virtual graph is a great feature I'd like to take advantage of. However, since it tries to cache all triples at that SPARQL endpoint, it is not practical for large datasets (e.g. DBPedia). Is there a way to configure a virtual graph for a SPARQL endpoint that does not try to cache the contents of the remote store?
-- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/9749e6cc-0534-4934-8f39-d7ca8fe675a3n%40googlegroups.com.
