Hi Erich,
Ah, you should not really be using that bitmap index with the default v7
indexes which are for column store. I tried that myself just now and my server
crashed on Mac loading datasets, which it should not even if the indexes are
mismatched, so I have reported to development. The docs
Hi Hugh,
Reason #1: The Virtuoso tuning guide suggested:
"If predicate and graph are given but subject is not, then it is
sometimes useful to add:
CREATE BITMAP INDEX RDF_QUAD_PGOS ON DB.DBA.RDF_QUAD (G, P, O, S)
PARTITION (O VARCHAR (-1, 0hex));"
The instructions did not indicate for this
Hi Erich,
Why are you creating these additional indexes and if you did were the defaults
dropped first ? What does the the following query return:
STATISTICS DB.DBA.RDF_QUAD;
Which should return a list of indexes on the RDF_QUAD table ...
As indicated in the performance tuning guide th
Either way, I get the following error when starting my bulk load:
*** glibc detected *** virtuoso-t: double free or corruption (out):
0x7f6b710f2000 ***
Segmentation fault
- Erich
Erich Bremer
http://www.ebremer.com
The default schema as per the below URL is:
CREATE DISTINCT NO PRIM
The default schema as per the below URL is:
CREATE DISTINCT NO PRIMARY KEY REF BITMAP INDEX RDF_QUAD_SP
ON RDF_QUAD (S, P)
PARTITION (S INT (0hex00));
CREATE BITMAP INDEX RDF_QUAD_POGS
ON RDF_QUAD (P, O, G, S)
PARTITION (O VARCHAR (-1, 0hex));
CREATE DISTINCT NO PRIMARY KEY RE
Hi,
I tried creating the index as per the page:
http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtRDFPerformanceTuning
CREATE BITMAP INDEX RDF_QUAD_PGOS ON DB.DBA.RDF_QUAD (G, P, O, S) PARTITION (O
VARCHAR (-1, 0hex));
which successfully creates via ISQL (seemingly), but
