RE: rya logo

[Meier, Caleb]

I vote for the logo in the bottom right of the pdf (black disk around blue 
planet with yellow, red, and green moons).  All of the options look great!

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Adina Crainiceanu 
Sent: Monday, September 17, 2018 9:32 AM
To: dev@rya.incubator.apache.org; Robert David 
Cc: Susan Härtig 
Subject: Re: rya logo

Hi Robert,

No attachment to the previous message.

Thanks,
Adina

On Mon, Sep 17, 2018 at 6:01 AM, Robert David  wrote:

> Hi all,
>
> attached you can find proposals for the Rya logo. Please vote for one
> of them.
>
> Best,
> Robert
>
>
> 2018-08-27 15:13 GMT+02:00 Adina Crainiceanu :
>
>> Thank you! Looking forward to having a Rya logo!
>>
>> Best,
>> Adina
>>
>> On Mon, Aug 27, 2018 at 5:06 AM, Robert David <
>> robert.da...@semantic-web.com
>> > wrote:
>>
>> > Hi Adina,
>> >
>> > i will take care that you will get the logo. It may take a little
>> > more time, but end of September is definitely possible.
>> >
>> > Best,
>> > Robert
>> >
>> >
>> > 2018-08-26 22:51 GMT+02:00 Adina Crainiceanu :
>> >
>> > > Hi all,
>> > >
>> > > I'm going to ApacheCon at the end of September and it would be
>> > > really
>> > nice
>> > > to have some stickers with the Rya logo to distribute. Any
>> > > progress on
>> > the
>> > > logo?
>> > >
>> > > I liked the idea of Saturn and its moons, including Rhea, for the
>> > > "in
>> the
>> > > cloud" suggestion, plus the Saturn and its moons could be like
>> > > nodes
>> in a
>> > > graph.
>> > >
>> > > Thanks a lot,
>> > > Adina
>> > >
>> > > On Wed, Apr 18, 2018 at 3:08 PM, David Lotts 
>> wrote:
>> > >
>> > > > > moons of Saturn image is extremely cool, it doesn't seem as
>> relevant
>> > > > I forgot to mention: a moon of Saturn is named Rhea.
>> > > >
>> > > > > we could have our designer (susan, in cc) take a look
>> > > > That would be awsome!  Go Susan!
>> > > >
>> > > > david.
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > Dr. Adina Crainiceanu
>> > > Associate Professor
>> > > Computer Science Department
>> > > United States Naval Academy
>> > > 410-293-6822
>> > > ad...@usna.edu
>> > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.usna.edu_
>> > > Users_cs_adina_=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdf
>> > > xIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=sCx8Q8SuoG9
>> > > _4KiRuDpbyjkyTeImeSGVhJ0lqQB-7F4=Xjy81PymGmn99aHH6QvYulEoxwXhoV
>> > > 89VpOZFBv-LIg=
>> > >
>> >
>> >
>> >
>> > --
>> > *Robert David*
>> > CTO
>> >
>> > Semantic Web Company GmbH
>> >
>> > EU: +43-14021235
>> > US: (415) 800-3776
>> >
>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.poolparty.
>> > biz=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzY
>> > C2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=sCx8Q8SuoG9_4KiRuDpbyjkyTeI
>> > meSGVhJ0lqQB-7F4=BmUEXRLJiRuB9hkXvuYQN7XHT163szWdZ62XaPmcK6g=
>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.semantic-2
>> > Dweb.com=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=v
>> > uVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=sCx8Q8SuoG9_4KiRuDpbyj
>> > kyTeImeSGVhJ0lqQB-7F4=W_71nx57HStHylDjRaIn0SVFLHhb3gc1VvFwngtQ6T8
>> > =
>> >
>> > *Download E-Book*: Introducing Semantic AI
>> > > > .biz_machine-2Dlearning-2Dmeets-2Dsemantics_=DwIBaQ=Nwf-pp4xtYR
>> > e0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCge
>> > o_4WXTD0qo8=sCx8Q8SuoG9_4KiRuDpbyjkyTeImeSGVhJ0lqQB-7F4=91fbsDN
>> > LlXnAILg5F87cEwv0oO73wpCH0Tr9YJ4pmok=>
>> >
>>
>>
>>
>> --
>> Dr. Adina Crainiceanu
>> Associate Professor
>> Computer Science Department
>> United States Naval Academy
>> 410-293-6822
>> ad...@usna.edu
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.usna.edu_User
>> s_cs_adina_=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=
>> vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=sCx8Q8SuoG9_4KiRuDpbyjk
>> yTeImeSGVhJ0lqQB-7F4=Xjy81PymGmn99aHH6QvYulEoxwXhoV89VpOZFBv-LIg=
>>
>
>
>
> --
> *Robert David*
> CTO
>
> Semantic Web Company GmbH
>
> EU: +43-14021235
> US: (415) 800-3776
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.poolparty.biz
> =DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksV
> ZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=sCx8Q8SuoG9_4KiRuDpbyjkyTeImeSGVhJ0l
> qQB-7F4=BmUEXRLJiRuB9hkXvuYQN7XHT163szWdZ62XaPmcK6g=
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.semantic-2Dwe
> b.com=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC
> 2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=sCx8Q8SuoG9_4KiRuDpbyjkyTeImeSG
> VhJ0lqQB-7F4=W_71nx57HStHylDjRaIn0SVFLHhb3gc1VvFwngtQ6T8=
>
> *Download E-Book*: Introducing Semantic AI
>  z_machine-2Dlearning-2Dmeets-2Dsemantics_=DwIBaQ=Nwf-pp4xtYRe0sCRV
> 

RE: How to enable GeoSPARQL support for endpoint on MongoDB?

[Meier, Caleb]

Hey Joost,

Another thing to try.  Try changing the class for the "sail" bean id in your 
spring-mongo-db-geo.xml file to org.apache.rya.indexing.GeoRyaSailFactory.  If 
that doesn't work, you can try adding the following properties to your "conf" 
bean id:


-
-org.apache.rya.indexing.mongodb.geo.MongoGeoIndexer
-
-
-
-
-org.apache.rya.indexing.GeoEnabledFilterFunctionOptimizer
-
-

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Joost Farla <jo...@apiwise.nl>
Sent: Thursday, May 10, 2018 4:22 AM
To: dev@rya.incubator.apache.org
Subject: Re: How to enable GeoSPARQL support for endpoint on MongoDB?

Hi Eric,

I've now added the following lines to spring-mongodb-geo.xml:

sc.use_geo=true
sc.geo.predicates=${sc.geo.predicates}

After that, the application complained about an unknown class:
MongoGeoIndexer.

I've now added rya.geo.mongo as extra dependency for web.rya, but the 
result-set remains empty.

Are you able to reproduce the issue?

Cheers, Joost



2018-05-09 20:38 GMT+02:00 White, Eric <eric.wh...@parsons.com>:

> Nevermind.  Make that change in "spring-mongodb-geo.xml" NOT
> "spring-root-extensions.xml".  And add all the other geo related
> properties in there over too.
>
> sc.geo.table=${sc.geo.table}
> sc.geo.predicates=${sc.geo.predicates}
> sc.geo.numPartitions=${sc.geo.numPartitions}
>
> -Original Message-
> From: White, Eric <eric.wh...@parsons.com>
> Sent: Wednesday, May 09, 2018 2:22 PM
> To: dev@rya.incubator.apache.org
> Subject: RE: How to enable GeoSPARQL support for endpoint on MongoDB?
>
> Sounds like it's still not enabling geo entirely.  "sc.use_geo"
> appears to never be set in the conf.  Modify "spring-root-extensions.xml":
>
> Add in "sc.use_geo" to the "hadoopConf":
>  
> ...
> ...
> sc.use_geo=${sc.use_geo}
> ...
> ...
>   
>
> Thanks,
> -Eric White
>
> -Original Message-
> From: Joost Farla <jo...@apiwise.nl>
> Sent: Wednesday, May 09, 2018 12:26 PM
> To: dev@rya.incubator.apache.org
> Subject: Re: How to enable GeoSPARQL support for endpoint on MongoDB?
>
> Hi Caleb,
>
> I've compared them and they seem identical. For the "unscrambled" data
> and query, I've just created a Gist:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__gist.
> github.com_joostfarla_5c075c8e468b6e40a85987b383174966=DwIFaQ=Nwf-
> pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=RaJkRMooYbg4vmML14E10F9hYEBL
> Oe
> OHS3mAimFNgqQ=KSUZQOWwaQJYPo8HHuU06mwwn3ESiLKUAqpT0x9F_ns=uvqpZy_
> HrZYeHWtazH1sr2VMBlwXB--vNr7wBniHCxo=
>
> Cheers, Joost
>
>
>
> 2018-05-09 18:17 GMT+02:00 Meier, Caleb <caleb.me...@parsons.com>:
>
> > Hey Joost,
> >
> > Have a look at the following IT to make sure that you are formatting
> > your queries correctly:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apac
> > he
> > _incubator-2Drya_blob_master_=DwIFaQ=Nwf-pp4xtYRe0sCRVM8_LWH54jo
> > YF
> > 7EKmrYIdfxIq10=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ=KSUZQ
> > OW
> > waQJYPo8HHuU06mwwn3ESiLKUAqpT0x9F_ns=akVnlrNtzMve69IpjduRTAlnFXszb
> > tj 4A02dzNg9DrE=
> > extras/rya.geoindexing/geo.mongo/src/test/java/org/
> > apache/rya/indexing/mongo/MongoGeoIndexerFilterIT.java
> >
> > Carefully compare your geo predicate and your geo prefixes with the
> > predicate and prefixes in the above example.  Sorry, I can't tell
> > based on the example that you provided below because URLs get
> > scrambled by our e-mail server.
> >
> > Caleb A. Meier, Ph.D.
> > Senior Software Engineer ♦ Analyst
> > Parsons Corporation
> > 1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
> > Office:  (703)797-3066
> > caleb.me...@parsons.com ♦ www.parsons.com
> >
> > -Original Message-
> > From: Joost Farla <jo...@apiwise.nl>
> > Sent: Wednesday, May 09, 2018 11:37 AM
> > To: dev@rya.incubator.apache.org
> > Subject: Re: How to enable GeoSPARQL support for endpoint on MongoDB?
> >
> > Hi Eric,
> >
> > Thanks for replying!
> >
> > Indexing and querying non-geo data is working well. However, when
> > filtering by a GeoSPARQL predicate, the query runs without errors,
> > but the result set is empty (where I would expect 1 binding). Please
>

RE: How to enable GeoSPARQL support for endpoint on MongoDB?

[Meier, Caleb]

Hey Joost,

Have a look at the following IT to make sure that you are formatting your 
queries correctly:

https://github.com/apache/incubator-rya/blob/master/extras/rya.geoindexing/geo.mongo/src/test/java/org/apache/rya/indexing/mongo/MongoGeoIndexerFilterIT.java

Carefully compare your geo predicate and your geo prefixes with the predicate 
and prefixes in the above example.  Sorry, I can't tell based on the example 
that you provided below because URLs get scrambled by our e-mail server.

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Joost Farla <jo...@apiwise.nl>
Sent: Wednesday, May 09, 2018 11:37 AM
To: dev@rya.incubator.apache.org
Subject: Re: How to enable GeoSPARQL support for endpoint on MongoDB?

Hi Eric,

Thanks for replying!

Indexing and querying non-geo data is working well. However, when filtering by 
a GeoSPARQL predicate, the query runs without errors, but the result set is 
empty (where I would expect 1 binding). Please see the exact data and query in 
my initial posting. Indexing geo-data seems to work okay, since the rya_rya_geo 
collection is created and populated with the correct statement.

About spring-mongodb-geo.xml, I did already notice this and I did already 
change the bean class to "org.apache.rya.indexing.GeoRyaSailFactory".
Unfortunately, this does not seem to have any effect.

What else can I try?

Cheers, Joost



2018-05-09 16:52 GMT+02:00 White, Eric <eric.wh...@parsons.com>:

> Joost,
>
> You might want to confirm that non-geo data can be added and queried.
> If only geo data isn't working then try stopping Tomcat and modifying
> your
> "/webapps/web.rya/WEB-INF/spring/spring-mongodb-geo.xml" file 
> (back it up first).
>
> Change the line:
>  factory-method="getInstance">
> To:
>  factory-method="getInstance">
>
> Save the file and then restart Tomcat and try that out.  Hope that helps.
>
> Thanks,
> -Eric White
>
> -Original Message-
> From: Joost Farla <jo...@apiwise.nl>
> Sent: Wednesday, May 09, 2018 3:28 AM
> To: dev@rya.incubator.apache.org
> Subject: Re: How to enable GeoSPARQL support for endpoint on MongoDB?
>
> Hi Caleb,
>
> Thanks for your suggestion! I've performed a rebuild with only the
> geoindexing profile, but still no luck
>
> Any clue?
>
> Cheers, Joost
>
>
>
> 2018-05-08 18:43 GMT+02:00 Meier, Caleb <caleb.me...@parsons.com>:
>
> > Hey Joost,
> >
> > After glancing at the pom file for web.rya, it appears that you are
> > enabling two profiles that will build different versions of the .war.
> > Have a look at the two profiles that appear at lines 189 and 196 in
> > the web.rya pom in the following link:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_meie
> > rc
> > aleb_incubator-2Drya_blob_master_web_=DwIFaQ=Nwf-pp4xtYRe0sCRVM8
> > _L
> > WH54joYF7EKmrYIdfxIq10=RaJkRMooYbg4vmML14E10F9hYEBLOeOHS3mAimFNgqQ
> > 
> > =aMq-SY6ieesyfCsAA4jaNiCdWdoFihroeUYZKwuHDXQ=Jew4790glP7fcpwxQGsMS
> > x2
> > qwsReekxD5Kt48lfLD0c=
> > web.rya/pom.xml
> >
> > In particular, -P mongodb will build and deploy a mongo backed web
> > service with no geo enabled, and -P geoindexing deploys a  mongo
> > backed web service with geo indexing enabled.  Could you try
> > building using only the geoindexing profile?  Hopefully that helps.
> >
> > Caleb
> >
> > Caleb A. Meier, Ph.D.
> > Senior Software Engineer ♦ Analyst
> > Parsons Corporation
> > 1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
> > Office:  (703)797-3066
> > caleb.me...@parsons.com ♦ www.parsons.com
> >
> > -Original Message-
> > From: Joost Farla <jo...@apiwise.nl>
> > Sent: Sunday, May 06, 2018 5:29 AM
> > To: dev@rya.incubator.apache.org
> > Subject: How to enable GeoSPARQL support for endpoint on MongoDB?
> >
> > Hi there,
> >
> > I've recently started experimenting with Rya on MongoDB. I've been
> > able to load geospatial data into MongoDB. The rya__triples and
> > rya_rya_geo collections are populated without issues.
> >
> > However, when I try to use GeoSPARQL functions via the provided
> > SPARQL endpoint implementation (web.rya), I get an empty result-set.
> > I've also tried to query using RDF4J directly, but same result.
> >
> > I'm using the latest master (4.0.0-SNAPSHOT) and I've built the .war
> with:
> >
> > mvn clean install -P mongodb -P geoindexing -DskipTests
>

RE: How to enable GeoSPARQL support for endpoint on MongoDB?

[Meier, Caleb]

Hey Joost,

After glancing at the pom file for web.rya, it appears that you are enabling 
two profiles that will build different versions of the .war.  Have a look at 
the two profiles that appear at lines 189 and 196 in the web.rya pom in the 
following link:

https://github.com/meiercaleb/incubator-rya/blob/master/web/web.rya/pom.xml

In particular, -P mongodb will build and deploy a mongo backed web service with 
no geo enabled, and -P geoindexing deploys a  mongo backed web service with geo 
indexing enabled.  Could you try building using only the geoindexing profile?  
Hopefully that helps.

Caleb

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Joost Farla 
Sent: Sunday, May 06, 2018 5:29 AM
To: dev@rya.incubator.apache.org
Subject: How to enable GeoSPARQL support for endpoint on MongoDB?

Hi there,

I've recently started experimenting with Rya on MongoDB. I've been able to load 
geospatial data into MongoDB. The rya__triples and rya_rya_geo collections are 
populated without issues.

However, when I try to use GeoSPARQL functions via the provided SPARQL endpoint 
implementation (web.rya), I get an empty result-set. I've also tried to query 
using RDF4J directly, but same result.

I'm using the latest master (4.0.0-SNAPSHOT) and I've built the .war with:

mvn clean install -P mongodb -P geoindexing -DskipTests


Env config (relevant part):

sc.useMongo=true
sc.use_geo=true
sc.geo.predicates=https://urldefense.proofpoint.com/v2/url?u=http-3A__www.opengis.net_ont_geosparql-23asWKT=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=hL9E1Bkzma7jWCW41bMKQOYWz2WY8WLuFGPmqH4hrdM=SJ_BJ1r2sYikKHP-BDWHYi8sdx-JPGSFvLqcpH-Yg0I=
mongo.db.collectionprefix=rya_
mongo.geo.maxdist=1e-10


The test data:

@prefix geo: 

 .
@prefix ex: 

 .

ex:Foo geo:hasGeometry ex:FooGeometry.
ex:FooGeometry geo:asWKT "POINT(5.091025039849683 
51.55845016358455)"^^geo:wktLiteral.


The test query:

PREFIX geo: 

PREFIX geof: 


SELECT ?s ?wkt
WHERE {
  ?s geo:asWKT ?wkt .
  FILTER(geof:sfWithin(?wkt, "POLYGON((5.034360992118195
51.595144381441415,5.149717437430695 51.595144381441415,5.149717437430695
51.52086334303003,5.034360992118195 51.52086334303003,5.034360992118195
51.595144381441415))"^^geo:wktLiteral))
}


The indexed POINT geometry is located within the provided POLYGON.
Therefore, I would expect one binding-set as result.

What should I do to get this working? Thanks!!

NOTICE: This email message and all attachments transmitted with it may contain 
privileged and confidential information, and information that is protected by, 
and proprietary to, Parsons Corporation, and is intended solely for the use of 
the addressee for the specific purpose set forth in this communication. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any reading, dissemination, distribution, copying, or other use of this 
message or its attachments is strictly prohibited, and you should delete this 
message and all copies and backups thereof. The recipient may not further 
distribute or use any of the information contained herein without the express 
written authorization of the sender. If you have received this message in 
error, or if you have any questions regarding the use of the proprietary 
information contained therein, please contact the sender of this message 
immediately, and the sender will provide you with further instructions.

RE: [VOTE] Release Apache Rya (incubating) 3.2.12 RC2

[Meier, Caleb]

Sigs and hashes verified.  Successful build on Centos with ITs and geo enabled. 
 

(+1 Binding)

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Jeff Dasch [mailto:hcs...@gmail.com] 
Sent: Friday, February 23, 2018 11:18 AM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC2

+1 (non-binding)

Verified sigs/checksums match for source release and maven artifacts.
Built on CentOS 7.3.1611 with Maven 3.3.9 and Oracle JDK 1.8.0_144 on a fresh 
repo.  Also built with -P geoindexing,benchmark,giraph

The only potential blocker I see is the Windows issues, but I'm fine marking 
that as a known issue in the release notes and fixing it for our next release.  
I created RYA-470 to track this issue -- it includes adding a Windows CI build 
to help prevent regression.

I also added RYA-471 to track Dave's feedback on a JDK9 build.  I don't think 
the lack of Java 9 build support is a blocker for this release but should be 
documented in the release notes and fixed for the next release.


On Tue, Feb 20, 2018 at 11:26 AM, Adina Crainiceanu  wrote:

> Rya community,
>
> I am pleased to be calling this vote for the source release of Apache 
> Rya (Incubating), version 3.2.12.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_r
> epos_dist_dev_incubator_rya_rya-2Dinc=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_L
> WH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8
> =YZm4gy-H7dtFTfznkcTYH1g_lHuhQPbKV35YdP9AYTA=W-j1sUX_yai_n8fwo8vunvg
> fJcntqEtedWyuvgIPbyI=
> ubating-3.2.12-rc2/
>
> Ancillary artifacts such as poms, jars, wars, etc. can be found here:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache
> .org_content_repositories_orgapache=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH
> 54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=Y
> Zm4gy-H7dtFTfznkcTYH1g_lHuhQPbKV35YdP9AYTA=iR4qVbO_jI63ZM71PWPA0uUzI
> XN_y0tImSAB6w1TlCI=
> rya-1010/org/apache/rya/
>
> The Git tag is rya-incubating-3.2.12-rc2 The Git commit ID is 
> edb9aa6f9d3479f22a8d17dae928d2ca19e5de37
> https://urldefense.proofpoint.com/v2/url?u=https-3A__git-2Dwip-2Dus.ap
> ache.org_repos_asf-3Fp-3Dincubator-2Drya.git=DwIBaQ=Nwf-pp4xtYRe0s
> CRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXT
> D0qo8=YZm4gy-H7dtFTfznkcTYH1g_lHuhQPbKV35YdP9AYTA=vSTkqNS3ZkvAHsBm
> fcaK2LdKZYrMpXtoJe-rhYnuo5U=;
> a=commit;h=edb9aa6f9d3479f22a8d17dae928d2ca19e5de37
>
>
> Checksums of rya-project-3.2.12-source-release.zip:
> SHA512:
> a0e87e1b3813e1425bf58e5e66e8cf8f948a1157f6905a55c913d4169dfb
> 8cfa05fa7c77514c2f75e414654198f9674533227a15ceee2fb6835e15777a0c48d8
> SHA1: 58128bf6cc5c8d92e429bd3a26aa1c104c757097
> MD5: 6e70b0d5aa54a4f018d5c12464e774e3
>
> Release artifacts are signed with the following key:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__people.apache.org
> _keys_committer_adina.asc=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKm
> rYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=YZm4gy-H7dt
> FTfznkcTYH1g_lHuhQPbKV35YdP9AYTA=Xty-LbT9Zw2Acfh8ZVbsAUxius_NK8cTWcW
> oUjyyF24=
>
> KEYS file available here:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_r
> epos_dist_release_incubator_rya_KEYS=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LW
> H54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=
> YZm4gy-H7dtFTfznkcTYH1g_lHuhQPbKV35YdP9AYTA=GKg5NtcVK7SPY1jJkfe4rcj_
> V5fL3jFdMGScKWcybLM=
>
> Issues that were closed/resolved for this release are here:
> *https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.or
> g_jira_secure_ReleaseNote.jspa-3Fproj=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_L
> WH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8
> =YZm4gy-H7dtFTfznkcTYH1g_lHuhQPbKV35YdP9AYTA=e-0VLfZnzmearmACjPtIGO8
> GnGJU2X_EtZXTyPKcjBs=
> ectId=12319020=12341570
>  g_jira_secure_ReleaseNote.jspa-3Fproj=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_L
> WH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8
> =YZm4gy-H7dtFTfznkcTYH1g_lHuhQPbKV35YdP9AYTA=e-0VLfZnzmearmACjPtIGO8
> GnGJU2X_EtZXTyPKcjBs=
> ectId=12319020=12341570>*
>
> Issues closed/resolved between RC1 and RC2 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org
> _jira_browse_RYA-2D468=DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYI
> dfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=YZm4gy-H7dtFTf
> znkcTYH1g_lHuhQPbKV35YdP9AYTA=NHR2uEhWxQpnF1XbWDmY2dO-ZvssxTyLPpvlD_
> 8hp4k=
>
>
> The vote will be open for at least 72 hours (until Friday, February 
> 23,
> 2018 1200 ET).
> Please download the release candidate and evaluate the necessary items 
> including checking hashes, signatures, build from source, and test.  

RE: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

[Meier, Caleb]

-1 (binding)

I agree that we should fix the licensing and build issues for this release so 
that we can move onto graduation.

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Adina Crainiceanu [mailto:ad...@usna.edu] 
Sent: Friday, February 16, 2018 11:21 AM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Apache Rya (incubating) 3.2.12 RC1

-1 from me. I think we should fix the licensing, release without any licensing 
issues, and then graduate very soon :)

I'll send an email to close the vote and start another release candidate.

Thank you.

On Fri, Feb 16, 2018 at 11:16 AM, Puja Valiyil  wrote:

> +1 (binding).
> There are two known issues with RC1:
> The licensing issue with Giraph:  This can be fixed in a future 
> release prior to graduation.
> Not being able to build under Windows:  Again, not clear if this is an 
> issue since no one is responding to the other thread about the issue.  
> So I will say Windows support is not a deal breaker here.
>
> On Thu, Feb 15, 2018 at 7:13 PM, Josh Elser  wrote:
>
> > IIRC, the findbugs-annotation artifact is dubious at best in terms 
> > of licensing. I think the "intent" was that it was compatibly 
> > licensed, but the artifacts in Maven totally had it mislabeled.
> >
> > Not something that needs to block your release now, but you should 
> > be taking this up to make sure are I want y'all to graduate soon :)
> >
> >
> > On 2/14/18 11:29 AM, Jeff Dasch wrote:
> >
> >> I just dug through some emails and we did identify this in 3.2.11-RC2.
> We
> >> had a number of other licensing issues on that RC so it is not 
> >> clear to
> me
> >> if this particular finding got dropped, or was determined to be a 
> >> non-issue.  Regardless, this same issue does affect the 3.2.11 release.
> >>
> >> On Wed, Feb 14, 2018 at 10:57 AM, Puja Valiyil 
> wrote:
> >>
> >> I’m confused because that project was in our previous release.  
> >> Didn’t
> we
> >>> upgrade the version of giraph to fix this or am I misremembering?
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Feb 14, 2018, at 10:37 AM, Jeff Dasch  wrote:
> 
>  Again, not sure if this license thing is a blocker.  But if it 
>  is, I
> put
> 
> >>> up
> >>>
>  PR-274 as a fix: 
>  https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_a
>  pache_incubator-2Drya_pull_274=DwIFaQ=Nwf-pp4xtYRe0sCRVM8_LWH
>  54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo
>  8=rJpSvZFMvmPo3jFa4QbcgANvKeOpOH_KwouvUS_c3Ek=o6vO6bBa0jDTynG
>  HRmZ8_fDOnNOCrx-srgmEFNVLRjg=
> 
> 
>  On Tue, Feb 13, 2018 at 4:37 PM, Jeff Dasch  wrote:
> >
> > I'm not voting yet, but I did run a license check and got a hit 
> > on
> > this:
> > (GNU Lesser Public License) FindBugs-Annotations
> > (com.google.code.findbugs:annotations:2.0.2 -
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__findbugs.sou
> > rceforge.net_=DwIFaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfx
> > Iq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=rJpSvZFMvmP
> > o3jFa4QbcgANvKeOpOH_KwouvUS_c3Ek=8crfbvCjZv-O9e6T3ASaH2-kAAFnC
> > yKhhS5Bky8dnzA=)
> >
> > which comes from Apache Giraph
> > [INFO] org.apache.rya:rya.giraph:jar:3.2.12-incubating
> > [INFO] +- org.apache.giraph:giraph-core:jar:1.2.0:compile
> > [INFO] |  +- 
> > com.google.code.findbugs:annotations:jar:2.0.2:compile
> >
> > I'm pretty sure we ran into this during the last release.  Are 
> > we
> still
> > good to go on this RC, or do we need to cut a new one that has a
> giraph
> > profile?
> >
> >
> >
> > On Mon, Feb 12, 2018 at 8:51 PM, Adina Crainiceanu 
> > 
> >>
> > wrote:
> >>>
> 
> >> Rya community,
> >>
> >> I am pleased to be calling this vote for the source release of
> Apache
> >>
> > Rya
> >>>
>  (Incubating), version 3.2.12.
> >>
> >> The source zip, including signatures, digests, etc. can be found at:
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apach
> >> e.org_repos_dist_dev_incubator_rya_rya-2D=DwIFaQ=Nwf-pp4xtY
> >> Re0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7Cr
> >> MHCgeo_4WXTD0qo8=rJpSvZFMvmPo3jFa4QbcgANvKeOpOH_KwouvUS_c3Ek&
> >> s=kyxk7CSfvebi0hIqyQQSZExbKVYH-sLAn0yc4O1rzlo=
> >> incubating-3.2.12-rc1/
> >>
> >> Ancillary artifacts such as poms, jars, wars, etc. can be found
> here:
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__repository
> >> .apache.org_content_repositories_=DwIFaQ=Nwf-pp4xtYRe0sCRVM
> >> 8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4
> >> 

RE: First day with RYA questions.

[Meier, Caleb]

Have you tried running git clean -fdx?  There might be some files left over 
from a previous build or from your IDE.

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Geoffry Roberts [mailto:threadedb...@gmail.com] 
Sent: Tuesday, February 13, 2018 11:46 AM
To: dev@rya.incubator.apache.org
Subject: First day with RYA questions.

All,

I have a good use case for RYA.  I hope I can get it working.  This is my first 
day with the project and I have a few questions.

I tried to run $ mvn clean install.  Each sub build succeeded until *Apache Rya 
Extra Projects* It then complains about *Too many files with unapproved 
license:* What does this mean and how to fix?  I see the list in rat.txt.  What 
do I do about it?

I see RYA uses an older version of Accumulo.  Is this required?  I am running 
something newer (1.8.1).

Is MongoDB required? or is it an alternative to Accumulo?

Thanks

--
There are ways and there are ways,

Geoffry Roberts

RE: [VOTE] Release Rya (Incubating) version 3.2.11 RC3

[Meier, Caleb]

+1 (binding)

Verified sigs, hashes, and build.

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Puja Valiyil [mailto:puja...@gmail.com] 
Sent: Thursday, September 28, 2017 8:35 PM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC3

+1 (binding)

Sent from my iPhone

> On Sep 28, 2017, at 5:11 PM, Jeff Dasch  wrote:
> 
> +1 (non-binding)
> 
> Verified sigs/checksums match for source release and maven artifacts.
> Built with all tests on CentOS 7.3.1611 with Maven 3.3.9 and Oracle 
> JDK
> 1.8.0_144 on a fresh repo.  Also built with -P geoindexing,benchmark.
> 
>> On Tue, Sep 26, 2017 at 1:27 PM, David Lotts  wrote:
>> 
>> I am pleased to be calling this vote for the source release of Apache 
>> Rya (Incubating), version 3.2.11.
>> 
>> The source zip, including signatures, digests, etc. can be found at:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_
>> repos_dist_dev_incubator_rya_rya-2D=DwICAg=Nwf-pp4xtYRe0sCRVM8_LW
>> H54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8
>> =3fuNCnUTiPYAZaX4NIZ4eJ5UatM8r4w0kkFBHWzDh-k=FKW-S-2khBFm_YaZNTCySx
>> 61U9mFREWDbGIpT3Al1IQ=
>> incubating-3.2.11-rc3/
>> 
>> 
>> Ancillary artifacts such as poms, jars, wars. can be found here:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apach
>> e.org_content_repositories_=DwICAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7
>> EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=3fuNCnU
>> TiPYAZaX4NIZ4eJ5UatM8r4w0kkFBHWzDh-k=ZDQqrfyAegIO4cw1csaJKBNCIaHTxi
>> wO66flGHGVaFU= 
>> orgapacherya-1008/org/apache/rya/rya-project/3.2.11-incubating/
>> 
>> The Git tag is rya-incubating-3.2.11-rc3 The Git commit ID is 
>> afe522412fb74cbb4ab97e1b7a8d1c112be33773
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__git-2Dwip-2Dus.a
>> pache.org_repos_asf-3Fp-3Dincubator-2Drya.git-3Ba-3Dcommit-3Bh-3D=D
>> wICAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5
>> STiFwDpzJ7CrMHCgeo_4WXTD0qo8=3fuNCnUTiPYAZaX4NIZ4eJ5UatM8r4w0kkFBHW
>> zDh-k=gnYHkeVqkQ1EFNrqFn6MnuXLQ5hqT-HQlnbo_okWCLg=
>> afe522412fb74cbb4ab97e1b7a8d1c112be33773
>> 
>> 
>> Checksums of rya-project-3.2.11-source-release.zip:
>> MD5: 3968cfb695a5740cac6acb3c33b702ca
>> SHA1: d601431c06d9adb3336c2913cc544bd9b43c0d7a
>> SHA512: b6ae761aa42f80e1cb84bb645184e29e4436eaaaf66aa7249aa65b6adb38
>> f3dfdd9a6f8b536eb0e2de88ac75cc2a0c8d97d85b4dd0ffef7f9407e05642110b3f
>> 
>> Release artifacts are signed with the following key:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__people.apache.or
>> g_keys_committer_dlotts.asc=DwICAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7
>> EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=3fuNCnU
>> TiPYAZaX4NIZ4eJ5UatM8r4w0kkFBHWzDh-k=d7SDM_0ihpYKjFWiGhTNGCToMfBgaE
>> hPIyytXsTSqT8=
>> 
>> KEYS file available here:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_
>> repos_dist_release_incubator_rya_KEYS=DwICAg=Nwf-pp4xtYRe0sCRVM8_
>> LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8
>> =3fuNCnUTiPYAZaX4NIZ4eJ5UatM8r4w0kkFBHWzDh-k=Lv-4FMQ8DD9ujXySnUDF
>> E34d3ZzxN8AW85I2JmJA4D0=
>> 
>> Issues that were closed/resolved for this release are here:
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.or
>> g_jira_secure_ReleaseNote.jspa-3Fproje=DwICAg=Nwf-pp4xtYRe0sCRVM8
>> _LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo
>> 8=3fuNCnUTiPYAZaX4NIZ4eJ5UatM8r4w0kkFBHWzDh-k=Btz5s8qy-Vw_AKhKTJX
>> CfoBbVTQnk8vZ12Dag-Wkcjw=
>> ctId=12319020=12341279
>> 
>> 
>> The vote will be open for at least 72 hours starting Tuesday 2pm 
>> 9/26/2017 and close at Friday 9/29/2017 2pm Eastern Time USA.
>> Please download the release candidate and evaluate the necessary 
>> items including checking hashes, signatures, build from source, and 
>> test.  Then please vote:
>> 
>> [ ] +1 Release this package as rya-project-3.2.11 [ ] +0 no opinion [ 
>> ] -1 Do not release this package because because...
>> 

RE: Loading tab spaced data

[Meier, Caleb]

Hey Matteo, 

Do you know offhand how many triples are included in your dataset?  Also, can 
you send a stack trace?  How are you converting your Parquet file to one of the 
formats supported by the RdfIngestTool (n-triples, trig, ...)?

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Matteo Cossu [mailto:elco...@gmail.com] 
Sent: Tuesday, August 29, 2017 10:36 AM
To: dev@rya.incubator.apache.org
Subject: Re: Loading tab spaced data

Hello Caleb,
I was trying to load a 53GB file (in parquet format) with 10 containers with 
assigned 15GB of memory each.
Does someone have some reference numbers, like how how big a dataset can be 
with these resources?
This could help me to know when the problem is entirely mine, that is probable 
since with many of the tools I'm using (accumulo for example) I'm still a 
novice.

Thank you all for the answers,
Matteo Cossu


On 29 August 2017 at 16:12, Meier, Caleb <caleb.me...@parsons.com> wrote:

> Hello Matteo,
>
> Were you using the MapReduce ingest tool when you were running out of 
> memory?  If so, do you know big the file was that you were ingesting, 
> how many containers Yarn allocated to your job, and how much memory 
> was allocated to each container?
>
> Caleb A. Meier, Ph.D.
> Senior Software Engineer ♦ Analyst
> Parsons Corporation
> 1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
> Office:  (703)797-3066
> caleb.me...@parsons.com ♦ www.parsons.com
>
> -Original Message-
> From: Matteo Cossu [mailto:elco...@gmail.com]
> Sent: Monday, August 28, 2017 8:04 PM
> To: dev@rya.incubator.apache.org
> Subject: Re: Loading tab spaced data
>
> I would like to help, but I still can't even test Rya properly. I'm 
> developing for research a similar system (using Spark SQL) and I 
> wanted to compare my software performances with Rya on the University Cluster.
> When I try to use these Rya tools for loading the data with the big 
> datasets, it always crashes (mostly out of memory problems) and it 
> doesn't complete the loading. At the moment, I have the urgency of 
> publishing some results, so I am comparing my software with other systems.
> Later, I could go back on Rya and try to solve some bugs along the way 
> :P
>
> Best Regards,
> Matteo Cossu
>
> On 29 August 2017 at 01:29, Josh Elser <els...@apache.org> wrote:
>
> > Hi Matteo,
> >
> > Thanks for the bug-report. Do you have an interest in making the 
> > change to Rya to address this issue? :)
> >
> > In open source projects, we like to encourage users to make changes 
> > to "scratch their own itch". Please let us know how we can help 
> > enable you to make this change.
> >
> > On 8/25/17 8:45 AM, Matteo Cossu wrote:
> >
> >> Hello,
> >> I have some problems in loading the data with the Map Reduce code 
> >> provided.
> >> I am using this class:
> >> *org.apache.rya.accumulo.mr.tools.RdfFileInputTool
> >> .*
> >> When my input data is in N-Triples format and the triples are tab 
> >> separated instead of spaces, I get this error:
> >>
> >> *org.openrdf.rio.RDFParseException: Expected '<', found: m* I 
> >> solved by substituting all the tabs with spaces in my input data, 
> >> but since tabs are a possible separator in the N-Triples format, I 
> >> think this should be implemented (or fixed) directly within the tool.
> >>
> >> Kind Regards,
> >> Matteo Cossu
> >>
> >>
>

RE: Loading tab spaced data

[Meier, Caleb]

Hello Matteo,

Were you using the MapReduce ingest tool when you were running out of memory?  
If so, do you know big the file was that you were ingesting, how many 
containers Yarn allocated to your job, and how much memory was allocated to 
each container?  

Caleb A. Meier, Ph.D.
Senior Software Engineer ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Matteo Cossu [mailto:elco...@gmail.com] 
Sent: Monday, August 28, 2017 8:04 PM
To: dev@rya.incubator.apache.org
Subject: Re: Loading tab spaced data

I would like to help, but I still can't even test Rya properly. I'm developing 
for research a similar system (using Spark SQL) and I wanted to compare my 
software performances with Rya on the University Cluster.
When I try to use these Rya tools for loading the data with the big datasets, 
it always crashes (mostly out of memory problems) and it doesn't complete the 
loading. At the moment, I have the urgency of publishing some results, so I am 
comparing my software with other systems.
Later, I could go back on Rya and try to solve some bugs along the way :P

Best Regards,
Matteo Cossu

On 29 August 2017 at 01:29, Josh Elser  wrote:

> Hi Matteo,
>
> Thanks for the bug-report. Do you have an interest in making the 
> change to Rya to address this issue? :)
>
> In open source projects, we like to encourage users to make changes to 
> "scratch their own itch". Please let us know how we can help enable 
> you to make this change.
>
> On 8/25/17 8:45 AM, Matteo Cossu wrote:
>
>> Hello,
>> I have some problems in loading the data with the Map Reduce code 
>> provided.
>> I am using this class: 
>> *org.apache.rya.accumulo.mr.tools.RdfFileInputTool
>> .*
>> When my input data is in N-Triples format and the triples are tab 
>> separated instead of spaces, I get this error:
>>
>> *org.openrdf.rio.RDFParseException: Expected '<', found: m* I solved 
>> by substituting all the tabs with spaces in my input data, but since 
>> tabs are a possible separator in the N-Triples format, I think this 
>> should be implemented (or fixed) directly within the tool.
>>
>> Kind Regards,
>> Matteo Cossu
>>
>>

RE: Podling Report Reminder - July 2017

[Meier, Caleb]

Adina is on vacation until the end of July.  So she is unavailable to work on 
it.

Caleb A. Meier, Ph.D.
Software Engineer II ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Puja Valiyil [mailto:puja...@gmail.com] 
Sent: Thursday, June 29, 2017 9:14 PM
To: dev@rya.incubator.apache.org
Subject: Re: Podling Report Reminder - July 2017

Has anyone started working on this or would like to volunteer to put it 
together?  I didn't see anything from Adina saying if she had been working on 
it or not.

Sent from my iPhone

> On Jun 29, 2017, at 8:51 PM, johndam...@apache.org wrote:
> 
> Dear podling,
> 
> This email was sent by an automated system on behalf of the Apache 
> Incubator PMC. It is an initial reminder to give you plenty of time to 
> prepare your quarterly board report.
> 
> The board meeting is scheduled for Wed, 19 July 2017, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC 
> report. The Incubator PMC requires your report to be submitted 2 weeks 
> before the board meeting, to allow sufficient time for review and 
> submission (Wed, July 05).
> 
> Please submit your report with sufficient time to allow the Incubator 
> PMC, and subsequently board members to review and digest. Again, the 
> very latest you should submit your report is 2 weeks prior to the 
> board meeting.
> 
> Thanks,
> 
> The Apache Incubator PMC
> 
> Submitting your Report
> 
> --
> 
> Your report should contain the following:
> 
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
>the project or necessarily of its field
> *   A list of the three most important issues to address in the move
>towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
>aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.apache.org_i
> ncubator_July2017=CwIFAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq
> 10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=flalrOvFDeLMSCH8lQT
> PrIxrM9msw2zGlvhUVqX5zHw=Bg6BsDNSH_cDn72IjWIW2yBbeUafd1Q8Q6QSIO21hm4
> =
> 
> Note: This is manually populated. You may need to wait a little before 
> this page is created from a template.
> 
> Mentors
> ---
> 
> Mentors should review reports for their project(s) and sign them off 
> on the Incubator wiki page. Signing off reports shows that you are 
> following the project - projects that are not signed may raise alarms 
> for the Incubator PMC.
> 
> Incubator PMC

RE: Timestamps and Cardinality in Queries

[Meier, Caleb]

Yes, that's a good place to start.  If you have external timestamps that are 
built into your graph using the time ontology in owl (e.g you have triples of 
the form (event123, time:inDateTime, 2017-02-23T14:29)), the temporal index is 
exactly what you want.  If you are hoping to query based on the internal 
timestamps that Accumulo assigns to your triples, then there are some slight 
tweaks that can be done to facilitate this, but it won't be nearly as efficient 
(this will require some sort of client side filtering).  

Caleb A. Meier, Ph.D.
Software Engineer II ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Liu, Eric [mailto:eric@capitalone.com] 
Sent: Thursday, February 23, 2017 2:27 PM
To: dev@rya.incubator.apache.org
Subject: Re: Timestamps and Cardinality in Queries

We’d like to be able to query by timestamp; specifically, we want to be able to 
find all statements that were made within a given time range. Is this what I 
should be looking at? 
https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_download_attachments_63407907_Rya-2520Temporal-2520Indexing.pdf-3Fversion-3D1-26modificationDate-3D1464789502000-26api-3Dv2=CwIGaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=BBheKpKX7A1Ijs8q_TDEUVtdfu-r015XHZjmcw6veAw=vLayAkLG0IKGE-0NbwRQKfpcfId05fXE5TX8oMJaa7Q=
 



On 2/22/17, 6:21 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.











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.

RE: January podling report draft - please comment

[Meier, Caleb]

I noticed that we only listed two important issues to be completed before 
graduation.  Maybe add something like "Continue to harden and develop core Rya 
features to improve user experience". 

Caleb A. Meier, Ph.D.
Software Engineer II ♦ Analyst
Parsons Corporation
1911 N. Fort Myer Drive, Suite 800 ♦ Arlington, VA 22209
Office:  (703)797-3066
caleb.me...@parsons.com ♦ www.parsons.com

-Original Message-
From: Adina Crainiceanu [mailto:ad...@usna.edu] 
Sent: Sunday, January 01, 2017 7:29 PM
To: dev@rya.incubator.apache.org
Subject: January podling report draft - please comment

Hi all,

Happy New Year!! I hope everyone had a chance to enjoy the holidays.

Below is the first draft of the podling report due on January 4th. Any comments 
and suggestions are welcome.


Rya

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that supports 
SPARQL queries. Rya is a scalable RDF data management system built on top of 
Accumulo. Rya uses novel storage methods, indexing schemes, and query 
processing techniques that scale to billions of triples across multiple nodes. 
Rya provides fast and easy access to the data through SPARQL, a conventional 
query mechanism for RDF data.

Rya has been incubating since 2015-09-18.

Three most important issues to address in the move towards graduation:

 1. Have more releases as part of the Apache Foundation  2. Increase diversity 
of contributors.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?

 No

How has the community developed since the last report?

 * New committer and PPMC member, David Lotts,  was invited and accepted to 
join Apache Rya PPMC.
 * Sean Busbey resigned as mentor
 * Billie Rinaldi became a mentor for Rya
 * Talk on Rya at Accumulo Summit, October 11, 2016
 * PRs from non-committers which are integrated into the repository continue to 
be received

How has the project developed since the last report?

 * We had the first release as part of the ASF
 * Resolved a handful of issues that users have encountered
 * Committed features: implemented new commands for Rya console: AddUser (give 
perimssions to users for the tables associated with Rya instance), RemoveUser , 
Uninstall, LoadStatementsFile. Added merge tool to allow cloning between Mongo 
and Accumulo instances. Added initial Spark support.

Date of last release:

 Oct 28, 2016

When were the last committers or PMC members elected?

 New committer and PPMC member David Lotts elected on Oct 25, 2016

Signed-off-by:

  [ ](rya) Josh Elser
  [ ](rya) Edward J. Yoon
  [ ](rya) Venkatesh Seetharam
  [ ](rya) Billie Rinaldi


Shepherd/Mentor notes:

--
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department United States Naval Academy
410-293-6822
ad...@usna.edu
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.usna.edu_Users_cs_adina_=CwIFaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=ZFNmd4En_Cf6Hlt2rezwksDd4a4jMszeTFXFM5wEmOE=p3avIUOnrqFQiSqTIToUqljnS8TxRHnN1mHim0kbLLs=
 

RE: [VOTE] Release Rya (Incubating) version 3.2.10 RC3

[Meier, Caleb]

+1 (binding)

Everything built fine.  The signatures and hashes were correct, and there were 
no extra binaries.  At the bottom of the e-mail are the remaining licenses that 
don't
fall into the "good" list of ASF pre-approved licenses.  These were obtained by 
running 

mvn license:aggregate-add-third-party

and then 

egrep -iv "BSD|ASF|MIT|CDDL|EPL|Apache|Eclipse|Public Domain" 
target/generated-sources/license/THIRD-PARTY.txt

I'm assuming that these have been signed off on by Josh, Puja, and Aaron.

 (Unknown license) ASM Core (asm:asm:3.1 - http://asm.objectweb.org/asm/)
 (GNU LESSER GENERAL PUBLIC LICENSE) JCalendar (com.toedter:jcalendar:1.1.4 
- http://www.toedter.com/en/jcalendar/)
 (Unknown license) commons-beanutils 
(commons-beanutils:commons-beanutils:1.7.0 - no url defined)
 (HSQLDB License) HSQLDB (hsqldb:hsqldb:1.8.0.10 - http://hsqldb.org/)
 (Unknown license) servlet-api (javax.servlet:servlet-api:2.5 - no url 
defined)
 (Unknown license) jsp-api (javax.servlet.jsp:jsp-api:2.1 - no url defined)
 (Common Public License Version 1.0) JUnit (junit:junit:4.8.2 - 
http://junit.org)
 (ASL, version 2) (LGPL, version 2.1) Java Native Access 
(net.java.dev.jna:jna:4.0.0 - https://github.com/twall/jna)
 (ASL, version 2) (LGPL, version 2.1) Java Native Access Platform 
(net.java.dev.jna:jna-platform:4.0.0 - https://github.com/twall/jna)
 (Unknown license) Antlr 3.4 Runtime (org.antlr:antlr-runtime:3.4 - 
http://www.antlr.org)
 (Unknown license) Jettison (org.codehaus.jettison:jettison:1.1 - no url 
defined)
 (GNU General Public License (GPL), version 2, with the Classpath 
exception) JMH Core (org.openjdk.jmh:jmh-core:1.13 - 
http://openjdk.java.net/projects/code-tools/jmh/jmh-core/)
 (GNU General Public License (GPL), version 2, with the Classpath 
exception) JMH Generators: Annotation Processors 
(org.openjdk.jmh:jmh-generator-annprocess:1.13 - 
http://openjdk.java.net/projects/code-tools/jmh/jmh-generator-annprocess/)
 (Unknown license) org.osgi.compendium (org.osgi:org.osgi.compendium:4.2.0 
- no url defined)
 (Unknown license) org.osgi.core (org.osgi:org.osgi.core:4.2.0 - no url 
defined)
 (Unknown license) spring-aop (org.springframework:spring-aop:3.0.5.RELEASE 
- no url defined)
 (Unknown license) spring-asm (org.springframework:spring-asm:3.0.5.RELEASE 
- no url defined)
 (Unknown license) spring-context-support 
(org.springframework:spring-context-support:3.0.7.RELEASE - no url defined)
 (Unknown license) spring-tx (org.springframework:spring-tx:3.0.5.RELEASE - 
no url defined)
 (Unknown license) oro (oro:oro:2.0.8 - no url defined)
 (Unknown license) regexp (regexp:regexp:1.3 - no url defined)
 (Unknown license) jasper-compiler (tomcat:jasper-compiler:5.5.12 - no url 
defined)
 (Unknown license) jasper-runtime (tomcat:jasper-runtime:5.5.12 - no url 
defined)

-Original Message-
From: Aaron D. Mihalik [mailto:aaron.miha...@gmail.com] 
Sent: Monday, October 24, 2016 3:30 PM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Rya (Incubating) version 3.2.10 RC3

This is a gentle reminder to everyone to provide some feedback on the release 
candidate.  We need at least another binding vote to continue this process.

Also, non-binding votes are encouraged :)

Josh/Adina: I have looked at your feedback and made minor updates, tickets, and 
comments to address the issues you raised:


> [Josh] Apache Accumulo®, please

I have updated the website accordingly

> [Josh] lots of warnings in your Maven project

Created a Jira issue for this: RYA-216 - Clean up Maven Warnings

> [Josh] include when the 72hrs is "up" (with tz)

I updated the template

> [Adina] Maybe we should put the KEYS file both in
dist.a.o/repos/dist/dev/ and dist.a.o/repos/dist/release/

Initially, I had the KEYS file in both places but I noticed that most projects 
only have it in "release" and I thought it might be confusing to maintain two 
files with the same content.  I'm fine reverting back to both places, however.  
Let me know.


> [Josh] you have no other signatures on your key

David Lotts signed my key last week.  I updated dist.a.o [1] but my key on 
people.a.o [2] is doesn't reflect David's signature.  Any idea how to push an 
update?  The key server that people.a.o pulls from has the update [3].

> [Josh] Put some thought in how your source-release creates binaries

Agreed... created RYA-217 Evaluate Shaded and Zip'd artifacts


--Aaron


[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_release_incubator_rya_KEYS=CwIFaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=ZfEFJtjCrTqWYlOG5OQ1anhuoUqfwnAT5VIhodw6Bys=oRAGQlItutHUnC5pj152XKymSWuxBwgqInEwC-XkZBc=
[2] 

RE: [VOTE] Release Rya (Incubating) version 3.2.10 RC2

[Meier, Caleb]

-1 because of the findbugs issue.  Also, Rat failed on Mongo, animal sniffer 
failed on Tinkerpop.Rya,
And there was a test failure (CopyToolTest.testImportDirectoryTool) for the 
merge tool.  Stopped building when I encountered the test failure.

-Original Message-
From: Aaron D. Mihalik [mailto:aaron.miha...@gmail.com] 
Sent: Monday, October 17, 2016 11:15 AM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Rya (Incubating) version 3.2.10 RC2

-1 We're still including findbugs.

I'm sorry everyone.  I misread Josh's earlier email [1] and thought it was okay 
to continue to include findbugs for our first release,  I'll take a look at 
upgrading/changing findbugs and make an RC3 very soon.

If anyone has feedback for RC2, I'd appreciate hearing it and we'll include any 
additional changes in RC3.

--Aaron

[1] I misread "No, it's not ok :)" as "No, it's ok :)"

On Sun, Oct 16, 2016 at 11:41 PM Aaron D. Mihalik 
wrote:

> I am pleased to be calling this vote for the source release of Apache 
> Rya (Incubating), version 3.2.10.
>
> The source zip, including signatures, digests, etc. can be found at:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_r
> epos_dist_dev_incubator_rya_rya-2Dincubating-2D3.2.10-2Drc2_=CwIBaQ&
> c=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDp
> zJ7CrMHCgeo_4WXTD0qo8=5B5wGwyOCArNTRFe4dw7o-R1Jp_RPBr858cN0qc3W5w=
> C7BGxRv1vQtw01N9tu2Dg2rKSp9ALd-R9FGZ9X2-5M8=
>
> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__repository.apache
> .org_content_repositories_orgapacherya-2D1002_org_apache_rya_rya-2Dpro
> ject_3.2.10-2Dincubating_=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKm
> rYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=5B5wGwyOCAr
> NTRFe4dw7o-R1Jp_RPBr858cN0qc3W5w=hYxVfOHRLA-SolUgzoDoEQpvumIApUUyTZE
> Mz-LHub8=
>
> The Git tag is rya-incubating-3.2.10-rc2 The Git commit ID is 
> 9f0d63e6089df172eb3f41957d2956ec0035953a
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__git-2Dwip-2Dus.ap
> ache.org_repos_asf-3Fp-3Dincubator-2Drya.git-3Ba-3Dcommit-3Bh-3D9f0d63
> e6089df172eb3f41957d2956ec0035953a=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH5
> 4joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=5B
> 5wGwyOCArNTRFe4dw7o-R1Jp_RPBr858cN0qc3W5w=cHqWeFyrs_oQzu3N6tbbiSNO1l
> 933gbNSK5N39ZalNE=
>
> Checksums of rya-project-3.2.10-source-release.zip:
> SHA1: 5f91b695e5bebfa89eee27debfca7a264f81f888
> MD5: 5199aee4ca11e3c735f6e8b40f563f09
>
> Release artifacts are signed with the following key:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__people.apache.org
> _keys_committer_mihalik.asc=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7E
> KmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=5B5wGwyOC
> ArNTRFe4dw7o-R1Jp_RPBr858cN0qc3W5w=VMi5E5lunVMX9Uk4TdujTk0CdpGnwOyTe
> mvnAjQaDYY=
>
> KEYS file available here:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_r
> epos_dist_release_incubator_rya_KEYS=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LW
> H54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=
> 5B5wGwyOCArNTRFe4dw7o-R1Jp_RPBr858cN0qc3W5w=jdG1zzP2AYVlLfrMGJcepSQK
> wig16jBP9s35S98AUmw=
>
> Issues that were closed/resolved for this release are here:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org
> _jira_secure_ReleaseNote.jspa-3Fversion-3D12334209-26styleName-3DHtml-
> 26projectId-3D12319020=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYI
> dfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=5B5wGwyOCArNTR
> Fe4dw7o-R1Jp_RPBr858cN0qc3W5w=mPUiPXUr56EjCDWJ322o7v4M4ZxancHZMHuLlO
> KQj1E=
>
> Issues resolved between RC1 and RC2 are here:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org
> _jira_browse_RYA-2D184=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYI
> dfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=5B5wGwyOCArNTR
> Fe4dw7o-R1Jp_RPBr858cN0qc3W5w=j--Owd-ooFUYW3ZuD22H0sA-T9ci44jdMBzPsd
> glfE0=
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items 
> including checking hashes, signatures, build from source, and test.  
> The please vote:
>
> [ ] +1 Release this package as rya-project-3.2.10 [ ] +0 no opinion [ 
> ] -1 Do not release this package because because...
>

checklist for release

[Meier, Caleb]

Hello Everyone,

Here's a checklist for things to consider when evaluating the release candidate:

1. Download the sources and verify they compile cleanly.

2. Validate the hashes match.

3. Validate that the sources contain no unexpected binaries.
Run the find/grep command:  find . -type f  | grep -v 
'\/test\/\|\/site\/\|\.java\|\.xml\|\.xsl\|\.groovy\|\.properties\|\.sh\|\.bat\|\.md\|\.txt'
which looks for all files that don't have one of the approved extensions.

4. Validate the signature for the build and hashes.
Verify .asc files found at 
https://repository.apache.org/content/repositories/orgapacherya-1002/org/apache/rya/rya-project/3.2.10-incubating/
 using
the Aaron's public key: 
https://dist.apache.org/repos/dist/release/incubator/rya/KEYS .  Then verify 
hashes of these files.

5. Validate the LICENSE/NOTICE/Headers.
Verify that each project contains the ASF license and notice files.
Run the grep command:  fgrep -Ri 'copyright' rya-project-3.2.10 | fgrep -v 'The 
ASF licenses this file'
This should return only License and Notice files in rya-project-3.2.10. The 
license files
and the notice files should be consistent with the ASF license and ASF 
copyright statement.  Verify that only
the notice files contains the ASF copyright statement.

RE: SCM tagging conventions

[Meier, Caleb]

Given that you cannot delete the tag "rel/", what are the tagging 
conventions that people use throughout the release process?
Obviously you don't want the tag for an RC to be rel in the event that you have 
to create a new RC and delete the old tag.  Is the convention to just
create an RC tag, and once an RC passes vote then create the "rel/" 
tag?

-Original Message-
From: Josh Elser [mailto:josh.el...@gmail.com] 
Sent: Friday, October 14, 2016 6:00 PM
To: dev@rya.incubator.apache.org
Subject: Re: SCM tagging conventions

Yeah, making a release with a SNAPSHOT version doesn't make any sense (as 
SNAPSHOTs are explicitly for non-released versions of software).

At the ASF, the only thing to be aware of is that the final Git tag should be 
"rel/<whatever" which will prevent it from being force-push deleted.

Meier, Caleb wrote:
> What are the conventions for SCM tags?  Josh, was the issue that you had with 
> our tag that is was v3.2.10-SNAPSHOT as opposed to either v3.2.10 or just 
> 3.2.10?  I want to close out RYA-182, but first I want to understand what the 
> issue was.
>

RE: [DISCUSS] Path forward for release

[Meier, Caleb]

So just make sure I'm clear with what you said, I'll attempt to summarize.  For 
the purposes of a release, it's okay to include source code for components that 
have improperly licensed, Runtime dependencies, so long as they are "optional" 
and turned off by default.  But when we actually deploy our artifacts, we need 
to exclude the jars for all components that have improperly licensed 
dependencies.  So in effect, any components that have improperly licensed 
dependencies need to be truly optional from a build perspective -- have an 
optional build profile -- and should not be built and deployed by default.  

What we are currently working on is making geoindexing optional from a build 
perspective.  We're separating it out from the indexing project so that it can 
have its own, optional build profile.  If what I said above is correct, it 
seems like there is no way around this, other than making the entire indexing 
project optional.  But that would be like throwing the baby out with the bath 
water.  

From: Josh Elser [els...@apache.org]
Sent: Monday, October 10, 2016 10:26 AM
To: dev@rya.incubator.apache.org
Subject: Re: [DISCUSS] Path forward for release

Ok, I put some more thought into this one because it wasn't sitting
right with me. I think there are two main issues:

1) Is geoindexing actually "optional"

2) Would JARs be also published alongside the source release, and do
those JARs bundle these GPL-licensed dependencies.

Assuming #1 is "yes" (because I don't know it well enough technically),
If the geo-indexing modules are disabled by default, you can make the
release. I think this is what Venkatesh was getting at.

When you publish JARs, even though they are not an official release in
Apache's eyes (only source code is an Apache release -- everything else
is "supplemental" and not actually part of the release), you should
still make sure that they are being properly licensed. This also extends
to not being allowed to bundle Category-X dependencies (e.g. GPL). I
think this is how I noticed this in the first place.

I will leave the #1 discussion up to you all because I don't have enough
context -- should really get an answer in the spirit of the question:
"Is Rya useful if GeoIndexing is optional?". Meaning, will the people
using this release all be building the optional GeoIndexing support? In
this case, it's a core feature, and not an optional one.

Let me know if #2 is still not clear. I apologize for (likely) making
things more complicated.

Josh Elser wrote:
> No, you're correct. I am disagreeing with Venkatesh :). That's why I
> included documentation which outlines why I am disagreeing with him.
>
> Meier, Caleb wrote:
>> Unless I am misunderstanding something, which I probably am, it seems
>> like Venkatesh and Josh are saying conflicting things. Venkatesh seems
>> to be implying that the licenses for runtime dependencies do not need
>> to be taken into account, while Josh seems to be be saying that the
>> licenses of all artifacts created need to be compliant, and that the
>> licensing of those artifacts depends on the licensing of run time
>> dependencies. Am I missing something here?
>>
>> Regarding geoindexing and indexing, those projects are somewhat
>> coupled right now. Puja took steps to remove geoindexing from indexing
>> in an effort to carry out 2. Going forward it might be best to make
>> the indexes pluggable.
>>
>>
>>
>> Sent from my Verizon 4G LTE smartphone
>>
>>
>>  Original message 
>> From: Josh Elser<els...@apache.org>
>> Date: 10/8/16 3:54 PM (GMT-05:00)
>> To: dev@rya.incubator.apache.org
>> Subject: Re: [DISCUSS] Path forward for release
>>
>> Venkatesh is right in that the only "official" release in the ASF's eyes
>> is the source release. Any JARs you publish are supplementary and
>> technically not subject to the rules of Apache releases.
>>
>> The area I'm still trying to fully grok is that the source-release you
>> publish must also create artifacts which are properly licensed[1]. Right
>> now, that means including numerous incompatible dependencies, and, thus,
>> does not meet the requirements of the ASL and the ASF.
>>
>> Regarding David's last question: I would assume that the license applies
>> to both the source code and binary forms of the geo-related artifacts
>> that you are currently bundling in Rya. GPL is forcing that the source
>> code for those artifacts be available, but is not implying that the
>> license only applies to the code in source form.
>>
>> "A" and 1/2 would be how I expected this to go forward (although, I'm
>> not sure how "removing

RE: [DISCUSS] Path forward for release

[Meier, Caleb]

Unless I am misunderstanding something, which I probably am, it seems like 
Venkatesh and Josh are saying conflicting things. Venkatesh seems to be 
implying that the licenses for runtime dependencies do not need to be taken 
into account, while Josh seems to be be saying that the licenses of all 
artifacts created need to be compliant, and that the licensing of those 
artifacts depends on the licensing of run time dependencies. Am I missing 
something here?

Regarding geoindexing and indexing, those projects are somewhat coupled right 
now. Puja took steps to remove geoindexing from indexing in an effort to carry 
out 2. Going forward it might be best to make the indexes pluggable.



Sent from my Verizon 4G LTE smartphone


 Original message 
From: Josh Elser 
Date: 10/8/16 3:54 PM (GMT-05:00)
To: dev@rya.incubator.apache.org
Subject: Re: [DISCUSS] Path forward for release

Venkatesh is right in that the only "official" release in the ASF's eyes
is the source release. Any JARs you publish are supplementary and
technically not subject to the rules of Apache releases.

The area I'm still trying to fully grok is that the source-release you
publish must also create artifacts which are properly licensed[1]. Right
now, that means including numerous incompatible dependencies, and, thus,
does not meet the requirements of the ASL and the ASF.

Regarding David's last question: I would assume that the license applies
to both the source code and binary forms of the geo-related artifacts
that you are currently bundling in Rya. GPL is forcing that the source
code for those artifacts be available, but is not implying that the
license only applies to the code in source form.

"A" and 1/2 would be how I expected this to go forward (although, I'm
not sure how "removing GeoIndexing" evolved into "removing Indexing" --
are they so intertwined?). The area that currently makes me feel awkward
is how to interpret "optional dependencies". If every user of Rya would
just be building this support anyways, that's skirting a very gray area
in my current understanding of what is allowed.

- Josh

[1] 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_dev_licensing-2Dhowto.html-23binary=CwICAw=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=PlHBkcTuE9DcvVb1m3V1nCNNRsvZnLKrtMK1AKmYSY0=43QIBqVfsjovifro22HiGqmGW3Q9qY4xvKVtqPzv_x8=

Puja Valiyil wrote:
> I don't think I follow.  The source references an lgpl Api, and we are 
> publishing binary that references it in nexus.   Are you sure it's not an 
> issue?
>
> Sent from my iPhone
>
>> On Oct 6, 2016, at 10:36 PM, Seetharam Venkatesh  
>> wrote:
>>
>> If it's a runtime dependency, you are fine. Apache only supports source 
>> releases. We vote on source tar ball and not binary artifacts.
>>
>> Makes sense?
>>
>> Sent from my iPhone,
>> Venkatesh
>>
>>> On Oct 6, 2016, at 12:40 PM, David Lotts  wrote:
>>>
>>> Yes, geotools is a runtime dependency.  No geotools source code is
>>> distributed.
>>>
>>> By that I mean: Geotools source code is not in our source code repository.
>>> Only references: imports in our *.java files and dependencies entries in
>>> our pom.xml.   Because of this maven will package geotools JARs (binaries)
>>> in our shaded/uber JAR and WAR files that we distribute.
>>>
>>> With option 1 or 2 as discussed, maven will exclude the geotools jars in
>>> our JARs and WARs.  Users of Rya can follow some instructions that we
>>> provide to add "-P indexing" (or similar) to their Maven build command
>>> create their own jar/war containing the optional Rya features and geotools
>>> binaries.
>>>
>>> Your "you should be okay." mean which of these
>>> A. option 1 and option 2 will work around the issue and we should proceed
>>> before we release,
>>> - OR -
>>> B.  We are already in compliance and this is not a blocker for release as
>>> long as we are not redistributing geotools source code.
>>>
>>> Hopeful for interpretation B, but expecting and happy with A.
>>>
>>> david.
>>>
>>> On Thu, Oct 6, 2016 at 1:22 PM, Seetharam Venkatesh
>>> wrote:
>>>
 Quick question - geotools is a runtime dependency? Are you shipping the
 source code? If not, you should be okay.

 Sent from my iPhone,
 Venkatesh

> On Oct 6, 2016, at 7:52 AM, Puja Valiyil  wrote:
>
> Hi everyone,
> Talking with Aaron, it seems like there were two paths forward for
> refactoring in order to create a release.  To refresh everyone's memory,
> the issue was that the geo-indexing extensions to Rya pull in geotools,
> which prohibits us from releasing Rya under an Apache 2 license.  There
 may
> be some more particulars that I'm glossing over -- someone please chime
 in
> if they feel it is key to the discussion.
> The two paths forward we had were:
> 1.  Make all of 

RE: Review PR 100

[Meier, Caleb]

I'll have a look at it this afternoon.

-Original Message-
From: Aaron D. Mihalik [mailto:aaron.miha...@gmail.com] 
Sent: Friday, October 07, 2016 11:10 AM
To: dev@rya.incubator.apache.org
Subject: Review PR 100

Caleb/Kevin/Puja:

Can you all review Keith's Fluo update PR?  [1]

I'd like to pull it in before I perform the "optional" profile.

I'm taking a look at it now, but I'd like one of you all to review it as well.

--Aaron

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_incubator-2Drya_pull_100=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=_EG9UXNmSwu-YmfvkNBA5T1MQ8Uj6Y7mQ_CYID-dQ4I=5EFAGPadjBzEbX1EGrcSSWtTZQHc87oVDqfmGHCVYoE=
 

RE: [DISCUSS] Path forward for release

[Meier, Caleb]

I don't think that's acceptable.  As you mentioned earlier, that is a large 
portion of what Parsons has contributed to Rya.



Sent from my Verizon 4G LTE smartphone


 Original message 
From: "Aaron D. Mihalik" 
Date: 10/6/16 10:16 PM (GMT-05:00)
To: dev@rya.incubator.apache.org
Subject: Re: [DISCUSS] Path forward for release

After reviewing the PR that David submitted, it's concerning the number of
projects that would fall into this "optional" bin.  Some users probably
consider these "core" functions (e.g. reasoning and web):

Here the modules that need to be removed from the build in order to remove
the geotools references:

mapreduce
indexing
rya.indexing.pcj
indexingExample
rya.pcj.fluo
tinkerpop.rya
web.rya
rya.reasoning
rya.console
rya.merger

--Aaron

On Thu, Oct 6, 2016 at 3:41 PM David Lotts  wrote:

> Yes, geotools is a runtime dependency.  No geotools source code is
> distributed.
>
> By that I mean: Geotools source code is not in our source code repository.
> Only references: imports in our *.java files and dependencies entries in
> our pom.xml.   Because of this maven will package geotools JARs (binaries)
> in our shaded/uber JAR and WAR files that we distribute.
>
> With option 1 or 2 as discussed, maven will exclude the geotools jars in
> our JARs and WARs.  Users of Rya can follow some instructions that we
> provide to add "-P indexing" (or similar) to their Maven build command
> create their own jar/war containing the optional Rya features and geotools
> binaries.
>
> Your "you should be okay." mean which of these
> A. option 1 and option 2 will work around the issue and we should proceed
> before we release,
> - OR -
> B.  We are already in compliance and this is not a blocker for release as
> long as we are not redistributing geotools source code.
>
> Hopeful for interpretation B, but expecting and happy with A.
>
> david.
>
> On Thu, Oct 6, 2016 at 1:22 PM, Seetharam Venkatesh 
> wrote:
>
> > Quick question - geotools is a runtime dependency? Are you shipping the
> > source code? If not, you should be okay.
> >
> > Sent from my iPhone,
> > Venkatesh
> >
> > > On Oct 6, 2016, at 7:52 AM, Puja Valiyil  wrote:
> > >
> > > Hi everyone,
> > > Talking with Aaron, it seems like there were two paths forward for
> > > refactoring in order to create a release.  To refresh everyone's
> memory,
> > > the issue was that the geo-indexing extensions to Rya pull in geotools,
> > > which prohibits us from releasing Rya under an Apache 2 license.  There
> > may
> > > be some more particulars that I'm glossing over -- someone please chime
> > in
> > > if they feel it is key to the discussion.
> > > The two paths forward we had were:
> > > 1.  Make all of the indexing project and its downstream dependencies
> > > optional and exclude them from a release
> > > -- The indexing project includes several "optional" extensions to Rya
> > > (advanced indexing strategies).  Prior to Rya becoming an apache
> project,
> > > these indexing extensions were optional and there was a separate
> profile
> > > for including them.  This option involves reverting back to that
> mindset.
> > > The main argument against this is that these indexing
> > strategies/extensions
> > > are not in fact optional but are "core" to Rya and can't be excluded.
> > >
> > > 2.  Refactor Rya to pull geoindexing into a separate project and
> exclude
> > > that project from the release.
> > > - We could refactor Rya to have geoindexing be its own project and add
> a
> > > profile to include that in the build.  This would invovle moving the
> > class
> > > mvm.rya.indexing.GeoIndexer and packages mem.rya.indexing.accumulo.geo
> > and
> > > mvm.rya.indexing.mongodb.geo to a separate project and then
> > removing/moving
> > > references to geoindexing anywhere else.  Another option is to refactor
> > the
> > > GeoIndexer interface to remove the geotools dependency.
> > >
> > > I think #1 is a good immediate path for a release and that #2 is a good
> > > longer term path forward.  Since it's probably in our best interests
> as a
> > > community to get an apache release sooner rather than later, I'd rather
> > us
> > > go with #1 since it would quicker.  I also think that most users of Rya
> > > would be ok with excluding the indexing project since it is not core
> > > functionality for Rya.  While #2 is a better long term plan, it
> involves
> > > some pretty extensive refactoring that would be difficult to do well
> in a
> > > timely manner.
> > >
> > > Any thoughts?
> >
>

RE: [ANNOUNCE] Welcome new committer Caleb Meier

[Meier, Caleb]

Thanks Everybody!  

Happy to be part of the team and looking forward to playing a larger role as a 
committer!

-Original Message-
From: Aaron D. Mihalik [mailto:aaron.miha...@gmail.com] 
Sent: Friday, September 16, 2016 2:32 PM
To: dev@rya.incubator.apache.org
Subject: Re: [ANNOUNCE] Welcome new committer Caleb Meier

Ditto. Thanks for contributions and enthusiasm Caleb!

On Fri, Sep 16, 2016 at 12:40 PM Josh Elser  wrote:

> Congrats, Caleb!
>
> Adina Crainiceanu wrote:
> > Hi all,
> >
> > It is my pleasure to announce that Caleb Meier is now a committer 
> > for the Apache Rya (incubating).
> >
> > Thank you Caleb for your past and future contributions and we are 
> > looking forward to continue working with you. Welcome!
> >
> > Best wishes,
> > Adina (on behalf of Rya PPMC)
> >
>

RE: RYA-179 Review License / Copyright notices on Rya Artifacts

[Meier, Caleb]

While the indexer project extensions are optional in that they are turned off 
by default to minimize data plume, I would argue that they are not optional in 
the sense that Josh has described.  There is no other way to index/query for 
freetext, geospatial, and temporal data without these extensions.  So if a user 
wants these capabilities, they need the indexer project and all of the 
incompatibly licensed dependencies that come along with it.

From: Puja Valiyil [puja...@gmail.com]
Sent: Wednesday, September 14, 2016 9:49 PM
To: dev@rya.incubator.apache.org
Cc: Billie Rinaldi
Subject: Re: RYA-179 Review License / Copyright notices on Rya Artifacts

The indexer project has a set of configurable optional extension to Rya.  
Things like support for geosparql, support for free text indexing, and support 
for precomputed joins (which is where the fluo integration comes in).  These 
are extensions that by default are turned off.  They can really increase the 
data plume associated with some data, which is the main reason why.

In the original port into Apache, this project was only included if you 
specified that profile.  This was because we have traditionally considered 
those features experimental and they bring in a lot of possibly unwanted 
dependencies.  Aaron refactored it to not be optional when he was updating the 
pond to reference the Apache parent Pom.
So no alternative, but functionality that a typical user may debatably not want.

Sent from my iPhone

> On Sep 14, 2016, at 8:05 PM, Josh Elser  wrote:
>
> I would have said that this is only kosher when you have an alternative to 
> the incompatibly licensed software. Is the indexer actually optional (I don't 
> have enough context)? Are there ways for me to to indexing of the same type 
> of data that don't require use of these incompatible dependencies?
>
> Billie might be able to provide some more context too.
>
> Aaron D. Mihalik wrote:
>>> Could we revive the indexer profile again?
>>
>> (tl;dr: Yes.  Mentors: Please correct us if we're wrong)
>>
>> This might be a solution.  I found a couple similar cases with Apache
>> projects and discussions related to those cases.
>>
>> Apache Flink integrated with Amazon Kinesis [1] and [2].  Note that Kinesis
>> is an optional profile, and it's well documented in the POM why it's
>> optional.
>>
>> (Note that NiFi got around this by using Amazon's SDK for Java [3], which
>> is purely Apache 2.0)
>>
>> Spark uses optional profiles to build artifacts based on LGPL
>> dependencies.  Spark has to built by the user to use netlib [4][5], Ganglia
>> [6], or Kinesis [6].
>>
>> I think a profile will work, but I'd like to see it well documented (both
>> in the POM and manual) so that we never accidentally create a release with
>> these artifacts.
>>
>> I was going to open a separate ticket to implement this, but I think it's
>> good to track all of this effort under RYA-177.
>>
>> --Aaron
>>
>> [1]
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_flink_blob_release-2D1.1.2_flink-2Dstreaming-2Dconnectors_pom.xml-23L69=CwIFAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=USEC4e6JdxuZZwMB0AkZPzHtdsKWf8ep6g5BSRLQ2XY=wnYDdDdgR8EEFav9sKC7ftd6ZjSJcOXU8FISG6jJMHc=
>> [2]
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_flink_blob_release-2D1.1.2_flink-2Dstreaming-2Dconnectors_flink-2Dconnector-2Dkinesis_pom.xml-23L73=CwIFAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=USEC4e6JdxuZZwMB0AkZPzHtdsKWf8ep6g5BSRLQ2XY=ZFTL5gQzyzLvRcWrafGrCobMJ8d1DWSmZlIVz9M7EuQ=
>>
>> [3] 
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_nifi_blob_master_pom.xml-23L1316=CwIFAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=USEC4e6JdxuZZwMB0AkZPzHtdsKWf8ep6g5BSRLQ2XY=6pMGnZxiQccMUFNO18dbUc8luQrhNKa-XVCc1y_YlGg=
>>
>> [4] 
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_spark_blob_v2.0.0_mllib_pom.xml-23L120=CwIFAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=USEC4e6JdxuZZwMB0AkZPzHtdsKWf8ep6g5BSRLQ2XY=apxAyRJMc-jDvRpVzA6wFnuOjlNtFUKev9nXgiv79DM=
>> [5]
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_spark_blob_v2.0.0_docs_ml-2Dguide.md-23dependencies=CwIFAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=USEC4e6JdxuZZwMB0AkZPzHtdsKWf8ep6g5BSRLQ2XY=yFa0G6qUiJpaZxKA--8iuH8m3hxgmutd-0ZD0B32268=
>>
>> [6] 
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_spark_blob_v2.0.0_pom.xml-23L2414=CwIFAg=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=USEC4e6JdxuZZwMB0AkZPzHtdsKWf8ep6g5BSRLQ2XY=3xSSyDcql0fPyGpmzCoVV4W8Zgv2yHzm_HhKNhQahko=
>>
>> [7] 
>> 

RE: [VOTE] Release Rya (Incubating) version 3.2.10

[Meier, Caleb]

Hashes and Sigs looked good.  There were no binaries.  However,
my build failed on Mongo Tests.  Aaron, I know you were having some issues
with this.  How did you resolve it?

-Original Message-
From: David Lotts [mailto:dlo...@gmail.com] 
Sent: Monday, September 12, 2016 1:12 PM
To: dev@rya.incubator.apache.org
Subject: Re: [VOTE] Release Rya (Incubating) version 3.2.10

-1 (non-binding)  because RYA-169 Mongo direct example is broken.  This is 
fixed in pull request #87 The example is important and should be working in the 
release IMHO.
david.

On Mon, Sep 12, 2016 at 12:04 PM, Aaron D. Mihalik 
wrote:

> Thanks Josh!  This list is great.
>
> I'll add the RC-X to the "Vote" email for the next RC.  I also updated 
> the release docs to include that note.
>
> I added these tasks to track:
>
> (Blocker) RYA-177 - Review License on Rya Dependencies
> RYA-178 Review RAT Exclusions
> RYA-179 - Review License / Copyright notices on Rya Artifacts
> RYA-180 - Review Licensing of Shaded/War'd Rya Artifacts
> RYA-182 - Review SCM Tag in Parent POM
>
> Is RYA-180 subsumed by RYA-177?  If we verify that all of the Rya 
> Dependencies are not "Category X", are there additional concerns about 
> what we war/shade up?
>
> --Aaron
>
> On Mon, Sep 12, 2016 at 11:35 AM Josh Elser  wrote:
>
> > (thanks for the extension, I started looking at this and then forgot 
> > about it)
> >
> > -1 (binding)
> >
> > First off, please include some sort of "RC-X" identifier in the vote 
> > subject so that we can differentiate them in the archives.
> >
> > - The good
> >
> > * xsums+sigs match
> > * Can build from source
> > * Ran all unit tests (as invoked during `mvn package`)
> > * Found no binary files
> >
> > - Things that must be fixed
> >
> > * 
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org
> > _repos_dist_release_incubator_rya=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH
> > 54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8
> > =WvEm7PukqYvhHT2u1O_8y5VbUPPX7Ue86qJEHI1_8tQ=F3WPgOX6zPtR2bvpRLans
> > MRSIsYEct6fZGxgd_skh2Q=  and 
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org
> > _repos_dist_dev_incubator_rya=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54jo
> > YF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=WvE
> > m7PukqYvhHT2u1O_8y5VbUPPX7Ue86qJEHI1_8tQ=as_NA5OQgeiTjH3JrcmQNFOa-
> > KmvrhG9jIefFwIktG4=  don't exist. You must have the former created 
> > with a KEYS file that contains the GPG public keys for those 
> > creating Rya release notes. Typically, you should use 
> > dist.a.o/repos/dist/dev/incubator/rya to stage your release 
> > artifacts, although policy on whether using the staging repo alone 
> > is sufficient is not clear to me. (were it not for the licensing 
> > issues below, we could just fix this)
> > * jgridshift:jgridshift appears to be LGPL licensed 
> > (https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_flo
> > scher_jGridShift_blob_master_LICENSE=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_
> > LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo
> > 8=WvEm7PukqYvhHT2u1O_8y5VbUPPX7Ue86qJEHI1_8tQ=C8fr3StPTh4auFWZk1DW-ME5lQwth3thFnyZJiogWj0=
> >  ). You may not use this software. It looks like it was not appropriately 
> > marked in its pom which is why the configuration from Rya's parent 
> > apache.pom did not catch it. This is brought in via 
> > org.geotools.xsd:gt-xsd-gml3.
> > * colt 
> > (https://urldefense.proofpoint.com/v2/url?u=http-3A__dst.lbl.gov_ACS
> > Software_colt_=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq1
> > 0=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=WvEm7PukqYvhHT2u1O
> > _8y5VbUPPX7Ue86qJEHI1_8tQ=pWVOQlS2iaxs9lhkvDYXRq9qKdjO7f-hfWpYwdJc
> > imM= ) appears to be another brought in by 
> > com.tinkerpop.blueprints:blueprints-core
> > * com.google.code.findbugs:jsr305 is another example of GPL licensing.
> > While the artifact appears to have the ASL tagged on the pom, all 
> > Findbugs documentation states that the project is GPL.
> >
> > I would recommend to make a pass over your dependencies to verify 
> > that you aren't depending on any projects which are licensed with a 
> > license on this list: 
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_legal_resolved.html-23category-2Dx=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=WvEm7PukqYvhHT2u1O_8y5VbUPPX7Ue86qJEHI1_8tQ=USJYWYBycEbL7kQNHm05tOaWE5yZAhqOp9vb3SiQiKY=
> >  . See 
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_licenses_GPL-2Dcompatibility.html=CwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_4WXTD0qo8=WvEm7PukqYvhHT2u1O_8y5VbUPPX7Ue86qJEHI1_8tQ=rILTE-9eQtTB_V1pagZGMaOJTMovaWcqRFyfD6KVImg=
> >   for more details.
> > The above three examples were found via a brief glance.
> >
> > - Things to fix later (later rc's or the next release)
> >
> > * Copyright year in NOTICE is 

RE: regarding slow query execution

[Meier, Caleb]

Hey Pranav,

Even if the filtering is occurring client side, that is still strange behavior. 
 What does your query look like?


-Original Message-
From: pranav.puri [mailto:pranav.p...@orkash.com] 
Sent: Monday, September 05, 2016 3:38 AM
To: dev@rya.incubator.apache.org
Subject: regarding slow query execution

Dear All

  The query execution time for sparql queries with regex filters is much
more(10-12 minutes) as compared to queries with no filters applied.

The queries are being run on tables containing triples from dbpedia dataset.
Each table(ie Spo,osp,po) contains 110 million entries.I am currently using a 
three node accumulo cluster.

Please suggest some ways to improve the query execution time .

Regards
Pranav

RE: regarding slow query execution

[Meier, Caleb]

Hello Pranav,

Are you using the freetext index or are your regex filters just normal open RDF 
filters?  The freetext index has the added benefit that filtering is pushed to 
the server, whereas in the 
case of the normal, open RDF filters, all of the filtering happens client side. 
 

-Original Message-
From: pranav.puri [mailto:pranav.p...@orkash.com] 
Sent: Monday, September 05, 2016 3:38 AM
To: dev@rya.incubator.apache.org
Subject: regarding slow query execution

Dear All

  The query execution time for sparql queries with regex filters is much
more(10-12 minutes) as compared to queries with no filters applied.

The queries are being run on tables containing triples from dbpedia dataset.
Each table(ie Spo,osp,po) contains 110 million entries.I am currently using a 
three node accumulo cluster.

Please suggest some ways to improve the query execution time .

Regards
Pranav

RE: [DISCUSS] let's try a release

[Meier, Caleb]

Hey Josh,

We're doing some research into the process now and we'll be working on it 
Thursday and Friday this week.

-Original Message-
From: Josh Elser [mailto:josh.el...@gmail.com] 
Sent: Monday, August 08, 2016 11:50 AM
To: dev@rya.incubator.apache.org
Subject: Re: [DISCUSS] let's try a release

Aaron --

Comments?

Puja Valiyil wrote:
> Aaron had signed himself up a few months ago, I'm not sure how far he got 
> though.
>
> Sent from my iPhone
>
>> On Jul 31, 2016, at 2:00 AM, Sean Busbey  wrote:
>>
>> Hi folks!
>>
>> Anyone up for acting as the community's first release manager? It's 
>> been a while, and working through the process of doing a release is 
>> something that takes practice so it's good to get in the habit.

Rya Working Group

[Meier, Caleb]

Hey All,

The slides for today's and past Rya Working Groups can now be found on 
Confluence:

https://cwiki.apache.org/confluence/display/RYA/Rya+Office+Hours


Puja already sent out the telecon info, but just for completeness here it is 
again:


Time: June 1st, 12:00 PM (noon) EST

Phone: 888-598-1409; 7483409

Rya Working Group Slides

[Meier, Caleb]

Here are the slides from our discussion today.

Caleb