I can find it with this query
select * {
<urn:org.apache.rya/2012/05#rts> ?p ?o .
}
I also get it when I load the graph into GraphX, since it pulls the entire
graph.
Being but a single triple it isn't a huge deal, but we are establishing the
precedent that metadata about the implementation details of our store is to
be intermixed with the users data, and intermixing user data with
implementation specific details seems like a bad idea. What if a
(malicious?) user wanted to store triples that talk about older versions of
Rya? They could insert the triple e.g.
INSERT DATA { <urn:org.apache.rya/2012/05#rts> <urn:org.apache.rya/2012/05#
version> "1.0.0" . }
And now our system would have the fact that it is both version 3.0.0 and
1.0.0. I imagine that could cause problems.
On Tue, Jan 17, 2017 at 1:18 PM, David Lotts <dlo...@gmail.com> wrote:
> >> When I perform a scan of the rya_spo table after adding a SINGLE triple,
> I
> >> see that Rya adds TWO triples, the one I wanted to add and one denoting
> the
> >> version of Rya. e.g.
>
> Can you see the triple via Sparql?
> This gets amplified now that we support "select * where {?s ?p ?o. }"
>
> Elsewhere, this is done with built-in functions:
>
> select ( system:version() )
>
> For example:
> https://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/
> VirtCheckSvrVersionViaSparql
>
> Pro's:
> All the SQL databases that I know of have system metadata tables. You
> don't see them unless you specify the table name.
> Because SQL tables and RDF name spaces have some similarities, in the same
> way, metadata is scoped and out of the way of applications.
> Also inference gives you triples that you did not add. So it's a "don't
> ask for what you don't want" kind of assumption.
>
> But I'm not an authority.
>
> Code is here:
>
> https://github.com/apache/incubator-rya/blob/master/
> common/rya.api/src/main/java/org/apache/rya/api/domain/RyaSchema.java
>
> The subject: *urn:org.apache.rya/2012/05#*
> is not a valid URI. The possible strings that follow "urn:" are registered
> by IANA
> <http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml> --
> the
> urn namespace. If you want to roll your own, use a URL (http:...) or a the
> "tag" URI scheme, described here: https://tools.ietf.org/html/rfc4151 .
> Tags look like this: *tag:rya.apache.org
> <http://rya.apache.org>,2017:details#version*
>
> david.
>
> On Tue, Jan 17, 2017 at 1:19 PM, Chilton, Kevin <kevin.chil...@parsons.com
> >
> wrote:
>
> > It was checked into 3.2.10. I don't recall if the Rya Details stuff is
> > enabled by default or if it works without using the rya shell to manage
> > your instance. I thought we had a jira ticket relating to version
> > statement, but I'm unable to find it.
> >
> > - Kevin
> >
>
