Tim,
This should work. The Classes View should look for classes only, except there is an instance count. The Properties View should look for properties only. The Instances View and SPARQL results will display only the first 1,000 or whatever the number you set in Preferences. I don't see the attached screenshot, but I would disable the display of the count of instances per class in the Class View. I would not remove building caches for subClassOf and subPropertyOf. We may need a call if you are still stuck. Regards, Irene From: [email protected] [mailto:[email protected]] On Behalf Of Tim Smith Sent: Friday, April 11, 2014 1:00 PM To: [email protected] Subject: Re: [topbraid-users] How to NOT cache all triples from database back end Ok, that I understand. In this case there are < 1000 classes and ~100 properties. The class/property definitions are not stored in the triple store. They are stored in local files which are imported as needed. So is TBC actually pulling out all the triples or just "definition" triples to find all the classes and properties to display? i.e SELECT ?s ?p ?o vs just looking for classes/properties... Thanks, Tim On Fri, Apr 11, 2014 at 12:42 PM, Scott Henninger <[email protected]> wrote: Tim, the issue is that Composer displays the classes and properties. If you have an ontology with a few classes and properties, Composer works well. Getting the first n instances (1000 out-of-the-box) when choosing the Instances view, etc. But if you have an ontology with 20k class definitions, then all need to be cached to display the tree. Same for properties. -- Scott On 4/11/2014, 11:32 AM, Tim Smith wrote: Hi Mark, So there is no way to tell Composer to not load the entire contents of an Oracle RDF triple store into memory when first opening the Oracle connector file? No queries have been issued at this point. That really can't be the case or TBC is completely useless for creating and editing anything that can't be held in local memory. I expect TBC to behave differently when the triples are hosted in a triple store vs a file system. Thoughts? Thanks, Tim On Fri, Apr 11, 2014 at 12:23 PM, Mark Graham <[email protected]> wrote: Hi Tim, Composer will need to cache all the data it needs to display the database. But some performance issue from large files can be mitigated with the use of SPARQLMotion or a SWP UI to control how the data is cached into memory - (written such that no data is cached until the query is executed, etc.). Thanks, Mark Thanks, Mark Mark Graham TopQuadrant Support *PRODUCT SUPPORT:* [email protected] http://www.topquadrant.com/products/support.html On Fri, Apr 11, 2014 at 11:10 AM, Tim Smith <[email protected]> wrote: Hi, I'm using TBC 4.3.1 with an Oracle 11g triple store. There are nearly 100M triples in the triple store. I am trying to get TBC to stop attempting to cache all the triples when I open the Oracle connector file in the workspace. I've read the help sections related to database back ends and I've checked "Suppress default superclass inferences for database projects" and I've removed all entries from the "Prebuild caches for properties" option. See attached screenshot. However, when I open the connector file using TBC, the error log displays: Starting caching all triples... and then gives me a count of how many triples it has cached. I end up canceling the load because I don't want all the triples cached locally. What am I missing? The help pages seem to indicate that these settings should disable the caching for large database. Thanks in advance for your help. I'm stuck until I get this one figured out. Tim -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] <mailto:topbraid-users%[email protected]> For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- 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]. For more options, visit https://groups.google.com/d/optout. -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] <mailto:topbraid-users%[email protected]> For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- 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]. For more options, visit https://groups.google.com/d/optout. -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- 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]. For more options, visit https://groups.google.com/d/optout. -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] <mailto:topbraid-users%[email protected]> For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- 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]. For more options, visit https://groups.google.com/d/optout. -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- 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]. For more options, visit https://groups.google.com/d/optout. -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- 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]. For more options, visit https://groups.google.com/d/optout.
