Rya commercial support

[Ly, Kiet]

Beside community support from Rya’s committers which I think is awesome, is 
there a commercial support for Rya? I Googled and found none.

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.

Re: answered: RAT complains about tinkerpop.rya

[Ly, Kiet]

[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check 
(check-licenses) on project rya.extras: Too many files with unapproved license: 
12 See RAT report in: 
/Users/lyk/Projects/Github/rya/rya-master/extras/target/rat.txt -> [Help 1]

Look like rat check license on eclipse artifact and output file. Bad rat config.

On 1/19/17, 12:32 PM, "Josh Elser" <josh.el...@gmail.com> wrote:

David/Kiet,

Can either of you share the report file that RAT generates (in target/) 
for the given module where it failed? This describes what failed the check.

Like Puja says, this shouldn't be happening under normal circumstances. 
It's something that was verified before the first release.

Puja Valiyil wrote:
> Fresh checkouts shouldn't have any rat errors-- it's building with rat
> enabled on apaches build servers.
>
> On Wednesday, January 18, 2017, Ly, Kiet<kiet...@finra.org>  wrote:
>
>> I just used mvn clean install -DskipTests -Drat.skip=true. Master branch
>> has a lot of rat errors.
>>
>> On 1/18/17, 5:43 PM, "David Lotts"<dlo...@gmail.com<javascript:;>>
>> wrote:
>>
>>  If your maven build err's with RAT complaints about  tinkerpop.rya 
then
>>  delete it.
>>
>>  The sub-project formerly known as "tinkerpop.rya" has recently been
>> removed
>>  from master. There is a new tinkerpop sub-project under a different
>> name, I
>>  think.
>>
>>  Anyway, I discovered that git won't delete the folder on checkout 
(in a
>>  previously used git clone) because it had a "target" subfolder, 
which
>> is
>>  explicitly ignored.
>>
>>  So manually remove tinkerpop.rya:
>>   rm -rf  ./extras/tinkerpop.rya
>>
>>  And RAT will no longer complain.
>>
>>  david.
>>
>>
>>
>> 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.
>>
>



*
Summary
---
Generated at: 2017-01-19T12:52:30-05:00
Notes: 2
Binaries: 45
Archives: 4
Standards: 32

Apache Licensed: 18
Generated Documents: 0

JavaDocs are generated and so license header is optional
Generated files do not required license headers

12 Unknown Licenses

***

Unapproved licenses:

  /Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/.classpath
  /Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/.project
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/.settings/org.eclipse.core.resources.prefs
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/.settings/org.eclipse.jdt.core.prefs
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/.settings/org.eclipse.m2e.core.prefs
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/.plxarc
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/classes/META-INF/MANIFEST.MF
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/maven-status/maven-compiler-plugin/compile/default-compile/createdFiles.lst
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/maven-status/maven-compiler-plugin/compile/default-compile/inputFiles.lst
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/maven-status/maven-compiler-plugin/testCompile/default-testCompile/createdFiles.lst
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/maven-status/maven-compiler-plugin/testCompile/default-testCompile/inputFiles.lst
  
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/rat.txt

***

Archives:

 + 
/Users/lyk/Projects/Github/rya/rya-master/extras/rya.geoindexing/target/rya.geoindexing-3.2.11-incubating

InterruptedException

[Ly, Kiet]

I got interrupted exception during query. Is it timing out? Is there a 
parameter setting for query timeout? Thanks.

root cause
java.lang.InterruptedException

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2088)

java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:418)

org.apache.accumulo.core.client.impl.TabletServerBatchReaderIterator.hasNext(TabletServerBatchReaderIterator.java:202)

org.apache.rya.accumulo.query.RyaStatementBindingSetKeyValueIterator.hasNext(RyaStatementBindingSetKeyValueIterator.java:96)

org.apache.rya.api.persist.utils.RyaDAOHelper$2.hasNext(RyaDAOHelper.java:142)

info.aduna.iteration.ConvertingIteration.hasNext(ConvertingIteration.java:73)

org.apache.rya.rdftriplestore.evaluation.MultipleBindingSetsIterator.getNextElement(MultipleBindingSetsIterator.java:84)

org.apache.rya.rdftriplestore.evaluation.MultipleBindingSetsIterator.getNextElement(MultipleBindingSetsIterator.java:36)

info.aduna.iteration.LookAheadIteration.lookAhead(LookAheadIteration.java:91)

info.aduna.iteration.LookAheadIteration.hasNext(LookAheadIteration.java:60)

org.apache.rya.rdftriplestore.evaluation.MultipleBindingSetsIterator.initIter(MultipleBindingSetsIterator.java:65)

org.apache.rya.rdftriplestore.evaluation.MultipleBindingSetsIterator.(MultipleBindingSetsIterator.java:50)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:110)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:756)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:200)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:256)

org.apache.rya.rdftriplestore.evaluation.MultipleBindingSetsIterator.(MultipleBindingSetsIterator.java:48)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:110)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:756)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:200)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:256)

org.apache.rya.rdftriplestore.evaluation.MultipleBindingSetsIterator.(MultipleBindingSetsIterator.java:48)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:110)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:756)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:200)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:256)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:662)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:577)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:197)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:256)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:607)

org.openrdf.query.algebra.evaluation.impl.EvaluationStrategyImpl.evaluate(EvaluationStrategyImpl.java:197)

org.apache.rya.rdftriplestore.evaluation.ParallelEvaluationStrategyImpl.evaluate(ParallelEvaluationStrategyImpl.java:256)

org.apache.rya.rdftriplestore.RdfCloudTripleStoreConnection.evaluateInternal(RdfCloudTripleStoreConnection.java:393)

org.openrdf.sail.helpers.SailConnectionBase.evaluate(SailConnectionBase.java:295)

org.openrdf.repository.sail.SailTupleQuery.evaluate(SailTupleQuery.java:60)

org.openrdf.repository.sail.SailTupleQuery.evaluate(SailTupleQuery.java:75)

org.apache.cloud.rdf.web.sail.RdfController.performQuery(RdfController.java:211)

org.apache.cloud.rdf.web.sail.RdfController.queryRdf(RdfController.java:151)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

accumulo native memory setting

[Ly, Kiet]

Has anyone used the native memory setting and found it stable enough for 
production used?  I found the data loading job crashed randomly after I turned 
it on. May be my setting was wrong elsewhere?


tserver.memory.maps.max
4G
  

  
tserver.memory.maps.native.enabled
true
  

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.

Rya UI/Console?

[Ly, Kiet]

Does Rya has any UI to run SPARQL query?

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.

Re: rya parser failed on parsing large numeric type

[Ly, Kiet]

Good idea, but why can’t you use LongEncoder which is also 8 bytes?

BigInteger.parseInt(array, start, end) required array conversion and extra 
start,end parameters.



I replaced Integer to Long and it worked for me.

public static final TypeEncoder INTEGER_STRING_TYPE_ENCODER = 
LexiTypeEncoders.longEncoder();



On 1/11/17, 12:51 PM, "David Lotts"  wrote:



I had an idea to make this work backwardly compatible.  It should not break

existing Rya repositories:

Encode the java sized integers as-is, then for anything out of range, use

MAX/MIN and concatenate the new big integer encoding.



Here is the current way of encoding returning a string:

return INTEGER_STRING_TYPE_ENCODER.

encode(Integer.parseInt(data));



Here is my replacement:



if  (value >= Integer.MAX) { //  value is a string, fix this with

parseint() and catch or similar

return INTEGER_STRING_TYPE_ENCODER.encode(Integer.MAX) +

bigIntegerEncode(value) ;

} else if (value <= Integer.MIN) {

return INTEGER_STRING_TYPE_ENCODER.encode(Integer.MIN)  +

bigIntegerEncode(value) ;

} else {

return INTEGER_STRING_TYPE_ENCODER.

encode(Integer.parseInt(data));

}



The only disadvantage I see is that every big integer literal that you

store will have an extra 8 bytes.  Regular integers are unencumbered.



david.



On Tue, Jan 10, 2017 at 3:32 PM, David Lotts  wrote:



> > RDF parser confused between large numeric data type with integer. Any

> work around for this?  This is a recent build from master branch 3.2.10 I

> think.

>

> This issue is reported here: https://issues.apache.org/jira/browse/RYA-43

>

> This has a mechanically simple fix, but it breaks existing

> implementations.  So making it backward compatible is probably why it has

> not been done yet.  Backward compatible can be done by designing a way to

> mix the encoding from LexiTypeEncoders.bigIntegerEncoder() with the

> existing LexiTypeEncoders.integerEncoder().  Or create a new Lexical

> encoder, that handles both, or maybe upgrade utility to modify the data.

>

> So you could do this as a work around in your own code if you have luxury

> of starting from an empty Rya repo:

>

> Copy 
/rya.api/src/main/java/org/apache/rya/api/resolver/impl/IntegerRyaTypeResolver.java

> to LittleIntegerRyaTypeResolver.java

>

> Then, in IntegerRyaTypeResolver.java, where-ever it uses a Integer,

> replace with a BigInteger.

> Replace LexiTypeEncoders.integerEncoder()  with LexiTypeEncoders.

> bigIntegerEncoder()

> https://github.com/calrissian/mango/blob/master/mango-core/

> src/main/java/org/calrissian/mango/types/encoders/lexi/

> BigIntegerEncoder.java

>

> Test and done!

>

> david.

>



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.

Re: Should Rya have a Twitter account?

[Ly, Kiet]

It is great and free marketing. Definitely should open an account. Appoint a 
social maven POC from one of the committers.

On 1/11/17, 9:58 AM, "David Lotts"  wrote:

Should Rya have a Twitter account?
Lets discuss it.
Who would manage it?  How to manage the password?
david.



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.

rya parser failed on parsing large numeric type

[Ly, Kiet]

RDF parser confused between large numeric data type with integer. Any work 
around for this?
This is a recent build from master branch 3.2.10 I think.

Caused by: java.lang.NumberFormatException: For input string: 
"-6703205597155942197"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:583)
at java.lang.Integer.parseInt(Integer.java:615)
at 
org.apache.rya.api.resolver.impl.IntegerRyaTypeResolver.serializeData(IntegerRyaTypeResolver.java:48)

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.

Re: Rya Working Group tomorrow

[Ly, Kiet]

Can we talk about the Architecture roadmap?
Also can we focus our integration backend with other open source projects, 
HBase, Cassandra rather than commercial product like DynamoDB given this is an 
open source project?
I would also like to see more Spark integration and convert exist MR to use 
Spark processing. MR is now consider legacy framework.

On 8/9/16, 11:00 AM, "Adina Crainiceanu"  wrote:

Puja, thank you so much for offering to talk about DynamoDB. I'm interested
in that, but I think it would be good if we can talk about the release
tomorrow. Maybe we can figure out what needs to be done and see how
everyone can help with the release.

Thanks,
Adina

On Tue, Aug 9, 2016 at 10:20 AM, Puja Valiyil  wrote:

> Hi everyone,
> Tomorrow is the next Rya Working Group meeting.  When we last met (a month
> ago), we had discussed having a discussion about the new DynamoDB backend
> for Rya.  I'm fine with leading that discussion, but I was wondering if
> anyone would rather we talk about something else.  Perhaps a status on the
> impending release?
>
> Let me know what everyone would like to discuss -- I can prepare something
> about the Dynamodb pull request if there isn't something else everyone
> would like to discuss.
>
> Thanks,
> Puja
>
>

-- 
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department
United States Naval Academy
410-293-6822
ad...@usna.edu
http://www.usna.edu/Users/cs/adina/



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.

owl:sameAs

[Ly, Kiet]

Hi,

Why owl:sameAs can infer the 2 addresses below the same? What do I need to have 
inference engine infers both addresses are the same?.

address:addressSet rdf:type rdfs:Class .
address:addressSet owl:hasKey ( address:NUMBER address:STREET address:ZIP ) .

address:ADDR1 rdf:type address:addressSet .
address:ADDR1 address:NUMBER "123"^^xsd:string .
address:ADDR1 address:STREET "THE STREET"^^xsd:string .
address:ADDR1 address:ZIP "12345"^^xsd:string .

address:ADDR2 rdf:type address:addressSet .
address:ADDR2 address:NUMBER "123"^^xsd:string .
address:ADDR2 address:STREET "THE STREET"^^xsd:string .
address:ADDR2 address:ZIP "12345"^^xsd:string .

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.

Re: RYA as triple stores questions?

[Ly, Kiet]

I know. It is the best way the reach at a lot of people at once. 
Of course, if any want to share the deployment info please email me privately 
kiet...@finra.org.


I saw your list of inference properties (rdfs/owl) and it is very basic. Is 
there plan to improve it?
Bring in OWL 2 reasoner (Pellet/Hermit)?. I will attend the bimonthly meeting 
later today.



On 6/15/16, 9:49 AM, "Puja Valiyil" <puja...@gmail.com> wrote:

>Hi Kiet,
>I'm not sure that a lot of us can disclose over the dev list a lot of the
>places that Rya is currently running operationally.
>As far as your other questions, I'm not aware of any hard limitations
>though I'm not sure I understood the question -- maybe Aaron or Adina (or
>someone else) might have more insight?
>I haven't heard of many operational issues with Accumulo, other than a lot
>of performance can be configuration dependent.  Accumulo has a lot of
>documentation on configuration and installation.  If you have more
>specifics about your particular deployment, we may be able to help more.
>
>On Tue, Jun 14, 2016 at 8:48 PM, Ly, Kiet <kiet...@finra.org> wrote:
>
>> We are trying to evaluate RYA as potential semantic data lake running on
>> EMR cluster. If I can get some answer to these questions, it would help us
>> greatly.
>>
>> What is the largest triples store currently in production using RYA in
>> term of billion/trillion of triples?
>> Any of the production installation running on EMR in AWS? If yes, what is
>> the instance types, #of nodes, # of zookeepers, etc..
>> Are there any hard limitations (# of nodes, min/max memory, etc…)?
>> Any operational issues with Accumulo? We had a lot of experience with
>> Hbase but not with Accumulo.
>>
>>
>>
>>
>> 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.
>>

RYA as triple stores questions?

[Ly, Kiet]

We are trying to evaluate RYA as potential semantic data lake running on EMR 
cluster. If I can get some answer to these questions, it would help us greatly.

What is the largest triples store currently in production using RYA in term of 
billion/trillion of triples?
Any of the production installation running on EMR in AWS? If yes, what is the 
instance types, #of nodes, # of zookeepers, etc..
Are there any hard limitations (# of nodes, min/max memory, etc…)?
Any operational issues with Accumulo? We had a lot of experience with Hbase but 
not with Accumulo.




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.

RE: RYA-83

[Ly, Kiet]

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 <puja...@gmail.com<mailto:puja...@gmail.com>>
Date: Tuesday, Jun 14, 2016, 8:18 AM
To: dev@rya.incubator.apache.org 
<dev@rya.incubator.apache.org<mailto:dev@rya.incubator.apache.org>>
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 <kiet...@finra.org> 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.

compile with accumulo 1.7.1

[Ly, Kiet]

How hard is it to update rya to use accumulo 1.7.x? Develop branch failed to 
compile with accumulo 1.7.1.

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.