We have this query disabled because it would involve a full table scan. Perhaps we should make this function configurable (an enable this query by default)?
Thanks for opening the ticket, and I'll add my comment onto the ticket. --Aaron On Tue, 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. >
