It is the same with spark. Call collect() on large dataset will blow up the
driver. The trick is select * where {} limit n. The use case i wanted to check
the triples just inserted are there.
From: Puja Valiyil <[email protected]<mailto:[email protected]>>
Date: Tuesday, Jun 14, 2016, 8:18 AM
To: [email protected]
<[email protected]<mailto:[email protected]>>
Subject: Re: RYA-83
Hi Kiet,
I've been meaning to post on your ticket. This is a deliberate feature for Rya
that is intended to avoid inadvertently starting a full table scan. Since the
data stored in Rya may be extremely large since it is intended for cloud based
systems, the exception is intentionally thrown. It isn't compliant with sparql
1.1 to not support that query, so I'm not sure if we should change it or not.
What does everyone else think?
Thanks,
Puja
Sent from my iPhone
> On Jun 14, 2016, at 7:26 AM, Ly, Kiet <[email protected]> wrote:
>
> I wrote up https://issues.apache.org/jira/browse/RYA-83. Is this a valid
> issue? It failed on select * where { ?s ?p ?o . }. I tested the this query on
> Blazegraph and it works correctly.
> I used POSTMAN to send in sparql query request against a develop branch build.
>
> Confidentiality Notice:: This email, including attachments, may include
> non-public, proprietary, confidential or legally privileged information. If
> you are not an intended recipient or an authorized agent of an intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of the information contained in or transmitted with this e-mail is
> unauthorized and strictly prohibited. If you have received this email in
> error, please notify the sender by replying to this message and permanently
> delete this e-mail, its attachments, and any copies of it immediately. You
> should not retain, copy or use this e-mail or any attachment for any purpose,
> nor disclose all or any part of the contents to any other person. Thank you.
