You both should take a look at the entity centric index -- it uses the column
family and column qualifier to store triple info outside of the row key. We
have looked at alternate storage schemes, they have been largely abandoned due
a desire to not disrupt existing users (which may have tools
hi
Since triples are stored entirely in the row id in Accumulo.
Can i use column qualifier or value for storing different parameters for
the triples.So that I could implement some iterator to filter the
triples based on these parameters and then run sparql queries on these
triples.
On Tues
Good questions. Putting all of the information in the Row ID seems like a
common pattern for composite indices in Accumulo, but I went back to the
original Rya Paper [1] to pull out the reasoning:
"""
All the data for the triple resides in the Accumulo Row ID. This offers
several benefits: 1) by
As I understand, Rya stores triples entirely in the row id in Accumulo.
Why?
Are entries stored this way to avoid overloading rows?
Is the storage configurable; that is, could I set a flag to allow triples
to be stored with one part of the triple in the row id, one part in the
column family, and
