I'm not exactly sure what you mean by "limit per node". I think you can
handle the limit per node in sparql, eg:
SELECT * WHERE {
{ SELECT * WHERE { ?s a <t:person> } LIMIT 100 }
{ SELECT * WHERE { ?s <p:talksTo> ?o . ?o a <t:person>} LIMIT 10 }
}
So this would, at most, return 1000 results (at most 100 "people" who "talk
to" at most 10 other people). Is this what you mean?
Note: I haven't tested this out yet in on an RDF repo, and I'd have to
double check how gracefully Rya handles this join.
--Aaron
On Wed, Feb 22, 2017 at 7:39 PM Liu, Eric <[email protected]> wrote:
> Hi,
>
> Continuing from our talk earlier today I was wondering if you could
> provide more information about how timestamps could be queried in Rya.
> Also, we are trying to support a type of query that would essentially be
> limiting on cardinality (different from the normal SPARQL limit because
> it’s for node cardinality rather than total results). I saw in one of
> Caleb’s talks that Rya’s query optimization involves checking cardinality
> first. I was wondering if there would be some way to tap into this feature
> for usage in queries?
>
> Thanks,
> Eric Liu
> ________________________________________________________
>
> The information contained in this e-mail is confidential and/or
> proprietary to Capital One and/or its affiliates and may only be used
> solely in performance of work or services for Capital One. The information
> transmitted herewith is intended only for use by the individual or entity
> to which it is addressed. If the reader of this message is not the intended
> recipient, you are hereby notified that any review, retransmission,
> dissemination, distribution, copying or other use of, or taking of any
> action in reliance upon this information is strictly prohibited. If you
> have received this communication in error, please contact the sender and
> delete the material from your computer.
>
