freebase data under Jena

Hello, This is me again. :) I have the following (very big) problem. Last year in November I have loaded freebase dump to Jena TDB and I was able to work with it reasonably good and got quite good performance for most of my queries. Recently I have updated my Jena TDB store with a dump from April.

Re: Reading TDB dataset in a union model

Thanks Andy, that works fine now. Karen On Monday, May 5, 2014 3:15 PM, Andy Seaborne wrote: On 25/04/14 04:41, Karen Menz wrote: (your message got dumped in my gmail spam folder) > Hi, >    I'm able to store a set of RDF/OWL files in a TDB dataset. > Now, I wonder if there's a way to read thi

Re: Persisting named graphs in TDB with jena-fuseki

Indeed the rule reasoner pre-dates the notion of datasets and only applies to a model = set of triples. Dave On 12/05/14 19:12, Сергей Антоненко wrote: Thanks, I've understood my problem. I was trying to produce minimal config version to reproduce the bigger problem. I am using a generic jen

Re: Problem with "datatype" function in a SPARQL query

Hi! Thanks for your answer both! Yep, the problem was in the parenthesis. Sorry if the message arrive twice to the mailing list, I had some problems with the email! Cheers On 11 May 2014 18:27, Andy Seaborne wrote: > On 9 May 2014 11:38, Alejandro Rodríguez González > wrote: > > Hi all, > >

Re: Persisting named graphs in TDB with jena-fuseki

Thanks, I've understood my problem. I was trying to produce minimal config version to reproduce the bigger problem. I am using a generic jena rules reasoner and I'm trying to make it work for all named graphs. But it seems like it can be applied only to a model (which as I believe is just a more

typed literals to java classes, problem with short and byte.

According to the docs: http://jena.apache.org/documentation/notes/typed-literals.html These are all available as static member variables from com.hp.hpl.jena.datatypes.xsd.XSDDatatype . Of these type

Re: Problem with "datatype" function in a SPARQL query

On 12/05/14 13:57, Alejandro Rodríguez González wrote: Hi! Thanks for your answer both! Yep, the problem was in the parenthesis. Sorry if the message arrive twice to the mailing list, I had some problems with the email! There were problems - all Apache lists email was offline for much of last

Re: Group By Query in Jena Java

Andy, On 12 May 2014, at 13:19, Andy Seaborne wrote: > On 12/05/14 12:54, Hugh Williams wrote: >> Hi Rob, >> >> What is not SPARQL 1.1 about the query being run ie >> >> select distinct ?T1 ?T2 count(*) from >> where >> { >> ?s1

Re: Group By Query in Jena Java

Hi Rob, What is not SPARQL 1.1 about the query being run ie select distinct ?T1 ?T2 count(*) from where { ?s1 ?T1. ?s2 ?T2. ?s1 ?s2. ?s2

Re: Group By Query in Jena Java

On 12/05/14 12:54, Hugh Williams wrote: Hi Rob, What is not SPARQL 1.1 about the query being run ie select distinct ?T1 ?T2 count(*) from where { ?s1 ?T1. ?s2 ?T2. ?s1

Re: Persisting named graphs in TDB with jena-fuseki

Hi there, Your setup creates an in-memory dataset and put a single graph from TDB into that dataset and only that graph. New graphs will go into the in-memory dataset, which isn't persistent. SPARQL operations act on datasets. Is there a specific reason for this setup? To attach the whole

Lucene & TDB Question

Hi,   I'm trying to get Lucene working with TDB, but no luck so far. I already have a TDB dataset saved in "tdb_directory" folder, with the following platform:     Jena-2.11.1     Lucene-4.8.0 (Apache)     Java-1.7.0, 64-Bit   And I have the following code: Dataset ds1 = TDBFactory.createDatas

Re: Group By Query in Jena Java

Yes, though the Virtuoso specific syntax shown there is not legal SPARQL See Aggregates (http://www.w3.org/TR/sparql11-query/#aggregates) in the SPARQL 1.1 specification which Jena fully supports Rob On 12/05/2014 05:49, "Md Mizanur Rahoman" wrote: >Dear Experts, > >My question is: > >Is there

Re: Inferencing

On 12/05/14 01:46, Kamalraj Jairam wrote: Hello All, Quick question on Ontology and inferencing If i have an RDF file with following statements A rdf:type e I have loaded this file into a Jena Model The OWL file has following statements in it