I put up a "limit per node" example here [1] and Rya behaves as I expected. Strangely, OpenRDF does not :/
Unfortunately, the join between the two inner "SELECT" statements is not the more efficient MultipleBindingSetsIterator. Instead, the join is the less efficient OpenRDF Join. --Aaron [1] https://github.com/amihalik/sesame-debugging/blob/6a26045d89ebee1c72cc0452e2b01dc29544b85c/src/main/java/com/github/amihalik/sesame/debugging/NodeLimitExample.java On Wed, Feb 22, 2017 at 9:24 PM Meier, Caleb <caleb.me...@parsons.com> wrote: > Hey Eric, > > Currently timestamps can't be queried in Rya. Do you need to be able to > query by timestamp, or simply discover the timestamp for a given node? Rya > does have a temporal index, but that requires you to use a temporal > ontology to model the temporal properties of your graph nodes. > ________________________________________ > From: Liu, Eric <eric....@capitalone.com> > Sent: Wednesday, February 22, 2017 6:38 PM > To: dev@rya.incubator.apache.org > Subject: Timestamps and Cardinality in Queries > > 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. >
