Re: [VOTE] Apache Rya (incubating) graduation to Top Level Project

[David Lotts]

Re-sending this from my Apache email account.  +1 still!
david.
On Wed, Aug 28, 2019 at 12:13 PM David Lotts  wrote:

> +1 - Recommend graduation of Apache Rya as a TLP
>
> Thank you Veep Adina!
> david lotts.
>

Re: [VOTE] Apache Rya (incubating) graduation to Top Level Project

[David Lotts]

+1 - Recommend graduation of Apache Rya as a TLP

Thank you Veep Adina!
david lotts.

Re: Rya version caused some problems

[David Lotts]

Sorry your having issues!
>  because the version numbers are inconsistent?
Which version numbers do you suspect are inconsistent?

Given the error perhaps your server cannot connect to your Zookeeper
server.  This could be that zookeeper is down, or no network connection, or
incorrect IP or port number.
>"INFO ipc.Client: Retrying connect to server:
node01.dbcluster1.tju.edu.cn/192.168.1.1:8032. Already tried 5 time(s);

However, I have seen this message when the cluster is coming up, it might
be a temporary issue.  Is the error only found when the Accumulo started?

Check that zookeeper is listening and network accessible.  These answers
might be useful:
https://stackoverflow.com/questions/29106546/how-to-check-if-zookeeper-is-running-or-up-from-command-prompt
I use netcat on linux, then use the zookeeper stat command to get status:
nc192.168.1.18032
stat
status info from zookeeper...

If that is all working, look for more errors in your log.
BTW, this SASL error usually means nothing, I've seen it many times on
healthy systems:
>Will not attempt to authenticate using SASL (unknown error)

Let me know if this helps!
david.

On Fri, Aug 16, 2019 at 8:06 AM 柴乐乐  wrote:

> Hi Rya followers,
> I install Rya on stand-alone machine, and I upload it on cluster, but
> I cannot load data now.
> My cluster cannot  access the external network, so I can only pass the
> compiled Rya through the intranet, the version of Rya is stand-alone, when
> I run the load command
> "hadoop jar
> /usr/local/JAR/rya.mapreduce-4.0.0-incubating-SNAPSHOT-shaded.jar
> org.apache.rya.accumulo.mr.tools.RdfFileInputTool -Dac.zk=192.168.1.1:2181
> -Dac.instance=accumuloV7 -Dac.username=root -Dac.pwd=11
> -Drdf.tablePrefix=triplestore_ -Drdf.format=N-Triples test.nt",
> it always has errors like
>"INFO zookeeper.ClientCnxn: Opening socket connection to server
> 192.168.1.1/192.168.1.1:2181. Will not attempt to authenticate using SASL
> (unknown error)"
> and "INFO ipc.Client: Retrying connect to server:
> node01.dbcluster1.tju.edu.cn/192.168.1.1:8032. Already tried 5 time(s);
> retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
> sleepTime=1000 MILLISECONDS)"
> My clusters have 8 nodes, node01 is the master and the others are
> slave. I have install Zookeeper and Apache Accumulo successfully, but I
> donot know how to solve the problem, I want to load data.
> The reason for this problem is because the version numbers are
> inconsistent?
> Best regards!
>
>
>
>
>

Re: [VOTE] Release Rya (Incubating) version 4.0.0 RC1

[David Lotts]

+1   Release this package as rya-project-4.0.0

I tested all the check-sums and signature.
I built and ran ALL the declared tests.
david.

On Tue, Jul 16, 2019 at 10:55 AM Aaron D. Mihalik 
wrote:

> I am pleased to be calling this vote for the source release of Apache Rya
> (Incubating), version 4.0.0.
>
> The source zip, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-4.0.0-rc1/
>
> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
>
> https://repository.apache.org/content/repositories/orgapacherya-1011/org/apache/rya/
>
> The Git tag is rya-incubating-4.0.0-rc1
> The Git commit ID is 824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3
>
> https://gitbox.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3
>
> Checksums of rya-project-4.0.0-source-release.zip:
> SHA1: e5e91b19abddbdf3c9f0e18469433e730bef7957
> MD5: 1d46620a37df803c3ba0b1b383c1da10
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/mihalik.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
>
> Issues that were closed/resolved for this release are here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319020=12341289
>
>
> The vote will be open for 72 hours and close at 11:00 AM Friday, July 19,
> 2019 (EDT).
> 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-4.0.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

Re: about install Rya at cluster

[David Lotts]

RyaWeb is an Accumulo client.  So it does not matter if it is talking to a
cluster or a standalone instance of Accumulo.  It just needs the usual
configuration: basically: zookeeper list and the Rya instance prefix name.
The same goes with MongoDB I believe, with MongoDB configuration.

Are you getting a specific error?  Where are you stuck?

david.

On Mon, Jul 15, 2019 at 4:44 AM 徐炜淇  wrote:

> hi,
> Normally, we enter the query in a web jsp endpoint ,and we can also get
> the search result in web jsp endpoint. I usually use eclipse to run the Rya
> project, so I can get the query execution time.
> But now, I want to install Rya at cluster,  there will be a problem
> occurred that I cannot enter the query without graphical interface.
> Can you give me some guidelines?
>
>
> Best wishes,
> wq
>
>
>
>
>

Re: Upcoming release?

[David Lotts]

I volunteer to be release manager.  Aaron is also volunteering, so we are
doing it jointly, if that is possible.
We will start right away if that is lazily okay with everyone!
david lotts.

On Sat, Jun 29, 2019 at 6:53 PM Adina Crainiceanu  wrote:

> I'll volunteer as release manager, but I can spend time on this only in
> about a month, as I'll be mostly  traveling for work and vacation till
> then. If someone else wants to volunteer for the release earlier, the
> instructions are at
> https://cwiki.apache.org/confluence/display/RYA/How+To+Release+Rya
>
> Adina
>
> On Tue, Jun 25, 2019 at 10:28 AM Adina Crainiceanu  wrote:
>
> > I agree, we should have a new release. Do we have a volunteer to be the
> > release manager? It has to be a committer.
> >
> >
> > On Tue, Jun 25, 2019 at 9:19 AM Puja Valiyil  wrote:
> >
> >> Hi Rya developers,
> >> I was thinking that it may be time to do another release of master.  We
> >> haven't had an official release in quite a while, and there have been
> >> significant changes on master.
> >> Thoughts?
> >>
> >
> >
> > --
> > 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/
> >
>
>
> --
> 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/
>

Fwd: [EXTERNAL] Release 4.0.0 -- last call for pull requests

[David Lotts]

This a last call for Pull Requests to be included in this release. Please
let me know

before Monday if you have an open PR you want included in this release.



We plan to have a candidate release next week.

Thanks,

david.

Re: Re: About Rya loadData and query

[David Lotts]

Let make sure you have seen the manual which has a quick start guide:

https://github.com/apache/incubator-rya/blob/5463da23c7cd5eaddf2ab13f0b42141211ab59f2/extras/rya.manual/src/site/markdown/index.md

Here is a better example that loads a file then does queries.  This one
uses MongoDB, but most everything is the same for Accumulo.

https://github.com/apache/incubator-rya/blob/5463da23c7cd5eaddf2ab13f0b42141211ab59f2/extras/indexingExample/src/main/java/MongoRyaDirectExample.java#L902

david.

Re: Apache Rya Logging question

[David Lotts]

> Second, since the Rya Shell connects directly to Zookeeper/Accumulo,
> does that mean it won't use Rya's query optimizer capabilities (Prospects 
> Table, etc.)?

When you are using the shell, all the Rya code is built into the
Shell.  Your configuration must match the configuration of all the
other clients that created/use the Rya instance.
david.

Re: Query time optimization

[David Lotts]

Also just wanted to mention the benchmark module in the Rya sources:
https://github.com/apache/incubator-rya/tree/master/extras/rya.benchmark
I can find out more if you think it is interesting.
david.

Re: Apache Rya Logging question

[David Lotts]

Did you try this?  This is from:
https://github.com/apache/incubator-rya/blob/master/extras/rya.manual/src/site/markdown/shell.md#logs

'''
Logging for the rya shell is written to the
rya.shell-3.2.11-incubating/logs directory. Configuration of the
logging is controlled by the
rya.shell-3.2.11-incubating/conf/log4j.properties file.
'''
The Rya shell connects directly to Zookeeper/Accumulo and does not
interact with the Rya web service.  I just checked with the shell
author.

david lotts.

Re: Code development questions

[David Lotts]

Timea,
Thanks for reaching out.
Some of your questions are addressed here in the wiki:
https://cwiki.apache.org/confluence/display/RYA/Contributing+to+Rya
But there is still room for confusion. Your questions are good, and might
be something we should add to that document more explicitly.

   - your master branch is the one containing the official releases correct?
>
No, master branch contains the current development snapshot. Create a
request to pull your work into master.


>- the 3.x/master branch is actually the branch were current
> development  is done?

No, I believe 3.x/master is to track changes for a major modification to
use the latest release of rdf4j library.  You should use master unless you
want to work on that rdf4j upgrade.


> (the equivalent of the develop branch in git flow:
>
> https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
> )
>Correct?

Not really, our master is their described develop branch.  Their master
branch has no corresponding branch, but instead we use *tags* to track each
release.  This is how a bunch of our peer projects do it.

(even is rya is set to 4 the branch 3.x name is misleading, maybe
>consider renaming it in the future)
>
I agree, it does seem confusing.  3.x refers to a future major breaking
version.


>- if we want to do pull requests we would do them on 3x/master branch?
>
No, use master.

   - do you have a place to report tickets/issues? (other projects make use
> of git issues)
>
Yep, Jira.  If you are new you'll need to create a user account:
https://issues.apache.org/jira/browse/RYA

Let us know if you have problems doing that.

david.

Re: October podling report draft - please comment

[David Lotts]

Would it be appropriate to mention the relatively new involvement of the
good folks at Semantic Web Company?
This increases our diversity and stability.
david.

Re: [VOTE] logo for Apache Rya

[David Lotts]

+1  Totally
Going out to get the tattoo!
(just kidding)
david.

On Fri, Sep 28, 2018 at 5:32 PM Puja Valiyil  wrote:

> +1 for me as well
>
> On Friday, September 28, 2018, Chilton, Kevin 
> wrote:
>
> > +1 I like the one with the red moons.
> >
> > Kevin Chilton
> > Senior Software Engineer
> > kevin.chil...@parsons.com - P: +1 703.797.3147
> >
> > PARSONS - Envision More
> > Parsons | LinkedIn | Twitter | Facebook
> >
> >
> > -Original Message-
> > From: White, Eric 
> > Sent: Friday, September 28, 2018 3:43 PM
> > To: dev@rya.incubator.apache.org
> > Subject: RE: [VOTE] logo for Apache Rya
> >
> > +1 (Awesome!)
> >
> > Thanks,
> > -Eric White
> >
> > -Original Message-
> > From: Brown, Jennifer 
> > Sent: Friday, September 28, 2018 3:32 PM
> > To: dev@rya.incubator.apache.org
> > Subject: Re: [VOTE] logo for Apache Rya
> >
> > + 1 (love it!)
> >
> >
> > Jennifer Brown
> > Project Manager, Semantic Technologies
> > PARSONS
> > 1911 N. Fort Myer Dr. Ste 800
> > Arlington, VA 22209
> > Phone: (703) 797-3136
> > Fax: (703) 522-6310
> > jennifer.br...@parsons.com
> > www.parsons.com 
> >
> > On 9/28/18, 3:19 PM, "Adina Crainiceanu"  wrote:
> >
> > Hi,
> >
> > After the discussion on the Rya logo [1], Susan created a modified
> > version
> > with 3 red colored moons. Please vote to adopt the logo as the
> official
> > Apache Rya logo. The logo is in rya3moons.pdf file at
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.
> > apache.org_confluence_display_RYA_Rya-2Blogo-2Bproposals=
> > DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-
> > wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=VS-AxA6K75NG7D_
> > 3fg5baE4_mIUbpdLlsUkPgYNWFxI=zxuoN8xaydQWRB9oq1inyuLIaLAPjx
> > pAldxlxjtP3Z8=
> >
> > This is a lazy consensus majority vote, open for at least 72 hours.
> >
> > Thank you,
> > Adina
> >
> >
> > [1]
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> > apache.org_thread.html_14000e4c7a74e6e6776c36c9003e41
> > 8b2ec2b4573372a2e5e7603f9f-40-253Cdev.rya.apache.org-253E=
> > DwIBaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=QwnT-
> > wJItyf76XsYIlx7lVWk0WP1Ot0bMlSgUFcldnw=VS-AxA6K75NG7D_
> > 3fg5baE4_mIUbpdLlsUkPgYNWFxI=8zBHn3x9Zhh1SFWlY9YVoVLB-
> > nF48sE1hBrVepORqk4=
> > --
> > 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_
> > LWH54joYF7EKmrYIdfxIq10=QwnT-wJItyf76XsYIlx7lVWk0WP1Ot0bMlS
> > gUFcldnw=VS-AxA6K75NG7D_3fg5baE4_mIUbpdLlsUkPgYNWFxI=buDN-
> > 6UlkZFYcTdkSNey6cSje0T7sBsXtLoFjSXfZXE=
> >
> >
> >
> > 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: Does Rya directly interact with Hadoop (bypassing Accumulo)?

[David Lotts]

Rya uses the hadoop-common library to manage the configuration properties.
This class is a descendent of org.apache.hadoop.conf.Configuration :

https://github.com/apache/incubator-rya/blob/master/dao/accumulo.rya/src/main/java/org/apache/rya/accumulo/AccumuloRdfConfiguration.java

When Rya calls  (AccumuloRdfConfiguration.java:323)

  org.apache.hadoop.conf.Configuration.getInstances(...)

it checks for HADOOP_HOME and throws your error.

You might be able to turn that off using Configuration
<http://hadoop.apache.org/docs/r3.0.1/api/org/apache/hadoop/conf/Configuration.html#Configuration-boolean->
(boolean loadDefaults) constructor as described here:

http://hadoop.apache.org/docs/r3.0.1/api/org/apache/hadoop/conf/Configuration.html
Quote:

Unless explicitly turned off, Hadoop by default specifies two
resources, loaded in-order from the classpath:

   1. core-default.xml
   
<http://hadoop.apache.org/docs/r3.0.1/hadoop-project-dist/hadoop-common/core-default.xml>:
   Read-only defaults for hadoop.
   2. core-site.xml: Site-specific configuration for a given hadoop
   installation.

BTW, I think we would all love to hear more about your use of Rya on Google
Cloud.
david.

On Fri, Jun 29, 2018 at 1:00 PM David Lotts  wrote:

> Hi Maxim,
> Rya uses an Accumulo client.  The Accumulo client is dependent on Hadoop,
> particularly HDFS and zookeeper.
> The environment variable  HADOOP_HOME or corresponding property is
> required to find the path to the locally installed hadoop runtime files.
> Details can be found in the Accumulo manual where it describes running
> client code:
>
>
> https://accumulo.apache.org/1.7/accumulo_user_manual.html#_writing_accumulo_clients
>
> david.
>
>
> On Wed, Jun 20, 2018 at 9:16 AM Maxim Kolchin 
> wrote:
>
>> Hi all,
>>
>> I'm running Apache Accumulo on Google VMs (aka Compute Engine) and use
>> Google Cloud Storage as a replacement for HDFS. Hadoop (its MapReduce
>> part)
>> is only used to run the import job to load some RDF to Accumulo, so I shut
>> it down when the job finishes.
>>
>> When I trying to startup Rya I see the following exception:
>> java.io.IOException: HADOOP_HOME or hadoop.home.dir are not set. The full
>> log is at [1].
>>
>> Does it mean that Rya requires a direct access to Hadoop? I guess Rya is
>> looking for a Hadoop cluster in Zookeeper and when it can't find it there
>> it's looking for the HADOOP_HOME.
>>
>> [1]: https://gist.github.com/KMax/687293ce666754ce8eed11c369a0db05
>>
>> Thank you in advance!
>> Maxim Kolchin
>>
>> E-mail: kolchin...@gmail.com
>> Tel.: +7 (911) 199-55-73
>> Homepage: http://kolchinmax.ru
>>
>

Re: Does Rya directly interact with Hadoop (bypassing Accumulo)?

[David Lotts]

Hi Maxim,
Rya uses an Accumulo client.  The Accumulo client is dependent on Hadoop,
particularly HDFS and zookeeper.
The environment variable  HADOOP_HOME or corresponding property is required
to find the path to the locally installed hadoop runtime files.
Details can be found in the Accumulo manual where it describes running
client code:

https://accumulo.apache.org/1.7/accumulo_user_manual.html#_writing_accumulo_clients

david.


On Wed, Jun 20, 2018 at 9:16 AM Maxim Kolchin  wrote:

> Hi all,
>
> I'm running Apache Accumulo on Google VMs (aka Compute Engine) and use
> Google Cloud Storage as a replacement for HDFS. Hadoop (its MapReduce part)
> is only used to run the import job to load some RDF to Accumulo, so I shut
> it down when the job finishes.
>
> When I trying to startup Rya I see the following exception:
> java.io.IOException: HADOOP_HOME or hadoop.home.dir are not set. The full
> log is at [1].
>
> Does it mean that Rya requires a direct access to Hadoop? I guess Rya is
> looking for a Hadoop cluster in Zookeeper and when it can't find it there
> it's looking for the HADOOP_HOME.
>
> [1]: https://gist.github.com/KMax/687293ce666754ce8eed11c369a0db05
>
> Thank you in advance!
> Maxim Kolchin
>
> E-mail: kolchin...@gmail.com
> Tel.: +7 (911) 199-55-73
> Homepage: http://kolchinmax.ru
>

Re: Failed build from master

[David Lotts]

> I documented this in RYA-485

is this related to?  RYA-472 "Shaded jars not being produced"
Just ran across it, did not read it.
david.

Re: review website for release 3.2.12 #6 and #7

[David Lotts]

​

Caleb and I have Apache ID's now.  Mine is dlotts .

- name: David Lotts

  apacheId:

  githubId: dlotts

  org: Parsons

  role: Contributor



- name: Caleb Meier

  apacheId:

  githubId: meiercaleb

  org:

  role: Contributor



I took a quick look at all changes for the website and it looks fine.  I'll
look some more on Monday after you publish.



david.

Re: Want to Help

[David Lotts]

 Shayak,
Welcome!
Look at the top half of this page in the wiki:

Contributing to Rya

https://cwiki.apache.org/confluence/display/RYA/Contributing+to+Rya

Where it says "assign it to yourself" you may not have permission, if so,
post here and a committer can assign it.
david.

On Fri, Feb 23, 2018 at 12:22 AM, Shayak Sadhu 
wrote:

>  Hello Team,
> I am a data engineer and I am familiar with Python, R, Java. I am novice at
> Scala and am picking it up. I have experience in data analysis and hadoop
> stack development. I would like to contribute to this project.
>
> Regards,
> Shayak Sadhu
>

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

[David Lotts]

+1 binding

Success on Fedora Linux using java version "1.8.0_121"  with:

mvn clean install  -P geoindexing -P benchmark -P enable-it -Drat.skip  -l
../rya$(date +%Y%m%d%H%M).log

Verified all the hashes and the signature.
Looked at https://repository.apache.org/#stagingRepositories

(Adina: For cleaning up, you can drop Repository orgapacherya-1009 (rc1)
anytime now.)

david.
David Lotts

​

Re: Release build fails on Windows

[David Lotts]

I just ran all the tests in Linux, Yay!
I am having issues in windows that are different than yours.  Lemme move
back to windows and see if I can find the cause and maybe reproduce your
errors.
david.

On Thu, Feb 15, 2018 at 1:41 PM, Puja Valiyil  wrote:

> Ok, I would vote to mark it as a known issue then.  Is there any concern if
> the release doesn't build under windows?  I don't see that being an issue
> personally.
>
> On Thu, Feb 15, 2018 at 1:32 PM, White, Eric 
> wrote:
>
> > I can try but that probably won't fix it since it determines that the
> > owner of “user.home” is system and that’s not the same as administrator.
> >
> > -Original Message-
> > From: Puja Valiyil [mailto:puja...@gmail.com]
> > Sent: Thursday, February 15, 2018 1:24 PM
> > To: dev@rya.incubator.apache.org
> > Subject: Re: Release build fails on Windows
> >
> > Did you try running as an administrator?
> > I think that we should probably mark this as a known issue -- I don't
> feel
> > it should hold up the release.  There have been lots of issues with
> people
> > building on windows, this is part of a larger issue I feel.
> >
> > On Thu, Feb 15, 2018 at 1:11 PM, White, Eric 
> > wrote:
> >
> > > I ran into issues building the release (3.2.12-rc1) on a Windows
> > > machine with git bash.  It seems some of the new Rya Shell tests fail
> > > due to the new PathUtils class (from another commit) saying "Operation
> > > of a file in a shared directory is not allowed" when attempting to add
> > > the .rya_shell_history file to "user.home".
> > >
> > > It seems it expects "user.home" to be owned by the user or an
> > > administrator, but it's owned by the system and fails.
> > >
> > > Thanks,
> > > -Eric White
> > >
> >
>

Re: First day with RYA questions.

[David Lotts]

This is a good example:

https://github.com/apache/incubator-rya/blob/master/extras/indexingExample/src/main/java/RyaDirectExample.java

There are several others in that same directory.

david.

On Tue, Feb 13, 2018 at 2:42 PM, Geoffry Roberts <threadedb...@gmail.com>
wrote:

> David,
>
> First thanks for being responsive.  Alas,  I am not seeing the example
> project.
> I have cloned: https://github.com/apache/incubator-rya.git
> I am not seeing anything called examples.  Am I looking in the right place?
>
> On Tue, Feb 13, 2018 at 2:28 PM, David Lotts <dlo...@gmail.com> wrote:
>
> >  Correction: You can disable the RAT check with this:
> > -Drat.skip
> >
> > You do not need a Mongo server unless you enable it in the configuration.
> > If you do need it, it's a bug.  Although there is no way to separate the
> > automated MongoDB unit tests from Accumulo, but tests create their own
> > testing/mock server.
> >
> > You configure Accumulo parameters via the Rya configuration.  That can be
> > done either by building up a config object, or using an XML config file.
> > There are examples of both in various places.  Look at the examples
> project
> > and the web project.  Ask again if you are not seeing it.
> >
> > You can also choose to use the web API or call the Rya API (OpenRDF AKA
> > Sesame AKA rdf4j) directly.
> >
> > david.
> >
> > On Tue, Feb 13, 2018 at 2:08 PM, Geoffry Roberts <threadedb...@gmail.com
> >
> > wrote:
> >
> > > All,
> > >
> > > Another question:  How do I point RYA at my Accumulo cluster?
> > >
> > > I have an Accumulo cluster running in the company cloud.
> > >
> > > Thanks
> > >
> > > On Tue, Feb 13, 2018 at 1:35 PM, Geoffry Roberts <
> threadedb...@gmail.com
> > >
> > > wrote:
> > >
> > > > git clean -fdx worked.  Never had that problem before.
> > > >
> > > > btw
> > > > I was not using an IDE but straight CLI.  Nevertheless, it worked.
> > > >
> > > > On Tue, Feb 13, 2018 at 11:53 AM, Meier, Caleb <
> > caleb.me...@parsons.com>
> > > > wrote:
> > > >
> > > >> 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
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > There are ways and there are ways,
> > > >
> > > > Geoffry Roberts
> > > >
> > >
> > >
> > >
> > > --
> > > There are ways and there are ways,
> > >
> > > Geoffry Roberts
> > >
> >
>
>
>
> --
> There are ways and there are ways,
>
> Geoffry Roberts
>

Re: First day with RYA questions.

[David Lotts]

Here are two manual pages.  First one sets up the web service on tomcat,
the other uses the java API.
https://github.com/apache/incubator-rya/blob/master/extras/rya.manual/src/site/markdown/quickstart.md
https://github.com/apache/incubator-rya/blob/master/extras/rya.manual/src/site/markdown/sm-sparqlquery.md
david.

On Tue, Feb 13, 2018 at 2:28 PM, David Lotts <dlo...@gmail.com> wrote:

> Correction: You can disable the RAT check with this:
> -Drat.skip
>
> You do not need a Mongo server unless you enable it in the configuration.
> If you do need it, it's a bug.  Although there is no way to separate the
> automated MongoDB unit tests from Accumulo, but tests create their own
> testing/mock server.
>
> You configure Accumulo parameters via the Rya configuration.  That can be
> done either by building up a config object, or using an XML config file.
> There are examples of both in various places.  Look at the examples
> project and the web project.  Ask again if you are not seeing it.
>
> You can also choose to use the web API or call the Rya API (OpenRDF AKA
> Sesame AKA rdf4j) directly.
>
> david.
>
> On Tue, Feb 13, 2018 at 2:08 PM, Geoffry Roberts <threadedb...@gmail.com>
> wrote:
>
>> All,
>>
>> Another question:  How do I point RYA at my Accumulo cluster?
>>
>> I have an Accumulo cluster running in the company cloud.
>>
>> Thanks
>>
>> On Tue, Feb 13, 2018 at 1:35 PM, Geoffry Roberts <threadedb...@gmail.com>
>> wrote:
>>
>> > git clean -fdx worked.  Never had that problem before.
>> >
>> > btw
>> > I was not using an IDE but straight CLI.  Nevertheless, it worked.
>> >
>> > On Tue, Feb 13, 2018 at 11:53 AM, Meier, Caleb <caleb.me...@parsons.com
>> >
>> > wrote:
>> >
>> >> 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
>> >>
>> >
>> >
>> >
>> > --
>> > There are ways and there are ways,
>> >
>> > Geoffry Roberts
>> >
>>
>>
>>
>> --
>> There are ways and there are ways,
>>
>> Geoffry Roberts
>>
>
>

Re: First day with RYA questions.

[David Lotts]

 Correction: You can disable the RAT check with this:
-Drat.skip

You do not need a Mongo server unless you enable it in the configuration.
If you do need it, it's a bug.  Although there is no way to separate the
automated MongoDB unit tests from Accumulo, but tests create their own
testing/mock server.

You configure Accumulo parameters via the Rya configuration.  That can be
done either by building up a config object, or using an XML config file.
There are examples of both in various places.  Look at the examples project
and the web project.  Ask again if you are not seeing it.

You can also choose to use the web API or call the Rya API (OpenRDF AKA
Sesame AKA rdf4j) directly.

david.

On Tue, Feb 13, 2018 at 2:08 PM, Geoffry Roberts 
wrote:

> All,
>
> Another question:  How do I point RYA at my Accumulo cluster?
>
> I have an Accumulo cluster running in the company cloud.
>
> Thanks
>
> On Tue, Feb 13, 2018 at 1:35 PM, Geoffry Roberts 
> wrote:
>
> > git clean -fdx worked.  Never had that problem before.
> >
> > btw
> > I was not using an IDE but straight CLI.  Nevertheless, it worked.
> >
> > On Tue, Feb 13, 2018 at 11:53 AM, Meier, Caleb 
> > wrote:
> >
> >> 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
> >>
> >
> >
> >
> > --
> > There are ways and there are ways,
> >
> > Geoffry Roberts
> >
>
>
>
> --
> There are ways and there are ways,
>
> Geoffry Roberts
>

Re: First day with RYA questions.

[David Lotts]

You can disable the RAT check with this:
-Drat.skip -l

Here is the command line I use.  It includes the optional projects and
skips tests.  Profile "enable-it" runs integrations tests, if they weren't
skipped.

mvn clean install  -P geoindexing -P benchmark -P enable-it -DskipTests
-Drat.skip -l ../rya$(date +%Y%m%d%H%M).log
david.

On Tue, Feb 13, 2018 at 11:53 AM, Meier, Caleb 
wrote:

> 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: Discussion: Next release - post v3.2.11 When, who, and what?

[David Lotts]

Yay!  Thanks Adina!  You can start right away, if you like, with the
one-time preparation portion of the wiki instructions.  Tell me your
twitter @name and I will authorize you to tweet as @ApacheRya.

My Apache-novice opinions are that we:

1- (when) start the release process now and be done before everybody
disappears for holidays.  It begins with the "Last call for PR's deadline"

2- (who) Adina

3- (what) put the RDF4J upgrade (a dream coming true) into a 4.0.0 in early
2018 or whenever it is stable.
Meanwhile, now, release our current master as 3.2.12.
Then for for each bug or feature, there must be two pull requests to port
to both v3 and v4.
Some features might skip v3 depending on the demand.

david.

Discussion: Next release - post v3.2.11 When, who, and what?

[David Lotts]

We soon will have plenty of new features and fixes for another release, if
we don't already.  So I'd like to kick off some discussion.  Requesting
comments for any of these:

1- When shall we target the next release? Start now?

2- Can we get a volunteer to be the next Release Manager?
There are a couple of us now listening to this list that can help you reify
the instructions[1], which are looking pretty good these days.  I'd be glad
to walk you through it.

3- Our current release is 3.2.11, shall we call this one 3.2.12 ?
Any breaking changes?  v3.3.0 or v4.0.0 ?

david.

[1] https://cwiki.apache.org/confluence/display/RYA/How+To+Release+Rya

Re: Twitter announce

[David Lotts]

>>Twitter shortens URLs itself and does not count the full len
> I read about that, but in practice it didn't happen.

I was wrong, I was expecting it to magically modify it.  But I see now any
size link is 23 chars.

david.

Re: Twitter announce

[David Lotts]

Kieth,
Thanks for the feedback!
> including any hashtags or mentions that may be relevant for the RDF
> side of things.  Similar to what you did for #BigData.

Definitely worth investigating!  I almost did #RDF but I didn't see it in
the auto-completion list that popped up.  I'm not sure what determines the
list.
I guess doing a search with #RDF and others will tell me what is worth
using.

> Twitter shortens URLs itself and does not count the full len

I read about that, but in practice it didn't happen.  I used bitly because
I could not get the twitter post box to generate a t.co link and I wanted
all the characters I could get.

Wow what flurry of activity it caused!  So many retweets and new
followers!  Thanks for your retweet!

david.

On Fri, Oct 27, 2017 at 2:26 PM, Keith Turner <ke...@deenlo.com> wrote:

> On Thu, Oct 26, 2017 at 11:56 AM, David Lotts <dlo...@gmail.com> wrote:
> > Below is the announcement that I plan to send from our twitter account.
> > Improvements?
> >
> > Does anyone know how to embed a page summary like this post?
> > https://twitter.com/TheASF/status/846668361253703680
> >
> > This is within three characters of the maximum.
> > ===
> > Apache Rya 3.2.11 incubating just released!
> > Rya is a #BigData RDF triple store using @ApacheAccumulo, @ApacheFluo
> > http://bit.ly/2izgy4I
> > ===
> > david.
>
> I know the tweet is out the door.  But for future I would recommend
> including any hashtags or mentions that may be relevant for the RDF
> side of things.  Similar to what you did for #BigData.  Not sure what
> that would be, but it would be worth investigating.
>
> Twitter shortens URLs itself and does not count the full len of your
> URL against the 140 char limit.  For example twitter created
> https://t.co/OP5xTuPT3r for your http://bit.ly/2izgy4I link.  Is there
> an advantage to using bit.ly link?
>

Re: Twitter announce

[David Lotts]

Below is the announcement that I plan to send from our twitter account.
Improvements?

Does anyone know how to embed a page summary like this post?
https://twitter.com/TheASF/status/846668361253703680

This is within three characters of the maximum.
===
Apache Rya 3.2.11 incubating just released!
Rya is a #BigData RDF triple store using @ApacheAccumulo, @ApacheFluo
http://bit.ly/2izgy4I
===
david.

Apache Rya 3.2.11-incubating released

[David Lotts]

The Apache Rya (Incubating) team is happy to announce the release of Apache
Rya 3.2.11-incubating:

https://rya.incubator.apache.org/news/2017/10/10/release-3.2.11/

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 Apache 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.


Thanks,
The Apache Rya team

=

*Disclaimer*

Apache Rya (incubating) is an effort undergoing Incubation at The Apache
Software Foundation (ASF), sponsored by the Incubator. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects. While
incubation status is not necessarily a reflection of the completeness or
stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.

Twitter announce

[David Lotts]

Josh,
I am about to send the release announcement.  Would you like to tweet it as
well?  I'm configuring my gmail account to send from dlo...@apache.org.
david.

On Thu, Jan 12, 2017 at 11:46 AM, Josh Elser  wrote:

> Since the responses have been mostly positive, I've just gone ahead and
> created an account.
>
> I am happy to transfer ownership of the actual account to anyone, as well
> as add anyone to the "team" via tweetdeck to be able to interact with the
> account.
>
> https://twitter.com/apacherya
>

Review website for the release 3.2.11 PR #4

[David Lotts]

I have changed the web site to include the release.
For your review, I have published them in a staging server here [1]
All this is described on the Rya website wiki instructions [2]

The updated and new pages are on [1] and click "get Rya" to get the
download page, then the release 3.2.11 download page, and the release notes.

You can put your comments here or on the pull request #4 for the markdown
[3]

I'll merge the pull requests Monday morning or so and then get the
announcement out after.

Thank you!

[1] https://dlotts.github.io/incubator-rya-site/
[2]
https://cwiki.apache.org/confluence/display/RYA/Website+rya.apache.org%2C+how+to+contribute+and+publish
[3] https://github.com/apache/incubator-rya-site/pull/4

Updated release info in the report

[David Lotts]

I updated Board report: I updated the release statement and the last
release date:

  * PPMC and IPMC voted to release 3.2.11

Date of last release:  2017-10-10

If you want a stronger statement, please update or let me know.

Thank you Billie for the report sign-off!

david.

Re: Merging Release back into Master?

[David Lotts]

What is wrong with having a merge commit?  I believe that will bring in the
modified pom.xml files that change to the next snapshot version:
3.2.12-SNAPSHOT .  These changes do not need to be chronologically correct.

Here is the quote from our awesome wiki instructions, the bold section is
what we are discussing:
https://cwiki.apache.org/confluence/display/RYA/How+To+Release+Rya



After the release has been approved by IPMC

Release the Jars
Go to https://repository.apache.org/ and release the staging
repository
Copy dev artifacts to release
Create a rel/ tag in Git

git checkout rya-incubating-3.2.10-rc3

git tag -a rel/rya-incubating-3.2.10 -m "rya-incubating-3.2.10
Release"

git push origin rel/rya-incubating-3.2.10
Merge Release branch into Master and Delete Release Branch





*git checkout mastergit merge 3.2.10-RC3git push
origin --delete 3.2.10-RC3*

**
Update the website
Send out an announce email


david.

On Thu, Oct 5, 2017 at 1:36 PM, Aaron D. Mihalik 
wrote:

> Those 10 commit are already in master.
>
> If we cherry pick the 2 release commits onto master, then that is wrong.
> Then it looks like the release contains those 10 new commits.
>
> If we do a merge, then we'll have the two release commits in the right
> spot, then the 10 commits, then a "merge commit".
>
> --Aaron
>
> On Thu, Oct 5, 2017 at 5:34 AM Smith, Andrew 
> wrote:
>
> > I'd like to avoid a force.  Could we cherry-pick those 10 commits over to
> > master?
> >
> > -Original Message-
> > From: Aaron D. Mihalik [mailto:aaron.miha...@gmail.com]
> > Sent: Thursday, October 05, 2017 1:17 PM
> > To: dev@rya.incubator.apache.org
> > Subject: Merging Release back into Master?
> >
> > Hey devs,
> >
> > How are we going to handle merging the release back into master?  master
> > has moved ahead since David marked the release and now the release branch
> > is "2 commits ahead, 10 commits behind master." [1]
> >
> > I propose pulling the 10 commits added to master on top of the release
> > branch and then doing a force push of that onto master.  what do you all
> > think?
> >
> > --Aaron
> >
> >
> > [1]
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.
> com_apache_incubator-2Drya_tree_3.2.11-2DRC3=DwIBaQ=
> Nwf-pp4xtYRe0sCRVM8_LWH54joYF7EKmrYIdfxIq10=U_RyVeYU_
> SBiw95AO0whBC3KHS5T7hkPx7rmMyjITF8=jWxjJgDMdB609alFiB_
> tKpRXzhLKdCmeM1o5d2GtOCI=XudaZE5HhUvHFqSzPwlwopkmViRx73iFyQ2iP_gOtxE=
> >
>

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

[David Lotts]

The Apache Rya community has voted and approved the proposed release of
Apache Rya 3.2.11 (Incubating) RC3.
[Second attempt, the first was rejected because my address was not yet
subscribed]

We now kindly request the Incubator PMC members review and vote on
this incubator
release.

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 Apache 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. More
information can be found at http://rya.incubator.apache.org/

[VOTE] Thread:
https://lists.apache.org/thread.html/c5b3e8294304b008344a08c
c63752213f15031f85531ac9a5adc737b@%3Cdev.rya.apache.org%3E

[VOTE RESULT] Thread:
https://lists.apache.org/thread.html/d5d0d24a80526c9c5c61b2a
65ba1e3bd06d8891c7df94f760d01fee3@%3Cdev.rya.apache.org%3E

The source zip, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/rya/rya-inc
ubating-3.2.11-rc3/


Ancillary artifacts such as poms, jars, wars. can be found here:
https://repository.apache.org/content/repositories/orgapache
rya-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://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;
a=commit;h=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://people.apache.org/keys/committer/dlotts.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/incubator/rya/KEYS

Issues that were closed/resolved for this release are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
ctId=12319020=12341279


The vote will be open for at least 72 hours plus a US Holiday weekend,
closing Tuesday 10/10/2017 1pm 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...


david.
David Lotts
dlo...@apache.org

[RESULT] [VOTE] Release Rya (Incubating) version 3.2.11 RC3

[David Lotts]

This vote passes with +5 Binding and +1 Non-binding votes.

+5 (binding):
 Adina Crainiceanu, Josh Elser, Puja Valiyil, Caleb Meier, David Lotts

+1 (non binding):
Jeff Dasch

Thanks for all the hard work!
I'll be sending a vote email to the IPMC soon.

david.

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

[David Lotts]

+1 (binding)

I ran tests on a AWS t2.micro instance.
A *t2.micro*  instance has 1 *vCPUs* and 1 GiB *RAM *
Just barely enough memory.
A second login to the box made Maven fail: out of memory, :-)
but it was able continue starting with the -rf option.

Some MongoDB integration tests failed, I believe due to insufficient
memory.  Needs to be revisited.  We need to improve mongoDB's startup error
reporting for integration tests.

david.

Re: Rya podling report draft - please comment

[David Lotts]

Working on the results now and then general@i.a.o. immediately after.
david.

On Mon, Oct 2, 2017 at 8:45 AM, Adina Crainiceanu  wrote:

> David, do you plan on starting a vote for Rya on the general@i.a.o list,
> since there are only positive votes from the dev list? Even if the vote
> does not conclude by the Wednesday deadline, we can submit the board report
> and then maybe modify it a few days later (before the mentor sign-off is
> due).
>
>
> On Sun, Oct 1, 2017 at 9:42 PM, Puja Valiyil  wrote:
>
> > Will the vote on the next release have ended before Wednesday?  It might
> > be worth waiting to submit until we can claim success there
> >
> > Sent from my iPhone
> >
> > > On Oct 1, 2017, at 9:27 PM, Adina Crainiceanu  wrote:
> > >
> > > Hi,
> > >
> > > I started the report due Wednesday. Please let me know how we can
> improve
> > > it. The draft is below:
> > >
> > > 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 release currently under vote on general@ list
> > >
> > >
> > > How has the project developed since the last report?
> > >
> > >  * Implemented new types of inferences: owl:hasValue, owl:unionOf,
> > > owl:equivalentClass, owl:allValuesFrom, owl:intersectionOf, owl: oneOf,
> > > owl:someValuesFrom, owl:ReflexiveProperty, owl:hasSelf
> > >  * Added documentation and examples for the use of shell, Prospector,
> and
> > > Pre-computed joins updater
> > >  * Removed/replaced code that used incopatible license (e.g. org.json,
> > > jcalendar)  - use ALv2 compatible license now
> > >
> > >
> > > How would you assess the podling's maturity?
> > > Please feel free to add your own commentary.
> > >
> > >  [ ] Initial setup
> > >  [ ] Working towards first release
> > >  [ ] Community building
> > >  [x] Nearing graduation
> > >  [ ] Other:
> > >
> > > Date of last release:
> > >
> > >  2016-10-28
> > >
> > > When were the last committers or PPMC members elected?
> > >
> > >  * PPMC member Caleb Meier elected on Jan 3rd, 2017
> > >
> > >
> > > Signed-off-by:
> > >
> > >  [ ](rya) Josh Elser
> > > Comments:
> > >  [ ](rya) Edward J. Yoon
> > > Comments:
> > >  [ ](rya) Venkatesh Seetharam
> > > Comments:
> > >  [ ](rya) Billie Rinaldi
> > > Comments:
> > >
> > > IPMC/Shepherd notes:
> > >
> > >
> > >
> > > Thank you,
> > > Adina
> > > --
> > > 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/
> >
>
>
>
> --
> 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/
>

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

[David Lotts]

​>Did you change something, or was it just my environment?
Nope, I don't anything was changed that would have fixed it.
david.

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

[David Lotts]

Thanks Adina!
Did you have any issues with Mongo this time?
david.

On Tue, Sep 26, 2017 at 10:26 PM, Adina Crainiceanu <ad...@usna.edu> wrote:

> +1
>
> I checked:
> -name includes incubating
> -DISCLAIMER exists and has the correct content
> -LICENSE exists
> -NOTICE exists
> -no unexpected binaries in the .zip file
> -can build from source, with included tests (I did mvm clean install)
> -checksums correct
>
> Thank you!
>
> Adina
>
> On Tue, Sep 26, 2017 at 1:27 PM, David Lotts <dlo...@gmail.com> 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://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> > incubating-3.2.11-rc3/
> >
> >
> > Ancillary artifacts such as poms, jars, wars. can be found here:
> > https://repository.apache.org/content/repositories/
> > 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://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> > 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://people.apache.org/keys/committer/dlotts.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
> >
> > Issues that were closed/resolved for this release are here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > 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...
> >
>
>
>
> --
> 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/
>

[RESULT] [VOTE] Release Rya (Incubating) version 3.2.11 RC2

[David Lotts]

The vote to release Rya (Incubating) version 3.2.11 RC2 has failed.
(I'm counting "recommend we fix" as a -1 vote)

-4 (binding): Josh Elser, Jen Brown, David Lotts, Caleb Meier
-1 (non binding): Jeff Dasch

The following Jira tasks have been created to capture the issues blocking a
successful release.
RYA-369 and RYA-370 are resolved, the rest probably by tonight.

RYA-372 [1] Replace org.json:json library with a compatibly licensed
alternative

RYA-373 [2] Benchmarks: JMH library cannot be distributed, make optional or
replace

RYA-370 [3] Geoindexing profile is broken and geo artifactIds should have
'rya.' prefix

   - Fixed a regression on the geoindexing profile in extras/pom.xml
   - Added a 'rya.' prefix to the new geo.* artifactIds to disambiguate
   generated artifacts.
   - Added pluginManagement definition for
   org.codehaus.mojo:license-maven-plugin for release auditing.
   - Specified an Xmx value for maven-failsafe-plugin for improved
   execution environment consistency on hosts with reduced memory.

RYA-369 [5] Release requires optional profile during prepare step
 Release candidate #3 (3.2.11-RC3) should be coming out  Monday.
Again, thanks for all the hard work!


[1] https://issues.apache.org/jira/browse/RYA-372
[2] https://issues.apache.org/jira/browse/RYA-373
[3] https://issues.apache.org/jira/browse/RYA-370
[4] http://giraph.apache.org/dependencies.html
[5] https://issues.apache.org/jira/browse/RYA-369
[6] https://mvnrepository.com/artifact/org.apache.giraph/giraph-dist/1.2.0

david.
​

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC2

[David Lotts]

-1 (binding)

We need add  RYA-370 since it fixes the optionalness of the GPL Geo
libraries, and a couple other little issues.
We did that already (PR is out there, thanks Jeff!).  Now we should go
ahead and make the benchmarks optional, and Giraph optional (see below),
since we get big benefit for short work.

Update on: JSON lib [1] we are not using the JSON  library directly -- that
is the org.json:json library with the incompatible (good/evil) license.
We are using Giraph libraries directly.  Maven[6] says the Giraph library
depends on the org.json:json library.  I could not find any mention of this
on the website.[4]  But I'll make an exclusion and see if breaks, then make
it Rya Giraph optional.
Excerpt from the maven dependency report:
$ mvn dependency:tree
...
[INFO] +- org.apache.giraph:giraph-core:jar:1.2.0:compile  ...
[INFO] |  +- org.json:json:jar:20090211:compile

Here is what we are doing for RC3.  RC3 should be out Monday after a 2 day
review time for these that should have PRs today:

RYA-372 [1] Replace org.json:json library with a compatibly licensed
alternative

RYA-373 [2] Benchmarks: JMH library cannot be distributed, make optional or
replace

RYA-370 [3] Geoindexing profile is broken and geo artifactIds should have
'rya.' prefix

   - Fixed a regression on the geoindexing profile in extras/pom.xml
   - Added a 'rya.' prefix to the new geo.* artifactIds to disambiguate
   generated artifacts.
   - Added pluginManagement definition for
   org.codehaus.mojo:license-maven-plugin for release auditing.
   - Specified an Xmx value for maven-failsafe-plugin for improved
   execution environment consistency on hosts with reduced memory.

RYA-369 [5] Release requires optional profile during prepare step
[1] https://issues.apache.org/jira/browse/RYA-372
[2] https://issues.apache.org/jira/browse/RYA-373
[3] https://issues.apache.org/jira/browse/RYA-370
[4] http://giraph.apache.org/dependencies.html
[5] https://issues.apache.org/jira/browse/RYA-369
[6] https://mvnrepository.com/artifact/org.apache.giraph/giraph-dist/1.2.0

david.

Re: third party licenses examined for 3.2.11 RC2

[David Lotts]

​Here is my completed analysis of our third party licenses.

Result: We have two Licenses not allowed for Apache projects.  See the
bottom.
The question is, is this a blocker for the release?  Can we make a Jira
task to fix for the next version?  One of them: JSON,  just  switched to
category X after our last release.

Using this history as a guide:
https://www.mail-archive.com/dev@rya.incubator.apache.org/msg00969.html
and this :
https://issues.apache.org/jira/browse/RYA-177

in order: the good, the bad:

### BSD  good  from:  http://asm.ow2.org/license.html
 (Unknown license) ASM Core (asm:asm:3.1 - http://asm.objectweb.org/asm/
)

### Good already excluded, see RYA-200 Remove findbugs:jsr305 Dependency
 (GNU Lesser Public License) FindBugs-Annotations
(com.google.code.findbugs:annotations:2.0.2 - http://findbugs.sourceforge.
net/)

### Apache project -- Good
 (Unknown license) commons-beanutils (commons-beanutils:commons-bea
nutils:1.7.0
- no url defined)

### Already exclusion from another library, its Good
 (HSQLDB License) HSQLDB (hsqldb:hsqldb:1.8.0.10 - http://hsqldb.org/)

### used by many Apache projects -- Good
 (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)

### BSD license -- good from http://www.antlr.org/about.html
 (Unknown license) Antlr 3.4 Runtime (org.antlr:antlr-runtime:3.4 -
http://www.antlr.org)

### Apache -- Good
 (Unknown license) Jettison (org.codehaus.jettison:jettison:1.1 - no
url defined)

### Apache licensed -- Good, all spring stuff
 (Unknown license) spring-aop (org.springframework:spring-ao
p:3.0.5.RELEASE)
 (Unknown license) spring-asm (org.springframework:spring-as
m:3.0.5.RELEASE)
 (Unknown license) spring-beans (org.springframework:spring-be
ans:3.0.5.RELEASE)
 (Unknown license) spring-context (org.springframework:spring-co
ntext:3.0.5.RELEASE)
 (Unknown license) spring-context-support (org.springframework:spring-co
ntext-support:3.0.7.RELEASE
 (Unknown license) spring-core (org.springframework:spring-co
re:3.0.5.RELEASE
 (Unknown license) spring-expression (org.springframework:spring-ex
pression:3.0.5.RELEASE
 (Unknown license) spring-tx (org.springframework:spring-tx
:3.0.5.RELEASE

### Apache project -- Good, BTW: As of 2010-09-01, the ORO project is
retired.
 (Unknown license) oro (oro:oro:2.0.8 - no url defined)
### Apache project -- Good, by looking at the source code
 (Unknown license) regexp (regexp:regexp:1.3 - no url defined)
### Apache licensed -- Good,
https://mvnrepository.com/artifact/org.osgi/org.osgi.compendium
 (Unknown license) org.osgi.compendium (org.osgi:org.osgi.compendium:
4.2.0)
 (Unknown license) org.osgi.core (org.osgi:org.osgi.core:4.2.0 )
### Python license is compat,  -- Good, similar to
http://www.jython.org/license.html
 (Jython Software License) Jython (org.python:jython:2.5.3 -
http://www.jython.org/)

## end of good.

### BAD: JSON: MIT- with evil clause
### As of 2016-11-03 this has been moved to the 'Category X' license list
### ( "The Software shall be used for Good, not Evil."  from
http://www.json.org/license.html   )
###  Consider replacing with this drop in replacement:
### https://mvnrepository.com/artifact/com.tdunning/json
### from: https://stackoverflow.com/questions/10396176/org-
json-jar-provisioning
### other alternatives:
### https://wiki.debian.org/qa.debian.org/jsonevil
  (provided without support or warranty) JSON (JavaScript Object Notation)
(org.json:json:20090211 - http://www.json.org/java/index.html)


### BAD: GPL with classpath exception is explicitly not compatible

 (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/)



>>

third party licenses examined for 3.2.11 RC2

[David Lotts]

​Here is my analysis of our third party licenses.

Using this history as a guide:
https://www.mail-archive.com/dev@rya.incubator.apache.org/msg00969.html
and this :
https://issues.apache.org/jira/browse/RYA-177

in order: the good, the bad, the to-do:

### BSD  good  from:  http://asm.ow2.org/license.html
 (Unknown license) ASM Core (asm:asm:3.1 - http://asm.objectweb.org/asm/
)

### already excluded, see RYA-200 Remove findbugs:jsr305 Dependency
 (GNU Lesser Public License) FindBugs-Annotations
(com.google.code.findbugs:annotations:2.0.2 - http://findbugs.sourceforge
.net/)

### apache project
 (Unknown license) commons-beanutils (commons-beanutils:commons-
beanutils:1.7.0
- no url defined)

### Already exclusion from another library, its OKAY
 (HSQLDB License) HSQLDB (hsqldb:hsqldb:1.8.0.10 - http://hsqldb.org/)

### used by many Apache projects
 (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)

### BSD license good from http://www.antlr.org/about.html
 (Unknown license) Antlr 3.4 Runtime (org.antlr:antlr-runtime:3.4 -
http://www.antlr.org)

### apache
 (Unknown license) Jettison (org.codehaus.jettison:jettison:1.1 - no
url defined)

### Apache licenced, all spring stuff
 (Unknown license) spring-aop (org.springframework:spring-
aop:3.0.5.RELEASE)
 (Unknown license) spring-asm (org.springframework:spring-
asm:3.0.5.RELEASE)
 (Unknown license) spring-beans (org.springframework:spring-
beans:3.0.5.RELEASE)
 (Unknown license) spring-context (org.springframework:spring-
context:3.0.5.RELEASE)
 (Unknown license) spring-context-support (org.springframework:spring-
context-support:3.0.7.RELEASE
 (Unknown license) spring-core (org.springframework:spring-
core:3.0.5.RELEASE
 (Unknown license) spring-expression (org.springframework:spring-
expression:3.0.5.RELEASE
 (Unknown license) spring-tx (org.springframework:spring-
tx:3.0.5.RELEASE

## end of good.

### MIT- with evil clause ( "The Software shall be used for Good, not Evil."
from http://www.json.org/license.html   )  Consider replaceing with this
drop in replacement:
https://mvnrepository.com/artifact/com.tdunning/json
from: https://stackoverflow.com/questions/10396176/org-json-jar-provisioning
  (provided without support or warranty) JSON (JavaScript Object Notation)
(org.json:json:20090211 - http://www.json.org/java/index.html)


### BAD I don't know about JMH libs:

 (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/)

That is as far as I got.  TODO:
 (Unknown license) oro (oro:oro:2.0.8 - no url defined)
 (Unknown license) regexp (regexp:regexp:1.3 - no url defined)
 (Unknown license) org.osgi.compendium (org.osgi:org.osgi.compendium:
4.2.0)
 (Unknown license) org.osgi.core (org.osgi:org.osgi.core:4.2.0 )
 (Jython Software License) Jython (org.python:jython:2.5.3 -
http://www.jython.org/)

Re: [VOTE] Release Rya (Incubating) version 3.2.11 RC2

[David Lotts]

> , nexus seems to have a lot of geoindexing
> artifacts in it.  Probably need to revist the extras/pom.xml as it
> looks like there's a regression in there.

The last release 3.2.10 has no geoindexing jars in Nexus.  I see what you
are saying.  This release candidate has folders for each.
https://repository.apache.org/content/repositories/releases/org/apache/rya/

 I unfortunately missed your renaming recommendation from your review.

 david.

On Wed, Sep 13, 2017 at 9:25 AM, Jeff Dasch <hcs...@gmail.com> wrote:

> Also, it appears that there is an issue with this project as well:
>
> grep -r 3.2.10-incubating-SNAPSHOT rya-project-3.2.11-incubating
> rya-project-3.2.11-incubating/osgi/sesame-runtime-osgi/pom.xml:
> *3.2.10-incubating-SNAPSHOT*
>
> On Wed, Sep 13, 2017 at 12:05 AM, Jeff Dasch <hcs...@gmail.com> wrote:
>
> > It is fine to not to release the geoindexing artifacts, but we need all
> of
> > the pom version strings to be consistent (and correct) so that if one did
> > want to build them with the geoindexing profile, they can.
> >
> > Speaking of artifacts, nexus seems to have a lot of geoindexing artifacts
> > in it.  Probably need to revist the extras/pom.xml as it looks like
> there's
> > a regression in there.
> >
> >
> >
> > On Tue, Sep 12, 2017 at 10:22 PM, Puja Valiyil <puja...@gmail.com>
> wrote:
> >
> >> Don't we not release the geoindexing artifacts? Sorry if I'm being slow
> >> here
> >>
> >> Sent from my iPhone
> >>
> >> > On Sep 12, 2017, at 5:23 PM, Jeff Dasch <hcs...@gmail.com> wrote:
> >> >
> >> > -1 (non-binding)
> >> >
> >> > The pom for rya.pcj.functions.geo references a parent artifact with a
> >> > 3.2.11-incubating-SNAPSHOT version:
> >> > grep -r 3.2.11-incubating-SNAPSHOT rya-project-3.2.11-incubating
> >> > rya-project-3.2.11-incubating/extras/rya.pcj.fluo/rya.pcj.fu
> >> nctions.geo/pom.xml:
> >> > 3.2.11-incubating-SNAPSHOT
> >> >
> >> > Need to clean your maven repo and build with the geoindexing profile
> to
> >> see
> >> > this issue.  RC1 was also affected.
> >> >
> >> >
> >> >> On Mon, Sep 11, 2017 at 5:44 PM, David Lotts <dlo...@gmail.com>
> 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://dist.apache.org/repos/dist/dev/incubator/rya/rya-
> >> >> incubating-3.2.11-rc2/
> >> >>
> >> >>
> >> >> Ancillary artifacts such as poms, jars, wars. can be found here:
> >> >> https://repository.apache.org/content/repositories/
> >> >> orgapacherya-1006/org/apache/rya/rya-project/3.2.11-incubating/
> >> >>
> >> >> The Git tag is rya-incubating-3.2.11-rc2
> >> >> The Git commit ID is f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
> >> >> https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;
> >> a=commit;h=
> >> >> f9e5787a4057d8fbaacc8d22e4de5d86fcb45ba8
> >> >>
> >> >> Checksums of rya-project-3.2.11-source-release.zip:
> >> >> MD5: aa4dff6ed9664fb1e06752389bebcea9
> >> >> SHA1: a801e7814bdd09f603256858e4511db4b59605b2
> >> >> SHA512:
> >> >> 66ad82cf9f6c04e5ab230b609fb902f071fd77ff63989f3fa2e331ddcc34
> >> >> 3b1ad7ee7d3ae3bbd138b399e59c565a57457060c357c01a805c0b4bbe2cd0c34dd9
> >> >>
> >> >> Release artifacts are signed with the following key:
> >> >> https://people.apache.org/keys/committer/dlotts.asc
> >> >>
> >> >> KEYS file available here:
> >> >> https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
> >> >>
> >> >> Issues that were closed/resolved for this release are here:
> >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> >> projectId=12319020=12341279
> >> >> (Should be complete now.)
> >> >>
> >> >> The vote will be open for at least 72 hours starting Monday 9/11/2017
> >> and
> >> >> close at Friday 9/15/2017 10am 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: [RESULT] [VOTE] Release Rya (Incubating) version 3.2.11 RC1

[David Lotts]

Adina -- Included sha512 and updated the wiki!
Josh -- thanks for looking at the sources.

RC2 is out.  Working on the announcement and some verification.

david.
​

[RESULT] [VOTE] Release Rya (Incubating) version 3.2.11 RC1

[David Lotts]

Hello,

The vote to release Rya (Incubating) version 3.2.11 RC1 has failed.

-1 (binding): Josh Elser
+0 (non binding): Jeff Dasch

The following Jira tasks have been created to capture the issues blocking a
successful release.
We have fixed all the following which should take care of all of the
feedback, with the exception of Adina's which perhaps we can address in a
future release or perhaps RC3.

RYA-360 [1]  Header issues: Correct Notice file year, fix wrong Apache
License, s/RYA/Apache Rya/ in the README  pull request #222  [2]
This task fixes three issues:
- wrong license header (including a copyright line which should not be
present)
- Copyright year in NOTICE needs updating
- s/RYA/Apache Rya/ in the README

RYA-361 [3] Remove JCalendar library from merge/copy/export #224 [4]
- rya.export depends on JCalendar which is LGPL (brought in by RYA-123)

RYA-362 [5] Improve no-arg error message for shell command create-pcj  #223
[6]
- UX nit on the rya.shell

The following Jira task has been created to capture all of the issues that
will be resolved in the next RC:
 RYA-367 Perform 3.2.11-RC2 Release [7]

Release candidate #2 (3.2.11-RC2) should be coming out  Monday.
Thanks for all the hard work!


[1] https://issues.apache.org/jira/browse/RYA-360
[2] https://github.com/apache/incubator-rya/pull/222
[3] https://issues.apache.org/jira/browse/RYA-361
[4] https://github.com/apache/incubator-rya/pull/224
[5] https://issues.apache.org/jira/browse/RYA-362
[6] https://github.com/apache/incubator-rya/pull/223
[7] https://issues.apache.org/jira/browse/RYA-367

david.
​

Re: Error: MongoDBRdfConfiguration.setMongoClient(NULL)

[David Lotts]

>
> Those who use Rya with Accumulo probably don't need
> MongoDB, but they would still have to have MongoDB installed and running to
> get past these tests and be able to build with a simple mvn clean install.
>

Good point, perhaps a profile to skip-mongodb-tests.
david.
​

Error: MongoDBRdfConfiguration.setMongoClient(NULL)

[David Lotts]

Adina,
I have seen this error. From your email:

> java.lang.NullPointerException: null
> at com.google.common.base.Preconditions.checkNotNull(
Preconditions.java:191)
> at org.apache.rya.mongodb.MongoDBRdfConfiguration.setMongoClient(
MongoDBRdfConfiguration.java:267)

MongoDB did not start for some reason.  I know of two reasons.

1. MongoDB can't be run on a VM in a drive shared with Windows.  Look for
an "fsync" error.

MongoDB cannot have its files on a shared drive that does not support
“fsync”.

See https://github.com/mvertes/docker-alpine-mongo/issues/1

2. This log output accompanied other tests that failed for "out of memory",
so we think that is the root cause:


2017-08-31 14:24:48,466 INFO  [Thread-3] mongodb.MockMongoFactory
(Slf4jLevel.java:log(42)) -

[initandlisten] terminate() called. An exception is active; attempting to
gather more information[mongod output]

[initandlisten] std::exception::what(): Resource temporarily
unavailable[mongod output]

Actual exception type: std::system_error[mongod output]


For some reason it gets logged as [INFO] so you need to turn that on to see
what Mongo is reporting.
Put this in your test file: org.apache.rya.mongodb.
MongoDBQueryEngineTest
Put this at the top of the @Before junit method:



org.apache.log4j.BasicConfigurator.configure();


Now all logging will go to stdout.
Look for output from mongodb.MockMongoFactory *and*[mongod output]
and send it here if you want more eyes on it.

I'm going to write a Jira ticket to request that we make this more obvious.
david.

[VOTE] Release Rya (Incubating) version 3.2.11 RC1

[David Lotts]

I am pleased to be calling this vote for the source release of Apache Rya
(Incubating), version 3.2.11.
Since I am sending this on the eve of a holiday weekend in the USA, we'll
start the vote on Tuesday, although voting early is fine.

The source zip, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-3
.2.11-rc1/

Ancillary artifacts such as poms, jars, wars, ect. can be found here:
https://repository.apache.org
/content/repositories/orgapacherya-1005/org/apache/rya/rya-project/3
.2.11-incubating/

The Git tag is rya-incubating-3.2.11-rc1
The Git commit ID is 2588d189d483698c0d2cd30e1e7c28f18c3d6871
https://git-wip-us.apache.org/repos/asf
?p=incubator-rya.git;a=commit;h=2588d189d483698c0d2cd30e1e7c28f18c3d6871

Checksums of rya-project-3.2.10-source-release.zip:
SHA1: f40fe200b6768076d28ccd7b3d613ff6
MD5: f40fe200b6768076d28ccd7b3d613ff6

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/dlotts.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/incubator/rya/KEYS

Issues that were closed/resolved for this release are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319020=12341279
(This is very incomplete as many items are yet to be tagged for the
release.  I'll take care of that after the Labor day Monday along with
release notes for the website.)

The vote will be open for at least 72 hours starting Tuesday 9/12/2017 and
close at 9/15/2017 Noon 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...

Release 3.2.11

[David Lotts]

​This is last call for PR's to include in this release.
Let me know ASAP if you intend to have a PR included.
If I don't hear anything, I'll try to get a release candidate out today or
Monday.

david.

Re: Send feature descriptions for the release

[David Lotts]

thanks Aaron!  I would say they are award-worthy.
david.

On Fri, Aug 18, 2017 at 3:37 PM, Aaron D. Mihalik <aaron.miha...@gmail.com>
wrote:

> David,  I think that only two of my commits are noteworthy:
>
> RYA-337 - Enabled query batching for MongoDB DAO. Previously, the MongoDB
> DAO sent one Statement Pattern query at a time to Mongo.  Now, the DAO
> batches Statement Pattern queries and performs a client side join (like the
> Accumulo DAO).
>
>
> RYA-323 - Enabled Multi Var Geo Functions. Previously, all Rya GeoSPARQL
> functions required that at least one parameter was a constant (eg
> "geof:sfWithin(?wkt, "POLYGON(( ... )))" ).  now, we can solve filters that
> have no constants (eg "geof:near(?wkt2, ?wkt1))")
>
> --Aaron
>
>
> On Fri, Aug 18, 2017 at 3:13 PM Aaron D. Mihalik <aaron.miha...@gmail.com>
> wrote:
>
> > Hey David,
> >
> > This might be helpful:  I scrapped the git logs and put together a
> > spreadsheet of everything committed since last release.  It's up on
> google
> > docs at:
> >
> >
> > https://docs.google.com/spreadsheets/d/1mwp0HRHBVrH_
> TR1ZGOfO8d3044NbrMJ3wO5TtyRp5So/edit?usp=sharing
> >
> > --Aaron
> >
> > On Fri, Aug 18, 2017 at 2:44 PM David Lotts <dlo...@gmail.com> wrote:
> >
> >> Lets get this started!
> >>
> >> Contributors, please send me one or two English sentence for each major
> >> feature that you principally worked on, describing the feature.  This
> >> would
> >> be all features since October.  I will compile this into the release
> >> notes.  I will also link the Jira generated release notes to be
> exhaustive
> >> <
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12341279==12319020=Create
> >> >
> >> .
> >>
> >> I need them no later than Wednesday 8/23/2017.
> >>
> >> You can skip bugs unless you think them noteworthy.  Multiple sentences
> >> might be appropriate for some features.
> >>
> >> Send them either to this list or to me directly.
> >> thanks,
> >> david.
> >>
> >
>

Send feature descriptions for the release

[David Lotts]

Lets get this started!

Contributors, please send me one or two English sentence for each major
feature that you principally worked on, describing the feature.  This would
be all features since October.  I will compile this into the release
notes.  I will also link the Jira generated release notes to be exhaustive

.

I need them no later than Wednesday 8/23/2017.

You can skip bugs unless you think them noteworthy.  Multiple sentences
might be appropriate for some features.

Send them either to this list or to me directly.
thanks,
david.

Re: next release of Rya?

[David Lotts]

​I'll volunteer to manage the release this time.
I'll get started late this week or Monday.

Does anybody know how to get edit karma for our wiki?
I have some updates to:
https://cwiki.apache.org/confluence/display/RYA/Contributing+to+Rya

david.

Re: please review changes to the web site (PR)

[David Lotts]

I have modified for all your suggestions, Adina.
Again, here is the preview site:

https://dlotts.github.io/incubator-rya-site

Also, here are instructions for modifying and hosting for review in the
README.md:

https://github.com/DLotts/incubator-rya-site/tree/showrelease

david.

Re: please review changes to the web site (PR)

[David Lotts]

I worked out the details for previewing the site using github pages.
Take a look here:
https://dlotts.github.io/incubator-rya-site/

I just now saw your note and browsed your review comments.  Thank you!

I am out tomorrow, so I'll finish reading/fixing on Monday unless someone
else wants to continue.

david.

On Thu, Jul 27, 2017 at 2:45 PM, Adina Crainiceanu <ad...@usna.edu> wrote:

> David,
>
> Thanks a lot on making the changes to the website - way past time to add
> details about our first release. I made some comments on the PR in Github.
> Can you see them? I thought that an email will be generated to this list
> for the comments, but I did not see it.
>
> I don't know how to review the changes as rendered HTML. I just generated
> the website with bundle exec jekyll serve and looked at localhost:4000
>
>  Adina
>
>
> On Mon, Jul 24, 2017 at 3:26 PM, David Lotts <dlo...@gmail.com> wrote:
>
> > And does anyone know how to review the changes as rendered HTML?
> >
> > You can see the changes as rendered Markdown:
> > https://github.com/apache/incubator-rya-site/pull/2
> >
> > or as raw HTML,
> > https://github.com/apache/incubator-rya-site/pull/3
> >
> > but I don't know how to show you without hosting it somewhere.
> >
> > Note the way this works:
> > - the master branch has the markdown that gets processed by the Jekyll
> > tool.
> > - the asf-site branch hosts the static HTML created by the Jekyll tool.
> >
> > david.
> >
>
>
>
> --
> 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/
>

please review changes to the web site (PR)

[David Lotts]

And does anyone know how to review the changes as rendered HTML?

You can see the changes as rendered Markdown:
https://github.com/apache/incubator-rya-site/pull/2

or as raw HTML,
https://github.com/apache/incubator-rya-site/pull/3

but I don't know how to show you without hosting it somewhere.

Note the way this works:
- the master branch has the markdown that gets processed by the Jekyll tool.
- the asf-site branch hosts the static HTML created by the Jekyll tool.

david.

Re: Rya's state

[David Lotts]

I'm going to add our release to the download page.
How does one get karma to merge pull requests?
I need it for github
*apache/incubator-rya-site *or do I need to do it from the Apache Git repo?
It has a PR for a bad link that I'd like to merge.

For the download page, I'll do a proper PR so we can review before we merge
and publish it.
david.

On Fri, Jul 7, 2017 at 5:07 PM, Josh Elser  wrote:

> Oh good catch, Dave! I didn't even notice that the website was never
> updated.
>
> Can someone volunteer to look into this over the weekend, please?
>
>
> On 7/5/17 2:38 PM, Dave Fisher wrote:
>
>> Hi -
>>
>> I’m doing a quick shepherd check of Rya.
>>
>> I look at http://rya.incubator.apache.org/download/ and it does not
>> provide ANY information about your release last October. That really does
>> not help the project build a community. Please look into your website and
>> give it the care it needs.
>>
>> Regards,
>> Dave
>>
>> On 2017-07-05 10:32 (-0700), Josh Elser  wrote:
>>
>>> Hi,
>>>
>>> Sorry for being a bit more hands-off as of late. Professional and
>>> personal life has been quite ramped up for me :). Looking over the July
>>> 2017 report, it made me wonder what the next steps for Rya are and how I
>>> can help push you all in this process!
>>>
>>> * What is the next release?
>>> - What would be contained?
>>> - What's left to be implemented?
>>> - When should it be released by?
>>> * Who is in the pipeline to be invited to committer (rhetorical -- these
>>> discussions _must_ happen in private@)
>>> * What contributions need help/shephering? I saw one[1] in a quick glance
>>>
>>> - Josh
>>>
>>> [1] https://github.com/apache/incubator-rya/pull/171
>>>
>>>

Ready for mentor review: Podling Report - July 2017

[David Lotts]

I added Caleb's feature list and it's all  now in the wiki, possibly ready
for review by mentors!

I have incubator Wiki access now .
(I had to click "create account", then request permission from
gene...@incubator.apache.org  -- thanks Aaron)
david.

On Mon, Jul 3, 2017 at 9:51 AM, Meier, Caleb 
wrote:

> Looks good David!  Thanks for putting this together.  I would also add the
> following under "How has the project developed since the last report":
> (1) expanded reasoning capabilities by implementing owl:hasValue inference
> (2) added construct query support, aggregation support (sums, counts,
> averages, max, min), and geo temporal filtering to Rya Fluo Incremental
> Updater.
> (3) Mongo backed entity centric index
> (4) Merged pull request for singleton AccumuloMinicluster to speed up
> integration tests
>
> Can anyone think of anything else?  David, will you be able to submit the
> report?
>

Re: Podling Report Reminder - July 2017

[David Lotts]

I was not able to log in to the wiki event though id.apache.org said I was
logged in.  Below is my draft report.  It belongs here:
https://wiki.apache.org/incubator/July2017
david.

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.
  3. Continue to harden and develop core Rya features to improve user
 experience

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?

  * Adina Crainiceanu presented two Rya talks at Apache Big Data North
America on May 16-18 in Miami:
** a 10 minute presentation at the Podling Shark Tank, and a
** full presentation on Apache Rya - A Scalable RDF Triple Store.
  * Pull Requests and issue reports from non-committers which are
integrated into the repository continue to be received


How has the project developed since the last report?
  * Resolved a handful of issues that users have encountered
  * geoTemporal Indexing
  * [many MORE Feature additions here ...]

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2016-10-28

When were the last committers or PPMC members elected?
* New committer and PPMC member David Lotts elected on Oct 25, 2016
* New PPMC member Caleb Meier elected on Jan 3rd, 2017



Signed-off-by:

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

IPMC/Shepherd notes:






On Wed, Jun 28, 2017 at 7:56 PM, Josh Elser <els...@apache.org> wrote:

> I can help out with the logistics if someone wants to take on the cross of
> word-smithing. There are plenty of good previous reports[1] to take
> inspiration from :)
>
> [1] https://wiki.apache.org/incubator/January2017
>
>
> On 6/28/17 2:05 AM, Adina Crainiceanu wrote:
>
>> Rya enthusiasts,
>>
>> Is anyone volunteering to work on the next board report due July 5th? I'm
>> traveling while on vacation.
>> For the community development section of the report, I would be include
>> the
>> 2 Rya talks I gave at Apache Big Data North America on May 16-18 in Miami:
>> a 10 minutes presentation at the  Podling Shark Tank, and a full
>> presentation on Apache Rya - A Scalable RDF Triple Store.
>>
>> Adina
>>
>> On Wed, Jun 28, 2017 at 2:54 AM <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.
>&g

Re: Podling Report Reminder - July 2017

[David Lotts]

I'll get it started.  Calib said he would take a look at my draft.

AFAIK, no one people have joined or departed.  None since Caleb, me, and
Billie as reported last time.  Let me know if you know otherwise.

david.

On Fri, Jun 30, 2017 at 2:04 PM, Puja Valiyil  wrote:

> Thanks Josh!  Don't know how I missed that.
> Does anyone want to volunteer to put it together?
>
> Sent from my iPhone
>
> > On Jun 30, 2017, at 11:17 AM, Josh Elser  wrote:
> >
> > https://lists.apache.org/thread.html/14fbb6ec756261cd522a4a17db7445
> 3d8382d117041af9995620e44a@%3Cdev.rya.apache.org%3E
> >
> > ;)
> >
> >> On 6/30/17 9:17 AM, Meier, Caleb wrote:
> >> 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
>

Rya Jira issues up for grabs and long ago assigned

[David Lotts]

We’ve noticed some awesome efforts on fixing some old annoying Jira tickets.

We love seeing those things closed!



Don’t let this slow you down, but keep in mind: if an issue is already
assigned to someone else long ago, please post your intention on the Jira,
(or on this list if you want extra attention or lack postability/karma)
before you start work on it.  Someone can officially assign it to you, and
as a bonus, you might get some partial code, or background information from
the old assignee.



Also there are bunch of unassigned tasks.  I know one or two that already
have a solution worked out in the Jira comments.



david.

Geo functions from Latest RDF4J Jar

[David Lotts]

If you have any opinions or knowledge on this, I'd love to hear it.  I plan
to make this part of Apache Rya, so I want to know before I start.

I want to use the Geo FILTER functions from the latest RDF4J Jar to use
with the Fluo Query Framework.  I was thinking of all kinds of twisted
Maven dependency work-arounds/hacks.  And just now it occurred to me that
the new libraries are completely repackaged from the OpenRDF/Sesame
versions that the rest of Rya uses -- there should not be any conflicts!

So now I'm thinking of adding the RDF4J v4 libraries that I need and
treating them as unrelated libraries.

The complicating factor here is that these will be geo libs with
dependancies on GeoTools (via Spatial4J).  This means it will go into the
optional Geo profile.

david.

Re: rya parser failed on parsing large numeric type

[David Lotts]

> Good idea, but why can’t you use LongEncoder which is also 8 bytes?
It's great that it works for you!  It would probably work for lots of cases
since a long is large.
I am seeing 16 bytes.  Maybe we are looking at something different:
org.calrissian.mango.types.encoders.lexi.LongEncoder.class

However it does not meet the RDF specifications which I believe allow it to
be unlimited length.
I'm going to paste my solution above into RYA-43 in case someone wants to
implement it.

david.

On Wed, Jan 11, 2017 at 1:20 PM, Ly, Kiet <kiet...@finra.org> wrote:

> 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<Long, String> INTEGER_STRING_TYPE_ENCODER
> = LexiTypeEncoders.longEncoder();
>
>
>
> On 1/11/17, 12:51 PM, "David Lotts" <dlo...@gmail.com> 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 <dlo...@gmail.com> 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.
>

Spatial4J

[David Lotts]

I recently came across Spatial4J.  I wanted to let Rya folks know about it,
and see if anyone has experience with it, especial in regard to using it as
alternative to JTS/GeoTools libraries and relationship to GeoMesa.

It is a spatial / geospatial library with an Apache license that is used by
the Apache Lucene project.
It seems to have a lot of what I need for doing filter functions in SPARQL.

Also of special interest to Ryians (Ryamancers? Ryaphiles?) is that
Spatial4J is used by the latest version of RDF4J (AKA OpenRDF/Seseme).  Rya
heavily depends on RDF4J, but is not yet up to the version that features
Spatial4J.

Because it is ASL licensed, it might make a good alternative to our
dependencies on JTS libraries.  However, there is an "optional" dependency
for JTS for polygons.  I'm wondering if that means that it won't handle
polygons unless the JTS libraries (LGPL) are included.  Perhaps it just a
convenience for people that are already using the JTS geometry classes.
This probably become clear once I get more into the API.

david.

Re: answered: RAT complains about tinkerpop.rya

[David Lotts]

So both Kiet and I suffered from a non-fresh working clone.  RAT is
sensitive to files that mvn clean and git checkout leave behind.
For Kiet, you were building with -Pgeoindexing, and then without.  Without
-Pgeoindexing, RAT sees a subfolder, not a submodule, and does not exclude
the Eclipse files.

david.

On Thu, Jan 19, 2017 at 2:46 PM, Aaron D. Mihalik <aaron.miha...@gmail.com>
wrote:

> oh, "optional geoindexing".  It looks like you had eclipse build
> rya.geoindexing
>
> So, two options:
>
> 1. Start building rya.geoindexing , ie: mvn clean install -Pgeoindexing
>
> 2. Blow away every file in the rya.geoindexing  project that is not in git
> ie: git clean -dxfn extras/rya.geoindexing/
>
> For #2, the command I gave is a 'dry-run'.  you should see a list like
> this:
>
> Would remove extras/rya.geoindexing/.classpath
> Would remove extras/rya.geoindexing/.project
> Would remove extras/rya.geoindexing/.settings/
> Would remove extras/rya.geoindexing/target/
>
> If you're satisfied with the list of files that it'll remove, re-run the
> command as: git clean -dxf extras/rya.geoindexing/
>
> On Thu, Jan 19, 2017 at 12:54 PM Ly, Kiet <kiet...@finra.org> wrote:
>
> > [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.
> > >>
> > >
> >
> >
> >
>

answered: RAT complains about tinkerpop.rya

[David Lotts]

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.

Re: Bulk Upload issues

[David Lotts]

Looks like you are missing an accumulo jar.
However the Hadoop command finds it's classpath, you need to point it to
the place where the vagrant script copies all the jars.
david.



On Fri, Jan 13, 2017 at 12:11 PM, Davide Allavena <
davide.allav...@synapta.it> wrote:

> Hello,
> while testing the vagrant file found here (
> https://github.com/apache/incubator-rya/tree/master/
> extras/vagrantExample/src/main/vagrant)
> i was unable to do bulk upload as described in the documentation.
>
> In order to perform SELECT * { s? p? o? } queries I built Rya from master
> (at commit f58eeda) substituting the generated war in the vagrant File.
>
> Moving either the RDF file and rya.mapreduce-3.2.11-
> incubating-SNAPSHOT.jar
> in the VM created from the Vagrantfile and inside the VM i gave the
> command:
>
> vagrant@rya-example-box:~$ hadoop jar
> rya.mapreduce-3.2.11-incubating-SNAPSHOT.jar
>  org.apache.rya.accumulo.mr.tools.RdfFileInputTool -Dac.zk=localhost:2181
> -Dac.instance=dev -Dac.username=root -Dac.pwd=root
> -Drdf.tablePrefix=triplestore_ -Drdf.format=N-Triples
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/accumulo/core/client/security/tokens/AuthenticationToken
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.apache.hadoop.util.RunJar.run(RunJar.java:214)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:136)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.accumulo.core.client.security.tokens.AuthenticationToken
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 4 more
>
> The jar i used is located
> in dao/accumulo.rya/target/accumulo.rya-3.2.11-incubating-SNAPSHOT.jar and
> the class name is not the one reported in the docs
>
> Is it the right command? The docs are a bit inconsistent with names.
>
> Cheers,
>
>
> Davide
>

Re: Rya UI/Console?

[David Lotts]

Also the openrdf-workbench.
It is pre-setup in the rya examples Vagrant VM.  That is what I use.
Here is the documentation for what I am talking about, but this is a new
version:
http://docs.rdf4j.org/server-workbench-console/

david.

On Wed, Jan 11, 2017 at 5:08 PM, John Smith  wrote:

> http://hostname:port/web.rya/sparqlQuery.jsp
>
> On Wed, Jan 11, 2017 at 2:02 PM, Ly, Kiet  wrote:
>
> > Does Rya has any UI to run SPARQL query?
>

Fwd: Should Rya have a Twitter account?

[David Lotts]

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

Re: rya parser failed on parsing large numeric type

[David Lotts]

> 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.

Re: select * where { s? p? o? } query

[David Lotts]

Way to go John!  That was fast turn around!
We just pulled your pull request so now it is in the Master branch of Rya.
I had some doubts about how it would handle graph-context, but on closer
inspection, that is handled outside of the strategy.

Anything else I can help you fix in Rya?  Feel free to look thru the Jira
issues.
david.

On Wed, Jan 4, 2017 at 6:16 PM, John Smith <johns0...@gmail.com> wrote:

> Thank you! I got it to work using your suggestion.  Here is a pull request
> with this capability (https://github.com/apache/incubator-rya/pull/136).
> I just had to added this NullRowTriplePatternStrategy to RyaTripleContext
> default triple pattern strategies, so that it is used :)
>
> On Wed, Jan 4, 2017 at 9:21 AM, David Lotts <dlo...@gmail.com> wrote:
>
> > The error is thrown here:
> > rya/dao/accumulo.rya/src/main/java/org/apache/rya/accumulo/
> > query/AccumuloRyaQueryEngine.java
> > line 142
> > 
> >strategy = ryaContext.retrieveStrategy(stmt);
> > if (strategy == null) {
> > throw new IllegalArgumentException("TriplePattern["
> +
> > stmt + "] not supported");
> > }
> > 
> > The strategy is TABLE_LAYOUT and the scan range.
> > The TABLE_LAYOUT  is which table it scans to match the statement pattern:
> > SPO, POS, or OSP, and
> > the scan range is a start and stop byte[] range for scanning that table.
> >
> > Try creating a new strategy and see where that takes you:
> >
> > 1. Copy class SpoWholeRowTriplePatternStrategy to
> > NullRowTriplePatternStrategy,
> >
> > /rya.api/src/main/java/org/apache/rya/api/query/strategy/wholerow/
> > SpoWholeRowTriplePatternStrategy.java
> > 2. fix the handle() method so that it returns true for all null
> parameters,
> > and
> > 3. replace the defineRange() with this:
> >
> > defineRange(RyaURI, RyaURI, RyaType, RyaURI,
> > RdfCloudTripleStoreConfiguration) {
> > start = new Byte[] { /* empty array */  };  // Scan from the
> > beginning of the Accumulo table.
> > stop = LAST_BYTES;// Scan to the end, up through things
> > beginning with 0xff.
> > return new RdfCloudTripleStoreUtils.
> CustomEntry<TABLE_LAYOUT,
> > ByteRange>(TABLE_LAYOUT.SPO, new ByteRange(start, stop));
> > }
> >
> > Then add a new instance of NullRowTriplePatternStrategy in method:
> > org.apache.rya.api.resolver.RyaTripleContext.
> > addDefaultTriplePatternStrategies(boolean)
> >
> > And your done!
> > There might be some oddness about creating a range with an empty start
> > array.  Might be better to skip the range when creating the scanner.
> > david.
> >
> > On Tue, Jan 3, 2017 at 4:01 PM, John Smith <johns0...@gmail.com> wrote:
> >
> > > *I was looking to make RYA more SPARQL1.1 compliant by enabling the
> > > capability to perform the following query*
> > >
> > > *SELECT * { s? p? o?  } *
> > >
> > >
> > >
> > >
> > >
> > > *I found that this capability is already supported, it is simply
> disabled
> > > ( RYA-83 <https://issues.apache.org/jira/browse/RYA-83> )Could someone
> > > point me to where in the code it is disabled?I would be interested in
> > > better understanding the reasons for disabling this capability.  All
> that
> > > is said in RYA-83 is that it would perform a full table scan.  I
> suppose
> > > that could be expensive.  But just because a query is expensive is that
> > > reason enough to prevent someone from issuing the query?  What if the
> > user
> > > is willing to pay the cost of running an expensive query?  What are
> your
> > > thoughts?*
> > >
> >
>

Re: select * where { s? p? o? } query

[David Lotts]

The error is thrown here:
rya/dao/accumulo.rya/src/main/java/org/apache/rya/accumulo/query/AccumuloRyaQueryEngine.java
line 142

   strategy = ryaContext.retrieveStrategy(stmt);
if (strategy == null) {
throw new IllegalArgumentException("TriplePattern[" +
stmt + "] not supported");
}

The strategy is TABLE_LAYOUT and the scan range.
The TABLE_LAYOUT  is which table it scans to match the statement pattern:
SPO, POS, or OSP, and
the scan range is a start and stop byte[] range for scanning that table.

Try creating a new strategy and see where that takes you:

1. Copy class SpoWholeRowTriplePatternStrategy to
NullRowTriplePatternStrategy,

/rya.api/src/main/java/org/apache/rya/api/query/strategy/wholerow/SpoWholeRowTriplePatternStrategy.java
2. fix the handle() method so that it returns true for all null parameters,
and
3. replace the defineRange() with this:

defineRange(RyaURI, RyaURI, RyaType, RyaURI,
RdfCloudTripleStoreConfiguration) {
start = new Byte[] { /* empty array */  };  // Scan from the
beginning of the Accumulo table.
stop = LAST_BYTES;// Scan to the end, up through things
beginning with 0xff.
return new RdfCloudTripleStoreUtils.CustomEntry(TABLE_LAYOUT.SPO, new ByteRange(start, stop));
}

Then add a new instance of NullRowTriplePatternStrategy in method:
org.apache.rya.api.resolver.RyaTripleContext.addDefaultTriplePatternStrategies(boolean)

And your done!
There might be some oddness about creating a range with an empty start
array.  Might be better to skip the range when creating the scanner.
david.

On Tue, Jan 3, 2017 at 4:01 PM, John Smith  wrote:

> *I was looking to make RYA more SPARQL1.1 compliant by enabling the
> capability to perform the following query*
>
> *SELECT * { s? p? o?  } *
>
>
>
>
>
> *I found that this capability is already supported, it is simply disabled
> ( RYA-83  )Could someone
> point me to where in the code it is disabled?I would be interested in
> better understanding the reasons for disabling this capability.  All that
> is said in RYA-83 is that it would perform a full table scan.  I suppose
> that could be expensive.  But just because a query is expensive is that
> reason enough to prevent someone from issuing the query?  What if the user
> is willing to pay the cost of running an expensive query?  What are your
> thoughts?*
>

November status?

[David Lotts]

Welcome Billie!

Everybody,
I did not notice a November status report reminder.  Have we switched to
quarterly reporting now?

Also, I think I am missing from the commiter list in the incubator status
page: http://incubator.apache.org/projects/rya.html

Should I add myself?  I think I have permission now.
david.

Re: checklist for release

[David Lotts]

Some additional detail:

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 [1] using the Aaron's public key: [2]  Then
> verify hashes of these files.
>
Here are the commands: [3]

a. Install GPG.
b. import Aaron's key from Apache [2]:
gpg --keyserver
https://dist.apache.org/repos/dist/dev/incubator/rya/KEYS --recv-key
F50EAE1A

c. Download the files at [1] and run this in that folder:
gpg --verify rya-project-3.2.10-incubating-source-release.zip.asc

If you see "*Good signature*" from the verify, that is good enough as long
as you feel strongly that you have Aaron's real public key.  To eliminate
the warning, either trust Aaron's key "ultimately" or let it find a trusted
path to a key that you trust ultimately.

[1] https://repository.apache.org/content/repositories/
orgapacherya-1002/org/apache/rya/rya-project/3.2.10-incubating/
[2] https://dist.apache.org/repos/dist/release/incubator/rya/KEYS
[3]  https://httpd.apache.org/dev/verification.html

>
> 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: [DISCUSS] Path forward for release

[David Lotts]

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: Rya presentation for Cray on Sept 29 at noon

[David Lotts]

I would not miss it!
david.

On Tue, Sep 27, 2016 at 9:51 AM, Andy Seaborne  wrote:

> What are the call-in coordinates?
>
> Andy
>
>
> On 26/09/16 14:36, Aaron D. Mihalik wrote:
>
>> Very cool Adina.  I will call in as well.
>>
>> On Fri, Sep 23, 2016 at 2:33 PM Puja Valiyil  wrote:
>>
>> I can call in too! Great job promoting Rya Adina!
>>>
>>> Sent from my iPhone
>>>
>>> On Sep 23, 2016, at 10:07 AM, Meier, Caleb 

>>> wrote:
>>>

 I can call in.

 -Original Message-
 From: Kim Ziehlke [mailto:kzieh...@modusoperandi.com]
 Sent: Thursday, September 22, 2016 3:14 PM
 To: dev@rya.incubator.apache.org
 Subject: RE: Rya presentation for Cray on Sept 29 at noon

 I will be available to participate.  Thanks!



 -Original Message-

 From: Adina Crainiceanu [mailto:ad...@usna.edu]

 Sent: Thursday, September 22, 2016 2:34 PM

 To: dev@rya.incubator.apache.org

 Subject: Rya presentation for Cray on Sept 29 at noon



 Hi all,



 A team from Cray asked whether we can give an informal presentation on

>>> Rya via Google Hangout/Level3/Skype. I offered to do the presentation
>>> next
>>> Thursday, Sept 29 at noon ET. It would be great of other people on this
>>> list would join. There will be about 10-20 participants on their side.
>>>

 Please let me know if you are available/interested.



 Thank you,

 Adina



 --

 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_=CwIGaQ=Nwf-pp4xtYRe0sCRVM8_LWH54joY
>>> F7EKmrYIdfxIq10=vuVdzYC2kksVZR5STiFwDpzJ7CrMHCgeo_
>>> 4WXTD0qo8=V5aBo71TPpLMQncvH8V2FoNN1vevdSboUWJ5wwREXbw=Gk
>>> A8WOoV3kFmyj3mIUj9TpH-Ih0v1_MvviqRJrq3Hxs=
>>>


>>>
>>

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

[David Lotts]

Here the method I used to find the licenses for dependencies, and below is
reprint of the results with better wrapping:

I used the license-maven-plugin[1]
It does not require changes to the pom.xml.  I just ran this command in the
root.

mvn license:aggregate-add-third-party

It generated a file for each module in the 'target/' folder[2].   The root
target folder contains the aggregated list.  I researched most of the ones
tagged as '(Unknown license)'.

We could possibly add something to the pom.xml to do an automatic file
generation in our build to update the files.  It's described in the plugin
docs[1] .

[1]  http://www.mojohaus.org/license-maven-plugin/usage.html
[2]  ./target/generated-sources/license/THIRD-PARTY.txt

This issue is a release blocker:

RYA-177 Review License on Rya Dependencies

I was able to create a 3rd party dependency license report for Rya from the
license maven plugin.

- Good: I can send the full list if you like.  Mostly ASL and clearly
permitted.

- Okay: A number of CDDL and CPL licenses -- permitted if no source code is
included.

- Needs Improvement: The following are not clearly permitted licenses:

(LGPL) (OGC copyright) Open GIS Interfaces
(org.geotools:gt-opengis:14.1 - no url defined)
(LGPL) API interfaces

(org.geotools:gt-api:14.3 - no url defined)
(LGPL) DataStore Support
(org.geotools:gt-data:14.1 - no url defined)
(LGPL) Feature Based Graphs and Networks
(org.geotools:gt-graph:14.3 - no url defined)
(LGPL) Feature transforming feature source wrapper
(org.geotools:gt-transform:14.1 - no url defined)
(LGPL) GML2 XML Support
(org.geotools.xsd:gt-xsd-gml2:14.3 - no url defined)
(LGPL) GML3 XML Support
(org.geotools.xsd:gt-xsd-gml3:14.3 - no url defined)
(LGPL) Grid Coverage module
(org.geotools:gt-coverage:14.3 - no url defined)
(LGPL) Image I/O-Extensions - Custom Streams
(org.geosolutions.imageio-ext:imageio-ext-streams:1.1.13
- no url defined)
(LGPL) Image I/O-Extensions - GeoCore
(org.geosolutions.imageio-ext:imageio-ext-geocore:1.1.13
- no url defined)
(LGPL) Image I/O-Extensions - utilities classes and methods
(org.geosolutions.imageio-ext:imageio-ext-utilities:1.1.13
- no url defined)
(LGPL) Improved TIFF Plugin
(org.geosolutions.imageio-ext:imageio-ext-tiff:1.1.13
- no url defined)
(LGPL) JCalendar (com.toedter:jcalendar:1.1.4
- http://www.toedter.com/en/jcalendar/)
(LGPL) JTS Topology Suite (com.vividsolutions:jts:1.13
- http://sourceforge.net/projects/jts-topo-suite)
(LGPL) Main module
(org.geotools:gt-main:14.1 - no url defined)
(LGPL) Metadata
(org.geotools:gt-metadata:14.1 - no url defined)
(LGPL) OGC CQL to Filter parser
(org.geotools:gt-cql:14.1 - no url defined)
(LGPL) Process
(org.geotools:gt-process:14.1 - no url defined)
(LGPL) Process Feature
(org.geotools:gt-process-feature:14.1 - no url defined)
(LGPL) Referencing services
(org.geotools:gt-referencing:14.3 - no url defined)
(LGPL) Remote Tea Runtime
(org.acplt:oncrpc:1.0.7 - http://remotetea.sourceforge.net/)
(LGPL) Render
(org.geotools:gt-render:14.1 - no url defined)
(LGPL) Shapefile module
(org.geotools:gt-shapefile:14.1 - no url defined)
(LGPL) Vector grids
(org.geotools:gt-grid:14.1 - no url defined)
(LGPL) XML Parsing
(org.geotools.xsd:gt-xsd-core:14.3 - no url defined)
(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)
(Unknown license) jai_codec (javax.media:jai_codec:1.1.3 - no url defined)
(Unknown license) jai_core (javax.media:jai_core:1.1.3 - no url defined)
(Unknown license) jai_imageio (javax.media:jai_imageio:1.1 - no url defined)
(Unknown license) jgridshift (jgridshift:jgridshift:1.0 - no url defined)
(MIT license for package cern.colt.* only) colt
(colt:colt:1.2.0 - no url defined)
-- this is a mistake, should be using:
-- java.util.Arrays, not  cern.colt.Arrays
-- creating an issue to eliminate dependency.

david.

On Thu, Sep 15, 2016 at 9:34 AM, Jim Hughes <jn...@ccri.com> wrote:

> Hi David,
>
> Ayup.  As I mentioned in another part of the thread, we had to exclude and
> work around category-X transitive dependencies.  Eclipse and Apache both
> agree on many of the no-go licenses and only-if you must ones.
>
> Since you mentioned JAI, I'd note that there is a project called Raster
> Processing Engine which is getting started to provide a better-licensed
> alternative.  There are a number of ways in which things are improving
> (both license-wise and in terms of technology).
>
> Cheers,
>
> Jim
>
>
> On 09/14/2016 03:35 PM, David Lotts wrote:
>
>> Jim, thanks for the clarity!  So that is settled, we can't just 

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

[David Lotts]

Oops, this thread was supposed to be subject RYA-177
RYA-179 is corrections to Rya source file license headers.

Jim, do you know when GeoMesa plans to be completely free of GeoTools ?
Clearly Geotools is an obstacle for Apache projects to use LocationTech
projects, or at least GeoMesa.
Or is there another path forward for GeoMesa?

On Wed, Sep 14, 2016 at 1:48 PM, Aaron D. Mihalik <aaron.miha...@gmail.com>
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://github.com/apache/flink/blob/release-1.1.2/
> flink-streaming-connectors/pom.xml#L69
> [2]
> https://github.com/apache/flink/blob/release-1.1.2/
> flink-streaming-connectors/flink-connector-kinesis/pom.xml#L73
>
> [3] https://github.com/apache/nifi/blob/master/pom.xml#L1316
>
> [4] https://github.com/apache/spark/blob/v2.0.0/mllib/pom.xml#L120
> [5]
> https://github.com/apache/spark/blob/v2.0.0/docs/ml-guide.md#dependencies
>
> [6] https://github.com/apache/spark/blob/v2.0.0/pom.xml#L2414
>
> [7] https://issues.apache.org/jira/browse/LEGAL-198
> [8] https://www.gnu.org/licenses/lgpl-java.html
>
>
>
> On Wed, Sep 14, 2016 at 12:09 PM David Lotts <dlo...@gmail.com> wrote:
>
> > Great find Aaron!
> > The ESRI library is quite comparable!
> >
> > Rya via Geomesa are using *JTS Topology Suite (*JTS): (the javadocs at
> > vividsolutions seems to be 404 )
> >
> >
> > http://tsusiatsoftware.net/jts/javadoc/com/vividsolutions/jts/geom/
> Geometry.html
> >
> > Far from a drop-in replacement, but a path forward:
> > http://esri.github.io/geometry-api-java/javadoc/
> >
> > Interesting, ESRI has Shape file support, but no GML, the opposite of
> JTS!
> > david.
> >
> >
> > On Wed, Sep 14, 2016 at 10:29 AM, Aaron D. Mihalik <
> > aaron.miha...@gmail.com>
> > wrote:
> >
> > > Yeah, that sounds possible. I don't like the idea of having to maintain
> > > another build/ci/release process, though.
> > >
> > > More importantly, we'd also have to modify our GeoIndexer interface [1]
> > to
> > > something Apache Friendly.  It looks like Ersi puts out an Apache 2.0
> > > library [2].
> > >
> > > [1]
> > > https://github.com/apache/incubator-rya/blob/master/
> > > extras/indexing/src/main/java/mvm/rya/indexing/GeoIndexer.java
> > > [2] https://github.com/Esri/geometry-api-java
> > >
> > > On Tue, Sep 13, 2016 at 10:36 PM Jim Hughes <jn...@ccri.com> wrote:
> > >
> > > > Hi Aaron,
> > > >
> > > > Thanks, wasn't finding that list quickly...
> > > >
> > > > It sounds like the GeoMesa/GeoTools usage might fall under this Q/A:
> > > > http://www.apache.org/legal/resolved.html#optional.
> > > >
> > > > Thoughts?
> > > >
> > > > Jim
> > > >
> > > > On 9/13/2016 9:25 PM, Aaron D. Mihalik wrote:
> > > > > Jim,
> > > > >
> > > > > We've been working off of these lists:
> > > > >
> > > > > http://www.apache.org/legal/resolved.html#category-a
> > > > >
> > > > > On Tue, Sep 13, 2016 at 6:07 PM Jim Hughes <jn...@ccri.com> wrote:
> > > > >
> > > > >> Hi David,
> > > > >>
> > > > >> A number of the geo-dependencies are likely from the geo-indexing
> > > (which
> > > > >> uses GeoMesa (Apache 2.0) which uses GeoTools and JTS).
> > > > >>
> > > > >> Are there options to make the geoindexing a profile, provide the
> > > source,
> >

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

[David Lotts]

I am seeing something happening might make this a non-issue in the medium
term.  Maybe someone can confirm this.  It looks like the LocationTech
community is adopting JTS and (here is my speculation) trying to shed
GeoTools and any dependence on LGPL.

"... induction of JTS
<https://www.locationtech.org/proposals/jts-topology-suite> into the
LocationTech community. The project tasks to address including a license
change from LGPL to BSD/EPL, ..."
found here:
http://boundlessgeo.com/2016/02/locationtech-incubation-sprint-update/

This is great, but Geotools is LGPL only, correct?   Third-party code
redistributed by Eclipse (EPL) explicitly excludes LGPL
<https://eclipse.org/legal/eplfaq.php#3RDPARTY>.
But then I see this:

http://boundlessgeo.com/press-release/boundless-ccri-launch-opengeo-suite-geomesa/

Perhaps this will all work out and we can just grab a later version of
GeoMesa with 100% Apache redistributability.  :-)

david.

On Wed, Sep 14, 2016 at 12:09 PM, David Lotts <dlo...@gmail.com> wrote:

> Great find Aaron!
> The ESRI library is quite comparable!
>
> Rya via Geomesa are using *JTS Topology Suite (*JTS): (the javadocs at
> vividsolutions seems to be 404 )
> http://tsusiatsoftware.net/jts/javadoc/com/vividsolutions/jts/geom/
> Geometry.html
>
> Far from a drop-in replacement, but a path forward:
> http://esri.github.io/geometry-api-java/javadoc/
>
> Interesting, ESRI has Shape file support, but no GML, the opposite of JTS!
> david.
>

On Wed, Sep 14, 2016 at 10:39 AM, Puja Valiyil <puja...@gmail.com> wrote:

> Could we revive the indexer profile again?  Make everything in indexing
> only included in that profile?  That could push off refactoring the
> geoindexing until our next release.
>
> On Wed, Sep 14, 2016 at 10:29 AM, Aaron D. Mihalik <
> aaron.miha...@gmail.com>
> wrote:
>
> > Yeah, that sounds possible. I don't like the idea of having to maintain
> > another build/ci/release process, though.
> >
> > More importantly, we'd also have to modify our GeoIndexer interface [1]
> to
> > something Apache Friendly.  It looks like Ersi puts out an Apache 2.0
> > library [2].
> >
> > [1]
> > https://github.com/apache/incubator-rya/blob/master/
> > extras/indexing/src/main/java/mvm/rya/indexing/GeoIndexer.java
> > [2] https://github.com/Esri/geometry-api-java
> >
> > On Tue, Sep 13, 2016 at 10:36 PM Jim Hughes <jn...@ccri.com> wrote:
> >
> > > Hi Aaron,
> > >
> > > Thanks, wasn't finding that list quickly...
> > >
> > > It sounds like the GeoMesa/GeoTools usage might fall under this Q/A:
> > > http://www.apache.org/legal/resolved.html#optional.
> > >
> > > Thoughts?
> > >
> > > Jim
> > >
> > > On 9/13/2016 9:25 PM, Aaron D. Mihalik wrote:
> > > > Jim,
> > > >
> > > > We've been working off of these lists:
> > > >
> > > > http://www.apache.org/legal/resolved.html#category-a
> > > >
> > > > On Tue, Sep 13, 2016 at 6:07 PM Jim Hughes <jn...@ccri.com> wrote:
> > > >
> > > >> Hi David,
> > > >>
> > > >> A number of the geo-dependencies are likely from the geo-indexing
> > (which
> > > >> uses GeoMesa (Apache 2.0) which uses GeoTools and JTS).
> > > >>
> > > >> Are there options to make the geoindexing a profile, provide the
> > source,
> > > >> and not provide artifacts for that code at Apache?
> > > >>
> > > >> Also, is there a list of approved licenses for Apache projects
> > > >> dependencies?
> > > >>
> > > >> Cheers,
> > > >>
> > > >> Jim
> > > >>
> > > >> On 09/13/2016 05:46 PM, David Lotts wrote:
> > > >>> This issue is a release blocker:
> > > >>> <https://issues.apache.org/jira/browse/RYA-179>
> > > >>>
> > > >>> RYA-179 <https://issues.apache.org/jira/browse/RYA-179> Review
> > > License /
> > > >>> Copyright notices on Rya Artifacts
> > > >>>
> > > >>> I was able to create a 3rd party dependency license report for Rya
> > > >>> from the license
> > > >>> maven plugin.
> > > >>> <http://www.mojohaus.org/license-maven-plugin/>
> > > >>>
> > > >>> Good: I can send the full list if you like.  Mostly ASL and clearly
> > > >>> permitted.
> > > >>>
> 

RYA-179 Review License / Copyright notices on Rya Artifacts

[David Lotts]

This issue is a release blocker:


RYA-179  Review License /
Copyright notices on Rya Artifacts

I was able to create a 3rd party dependency license report for Rya
from the license
maven plugin.


Good: I can send the full list if you like.  Mostly ASL and clearly
permitted.

Okay: A number of CDDL and CPL licenses -- permitted if no source code is
included.

Needs Improvement: The following are not clearly permitted licenses:

 (cern.colt MIT license see
https://dst.lbl.gov/ACSSoftware/colt/license.html) colt (colt:colt:1.2.0 -
no url defined)
 -- this is a mistake, should be  java.util.Arrays, not
cern.colt.Arrays  -- creating an issue to eliminate dependency.
 (GNU LESSER GENERAL PUBLIC LICENSE) JCalendar
(com.toedter:jcalendar:1.1.4 - http://www.toedter.com/en/jcalendar/)
 (Lesser General Public License (LGPL)) JTS Topology Suite
(com.vividsolutions:jts:1.13 -
http://sourceforge.net/projects/jts-topo-suite)
 (Lesser General Public License (LGPL)) Image I/O-Extensions - GeoCore
(it.geosolutions.imageio-ext:imageio-ext-geocore:1.1.13 - no url defined)
 (Lesser General Public License (LGPL)) Image I/O-Extensions - Custom
Streams (it.geosolutions.imageio-ext:imageio-ext-streams:1.1.13 - no url
defined)
 (Lesser General Public License (LGPL)) Improved TIFF Plugin
(it.geosolutions.imageio-ext:imageio-ext-tiff:1.1.13 - no url defined)
 (Lesser General Public License (LGPL)) Image I/O-Extensions -
utilities classes and methods
(it.geosolutions.imageio-ext:imageio-ext-utilities:1.1.13 - no url defined)
 (Unknown license) jai_codec (javax.media:jai_codec:1.1.3 - no url
defined)
 (Unknown license) jai_core (javax.media:jai_core:1.1.3 - no url
defined)
 (Unknown license) jai_imageio (javax.media:jai_imageio:1.1 - no url
defined)
 (Unknown license) jgridshift (jgridshift:jgridshift:1.0 - no url
defined)
 (GNU Lesser General Public License) Remote Tea Runtime
(org.acplt:oncrpc:1.0.7 - http://remotetea.sourceforge.net/)
 (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)
 (Lesser General Public License (LGPL)) API interfaces
(org.geotools:gt-api:14.3 - no url defined)
 (Lesser General Public License (LGPL)) Grid Coverage module
(org.geotools:gt-coverage:14.3 - no url defined)
 (Lesser General Public License (LGPL)) OGC CQL to Filter parser
(org.geotools:gt-cql:14.1 - no url defined)
 (Lesser General Public License (LGPL)) DataStore Support
(org.geotools:gt-data:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Feature Based Graphs and
Networks (org.geotools:gt-graph:14.3 - no url defined)
 (Lesser General Public License (LGPL)) Vector grids
(org.geotools:gt-grid:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Main module
(org.geotools:gt-main:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Metadata
(org.geotools:gt-metadata:14.1 - no url defined)
 (Lesser General Public License (LGPL)) (OGC copyright) Open GIS
Interfaces (org.geotools:gt-opengis:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Process
(org.geotools:gt-process:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Process Feature
(org.geotools:gt-process-feature:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Referencing services
(org.geotools:gt-referencing:14.3 - no url defined)
 (Lesser General Public License (LGPL)) Render
(org.geotools:gt-render:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Shapefile module
(org.geotools:gt-shapefile:14.1 - no url defined)
 (Lesser General Public License (LGPL)) Feature transforming feature
source wrapper (org.geotools:gt-transform:14.1 - no url defined)
 (Lesser General Public License (LGPL)) XML Parsing
(org.geotools.xsd:gt-xsd-core:14.3 - no url defined)
 (Lesser General Public License (LGPL)) GML2 XML Support
(org.geotools.xsd:gt-xsd-gml2:14.3 - no url defined)
 (Lesser General Public License (LGPL)) GML3 XML Support
(org.geotools.xsd:gt-xsd-gml3:14.3 - no url defined)

david.

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

[David Lotts]

Good news: I was able to create a 3rd party dependency license report for
Rya from the license maven plugin.

Bad news:  I'm going to send results in another thread in a few minutes.

david.

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

[David Lotts]

Good find.
I was just trying to get  this similar maven pluggin to work.  It's verbose
AND incomprehensible about errors, but no report.

http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html

Oh, now it's hung!
My command line:
mvn project-info-reports:dependencies
-Dproject.reporting.outputDirectory=/tmp/mvnreports

david.

On Tue, Sep 13, 2016 at 12:54 PM, Chilton, Kevin 
wrote:

>  http://www.mojohaus.org/license-maven-plugin/
> 
>
>

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

[David Lotts]

Okay, I'll lend my eye's to rya-177.  Since that is the blocker.
david.

On Tue, Sep 13, 2016 at 11:18 AM, Aaron D. Mihalik <aaron.miha...@gmail.com>
wrote:

> I'm fine pulling RYA-183 into the next RC, but my biggest concern is
> "(Blocker) RYA-177 - Review License on Rya Dependencies".  I'm up for
> taking a stab at it, but we might need a couple eyes on it.
>
> --Aaron
>
> On Tue, Sep 13, 2016 at 11:15 AM David Lotts <dlo...@gmail.com> wrote:
>
> > In support of preventing future hidden broken examples, I just created
> this
> > issue.  If you want to include it in this release, let me know and I'll
> do
> > it immediately.
> > RYA-183 <https://issues.apache.org/jira/browse/RYA-183> Run the
> > example
> > apps when automated tests are run
> > david.
> >
> > On Tue, Sep 13, 2016 at 10:33 AM, 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
> > >
> > > -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.
> > >
> > >
> >
>

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

[David Lotts]

In support of preventing future hidden broken examples, I just created this
issue.  If you want to include it in this release, let me know and I'll do
it immediately.
RYA-183 <https://issues.apache.org/jira/browse/RYA-183> Run the example
apps when automated tests are run
david.

On Tue, Sep 13, 2016 at 10:33 AM, 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
>
> -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.
>
>

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

[David Lotts]

-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://dist.apache.org/repos/dist/release/incubator/rya and
> > https://dist.apache.org/repos/dist/dev/incubator/rya 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://github.com/floscher/jGridShift/blob/master/LICENSE). 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 (http://dst.lbl.gov/ACSSoftware/colt/) 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: http://www.apache.org/legal/resolved.html#category-x. See
> > http://www.apache.org/licenses/GPL-compatibility.html 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 wrong (2015 instead of 2016)
> > * mvn apache-rat:check passes (after `rm DEPENDENCIES`)
> > * A number of files which have 'Copyright (C) 2014 Rya' in the license
> > header in extras/rya.merger that should not exist. Copyright statement
> > should only appear in the NOTICE file (`fgrep -Ri 'copyright'
> > rya-project-3.2.10 | fgrep -v 'The ASF licenses this file'`)
> > * v3.2.10-RC1 is incorrect in parent pom
> > * I see a bunch of maven-shade-plugin uses and at least one warfile
> > project: keep in mind that you should be ensuring that the generated
> > artifacts by your official source-release should also be licensed per
> > ASF policy. This isn't something you have to fix for this first release,
> > but it would bar Rya from a +1 to graduate from me.
> > * Saw some XML files in the build which were excluded from the
> > apache-rat-plugin. I'd recommend minimizing the exclusions as much as
> > possible.
> >
> > - Josh
> >
> > 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://repository.apache.org/content/repositories/
> orgapacherya-1001/org/apache/rya/rya-project/3.2.10/
> > >
> > > The Git tag is v3.2.10
> > > The Git commit ID is 16196b4c658062545964602835cb5fbd2870e578
> > >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=
> 16196b4c658062545964602835cb5fbd2870e578
> > >
> > > Checksums of rya-project-3.2.10-source-release.zip:
> > > SHA1: dee4a5e4f8e74c4de614d02c7b17a5e0db132649
> > > MD5: df4a47ae1232725bc95450f5e49de95c
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/mihalik.asc
> > >
> > > Issues that were closed/resolved for this release are here:
> > >
> > 

Re: [jira] [Commented] (RYA-134) stack overflow when using owl:TransitiveProperty

[David Lotts]

Kiet Ly,
For your stack overflow, can you share your model with me?  Dropbox, or zip
it and send to my gmail?
If not, maybe you could characterize it so I can recreate the issue.
david.

On Mon, Aug 1, 2016 at 2:34 PM, David W. Lotts (JIRA) 
wrote:

>
> [
> https://issues.apache.org/jira/browse/RYA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402590#comment-15402590
> ]
>
> David W. Lotts commented on RYA-134:
> 
>
> So are you thinking that a conversion from recursion to a loop would allow
> it to scale up better?
> It appears that it stores all it's chained inferred statements in memory,
> so I suppose that would be the upper limit.  But in your case it fails on a
> stack overflow.  Would you say it should eventually run out of RAM instead
> of stack overflow?
>
> > stack overflow when using owl:TransitiveProperty
> > 
> >
> > Key: RYA-134
> > URL: https://issues.apache.org/jira/browse/RYA-134
> > Project: Rya
> >  Issue Type: Bug
> > Environment: Accumulo 1.6.5 + Rya build from dev branch.
> >Reporter: Kiet Ly
> >Priority: Critical
> >
> > matter:involved rdf:type owl:TransitiveProperty .
> > Look like Rya is using recursion?
> > 28-Jul-2016 16:56:36.688 SEVERE [http-nio-8000-exec-5]
> org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for
> servlet [springrdf] in context with path [/web.rya] threw exception
> [Handler processing failed; nested exception is
> java.lang.StackOverflowError] with root cause
> >  java.lang.StackOverflowError
> > at
> sun.nio.ch.EPollArrayWrapper.setInterest(EPollArrayWrapper.java:213)
> > at
> sun.nio.ch.EPollSelectorImpl.putEventOps(EPollSelectorImpl.java:187)
> > at
> sun.nio.ch.SocketChannelImpl.translateAndSetInterestOps(SocketChannelImpl.java:980)
> > at
> sun.nio.ch.SelectionKeyImpl.nioInterestOps(SelectionKeyImpl.java:105)
> > at
> sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:83)
> > at sun.nio.ch.SelectorImpl.register(SelectorImpl.java:135)
> > at
> java.nio.channels.spi.AbstractSelectableChannel.register(AbstractSelectableChannel.java:209)
> > at
> java.nio.channels.SelectableChannel.register(SelectableChannel.java:277)
> > at
> org.apache.hadoop.net.SocketIOWithTimeout$SelectorPool.select(SocketIOWithTimeout.java:334)
> > at
> org.apache.hadoop.net.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:157)
> > at
> org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:161)
> > at
> org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:131)
> > at java.io.FilterInputStream.read(FilterInputStream.java:133)
> > at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> > at
> java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> > at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> > at
> org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:127)
> > at
> org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
> > at
> org.apache.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:129)
> > at
> org.apache.thrift.transport.TFramedTransport.read(TFramedTransport.java:101)
> > at
> org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
> > at
> org.apache.accumulo.core.client.impl.ThriftTransportPool$CachedTTransport.readAll(ThriftTransportPool.java:273)
> > at
> org.apache.thrift.protocol.TCompactProtocol.readByte(TCompactProtocol.java:601)
> > at
> org.apache.thrift.protocol.TCompactProtocol.readMessageBegin(TCompactProtocol.java:470)
> > at
> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:69)
> > at
> org.apache.accumulo.core.tabletserver.thrift.TabletClientService$Client.recv_startScan(TabletClientService.java:228)
> > at
> org.apache.accumulo.core.tabletserver.thrift.TabletClientService$Client.startScan(TabletClientService.java:204)
> > at
> org.apache.accumulo.core.client.impl.ThriftScanner.scan(ThriftScanner.java:403)
> > at
> org.apache.accumulo.core.client.impl.ThriftScanner.scan(ThriftScanner.java:279)
> > at
> org.apache.accumulo.core.client.impl.ScannerIterator$Reader.run(ScannerIterator.java:84)
> > at
> org.apache.accumulo.core.client.impl.ScannerIterator.hasNext(ScannerIterator.java:177)
> > at
> com.google.common.collect.TransformedIterator.hasNext(TransformedIterator.java:43)
> > at
> mvm.rya.api.utils.CloseableIterableIteration.hasNext(CloseableIterableIteration.java:60)
> > at
> mvm.rya.api.persist.utils.RyaDAOHelper$1.hasNext(RyaDAOHelper.java:80)
> > at
> 

Re: Rya-54 vagrant cleanup #47

[David Lotts]

Adina,
> However, after restarting the VM,  and starting zookeeper and accumulo in
the VM,

Can you try "ryaps" from the VM command line?
Output should look like this:
```
org.apache.zookeeper.server.quorum.QuorumPeerMain
org.apache.accumulo.start.Main monitor
org.apache.accumulo.start.Main tserver
org.apache.accumulo.start.Main master
org.apache.accumulo.start.Main gc
org.apache.accumulo.start.Main tracer
org.apache.catalina.startup.Bootstrap
```

> I'm not receiving any responses to queries using the OpenWorkbench or
> Rya web - the query is submitted, but the request from the browser just
never returns. Not sure what is going on there.

Sounds like Accumulo is down.
Unfortunately, I seen some issues with restarting the VM.  I hoped your
suggestion to move the Zookeeper data directory would fix that, but it
still fails to start sometimes.  It may have to do with my machine going to
into hibernation.

The work around is to "vagrant provision" from the host -- which does not
re-download nor delete data.

If that does not work, then:
>From within the VM, run:
sudo rm -r /data
sudo rm -r /var/zookeeper/
Then from the host:
vagrant provision

This is in the vagrant-example readme.md.

david.

On Thu, Jun 16, 2016 at 10:01 PM, Adina Crainiceanu  wrote:

> Hi David,
>
> I tried the new vagrant script from home and it worked without problems.
> However, after restarting the VM,  and starting zookeeper and accumulo in
> the VM, I'm not receiving any responses to queries using the OpenWorkbench
> or Rya web - the query is submitted, but the request from the browser just
> never returns. Not sure what is going on there.
>
> The problem Amila has with the vagrant seems to be the same one I have
> from school - we cannot download Rya from dropbox - some settings at out
> universities likely prevent that.
>
> Adina
>
>

Re: Rya-54 vagrant cleanup #47

[David Lotts]

Your output[1] appears to be a perfectly successful install!
Congratulations!

Did you go through the vagrant-example readme.md?  There are several
verification steps using the browser.

>  … in the vm i got the terminal only.

>  Is this because a problem in Vagrant up?

This VM has only a web user interface, and ssh text terminal interface.

>From your local terminal do a "vagrant ssh" and it will use keys instead of
passwords to login.


david.

On Fri, Jun 17, 2016 at 9:19 AM, Amila Wijayarathna <
amwijayarat...@gmail.com> wrote:

> Hi Adina,David,
> So I "up" again the vagrant file and got this [1]. I think it went
> successfully. But in the vm i got the terminal only.
> Is this because a problem in Vagrant up?
> any idea about this is appreciated.
>
> [1]
> https://gist.github.com/AmilaWijayarathna/2b84e6aae91799f2f03402d2dc304d16
>
>
>
> On Fri, Jun 17, 2016 at 7:31 AM, Adina Crainiceanu <ad...@usna.edu> wrote:
>
>> Hi David,
>>
>> I tried the new vagrant script from home and it worked without problems.
>> However, after restarting the VM,  and starting zookeeper and accumulo in
>> the VM, I'm not receiving any responses to queries using the OpenWorkbench
>> or Rya web - the query is submitted, but the request from the browser just
>> never returns. Not sure what is going on there.
>>
>> The problem Amila has with the vagrant seems to be the same one I have
>> from school - we cannot download Rya from dropbox - some settings at out
>> universities likely prevent that.
>>
>> Adina
>>
>> On Thu, Jun 16, 2016 at 8:46 AM, Amila Wijayarathna <
>> amwijayarat...@gmail.com> wrote:
>>
>>> Hi David,
>>> Again I "up" the vagrantfile in non proxy internet connection and I got
>>> this [1]. And when I tried again it stops by the Hadoop installation. I
>>> think this because of my internet connetion. I will try again and give you
>>> some updates.
>>>
>>> [1]
>>> https://gist.github.com/AmilaWijayarathna/9d295b4a6f911f9ed9ac6f1c1a5dface
>>>
>>> Thank you!
>>>
>>> On Wed, Jun 15, 2016 at 4:00 AM, David Lotts <dlo...@gmail.com> wrote:
>>>
>>>> From your output [1], I suspect that it is this line in the vagrant
>>>> file that is failing:
>>>>
>>>>  sudo -E add-apt-repository ppa:webupd8team/java
>>>>
>>>> And it generates this error from your output:
>>>>
>>>> ==> default: Error reading
>>>> https://launchpad.net/api/1.0/~webupd8team/+archive/java: Service
>>>> Temporarily Unavailable
>>>>
>>>> Perhaps the site was down?  The URL works for me now.  Try the command
>>>> above ( add-apt-repository ) from the prompt in your VM.
>>>>
>>>> It may also be a proxy issue, described here :
>>>> https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/516032
>>>>
>>>> export https_proxy=http://www.example.com:8000/
>>>>
>>>> then do the command ( add-apt-repository ) above.
>>>>
>>>> If you you think you have it, or just want to try again, do this
>>>> command from the host.  It will skip the vm creation. If it aborts again at
>>>> the same place, you may need to delete the line that you did yourself (
>>>> add-apt-repository ).
>>>>
>>>> vagrant provision
>>>>
>>>> david.
>>>>
>>>> On Tue, Jun 14, 2016 at 5:38 PM, Amila Wijayarathna <
>>>> amwijayarat...@gmail.com> wrote:
>>>>
>>>>> Hi David,
>>>>>
>>>>> I got these windows as well,
>>>>>
>>>>> Thank you!
>>>>>
>>>>>
>>>>> On Wed, Jun 15, 2016 at 12:41 AM, Amila Wijayarathna <
>>>>> amwijayarat...@gmail.com> wrote:
>>>>>
>>>>>> Hi David,
>>>>>>
>>>>>> Thank you for your prompt response.
>>>>>> So I "up" the vagrant again in a non proxy internet connection and
>>>>>> end up with this [1]. It has less errors than the earlier one. and when I
>>>>>> do "vagrant ssh" i got the following,
>>>>>>
>>>>>> amila@amila-X550LD:~/Installs/ryaVagrant$   vagrant ssh
>>>>>> Welcome to Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-87-generic x86_64)
>>>>>>
>>>>>>  * Documentation:  https

Re: Rya-54 vagrant cleanup #47

[David Lotts]

>From your output [1], I suspect that it is this line in the vagrant file
that is failing:

 sudo -E add-apt-repository ppa:webupd8team/java

And it generates this error from your output:

==> default: Error reading
https://launchpad.net/api/1.0/~webupd8team/+archive/java: Service
Temporarily Unavailable

Perhaps the site was down?  The URL works for me now.  Try the command
above ( add-apt-repository ) from the prompt in your VM.

It may also be a proxy issue, described here :
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/516032

export https_proxy=http://www.example.com:8000/

then do the command ( add-apt-repository ) above.

If you you think you have it, or just want to try again, do this command
from the host.  It will skip the vm creation. If it aborts again at the
same place, you may need to delete the line that you did yourself (
add-apt-repository ).

vagrant provision

david.

On Tue, Jun 14, 2016 at 5:38 PM, Amila Wijayarathna <
amwijayarat...@gmail.com> wrote:

> Hi David,
>
> I got these windows as well,
>
> Thank you!
>
>
> On Wed, Jun 15, 2016 at 12:41 AM, Amila Wijayarathna <
> amwijayarat...@gmail.com> wrote:
>
>> Hi David,
>>
>> Thank you for your prompt response.
>> So I "up" the vagrant again in a non proxy internet connection and end up
>> with this [1]. It has less errors than the earlier one. and when I do
>> "vagrant ssh" i got the following,
>>
>> amila@amila-X550LD:~/Installs/ryaVagrant$   vagrant ssh
>> Welcome to Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-87-generic x86_64)
>>
>>  * Documentation:  https://help.ubuntu.com/
>>
>>   System information as of Tue Jun 14 17:03:04 UTC 2016
>>
>>   System load:  0.96  Processes:   110
>>   Usage of /:   3.5% of 39.34GB   Users logged in: 0
>>   Memory usage: 3%IP address for eth0: 10.0.2.15
>>   Swap usage:   0%
>>
>>   Graph this data and manage this system at:
>> https://landscape.canonical.com/
>>
>>   Get cloud support with Ubuntu Advantage Cloud Guest:
>> http://www.ubuntu.com/business/services/cloud
>>
>> 0 packages can be updated.
>> 0 updates are security updates.
>>
>>
>> vagrant@rya-example-box:~$
>>
>> And after that I can run those two commands (ping google.com and wget
>> http://google.com/) without any error.
>> Is it ok? if it is I like to know how to proceed further.
>>
>> Thank you!
>>
>>
>> [1]
>> https://gist.github.com/AmilaWijayarathna/8a2a20e6a4a1b9b5449bad83f459762b
>>
>> On Tue, Jun 14, 2016 at 11:10 PM, David Lotts <dlo...@gmail.com> wrote:
>>
>>> Wow, well documented attempt!  Thanks for the listings.
>>>
>>> So you brought "up" a default vagrant VM.
>>> All the messages from [3] are as I would expect, that is great.
>>>
>>> Then your copied the Rya Vagrantfile, and did a vagrant up, creating the
>>> output in [5].
>>> It downloaded the vm image from cloudera successfully, so we know your
>>> internet connection on the host is fine.
>>> But then when the guest VM attempts to update it's libraries, we start
>>> seeing all errors, starting with this one:
>>>
>>> ==> default: Failed to fetch
>>> http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease
>>>
>>> So I think something is wrong with your network inside the VM.
>>> Run the command
>>> vagrant ssh
>>> from it's install directory, then see if you can run these without error:
>>> ping google.com
>>> and/or
>>> wget http://google.com/
>>> => Resolving google.com (google.com)... Connecting to google.com
>>> (google.com)
>>>
>>> I can't tell if your first VM [3] was able to connect, you might ssh to
>>> it, and then ping and wget to see if it also has network problems.
>>>
>>> If you start the Virtualbox app, you can modify the network setting for
>>> the box and see if you can get it working.  Maybe you can set a proxy as
>>> you mentioned.
>>>
>>> david.
>>>
>>>
>>> On Tue, Jun 14, 2016 at 12:36 PM, Amila Wijayarathna <
>>> amwijayarat...@gmail.com> wrote:
>>>
>>>> Hi david,
>>>> This is my first time, setting up a vagrant file.
>>>> I downloaded the vagrant from [1] and downloaded a virtual box from
>>>> [2].  As this is my first time i didn't know how to do it correctly. So i
>>>> installed the the vagrant and up it other 

Re: Rya-54 vagrant cleanup #47

[David Lotts]

Wow, well documented attempt!  Thanks for the listings.

So you brought "up" a default vagrant VM.
All the messages from [3] are as I would expect, that is great.

Then your copied the Rya Vagrantfile, and did a vagrant up, creating the
output in [5].
It downloaded the vm image from cloudera successfully, so we know your
internet connection on the host is fine.
But then when the guest VM attempts to update it's libraries, we start
seeing all errors, starting with this one:

==> default: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/trusty/InRelease

So I think something is wrong with your network inside the VM.
Run the command
vagrant ssh
from it's install directory, then see if you can run these without error:
ping google.com
and/or
wget http://google.com/
=> Resolving google.com (google.com)... Connecting to google.com (
google.com)

I can't tell if your first VM [3] was able to connect, you might ssh to it,
and then ping and wget to see if it also has network problems.

If you start the Virtualbox app, you can modify the network setting for the
box and see if you can get it working.  Maybe you can set a proxy as you
mentioned.

david.


On Tue, Jun 14, 2016 at 12:36 PM, Amila Wijayarathna <
amwijayarat...@gmail.com> wrote:

> Hi david,
> This is my first time, setting up a vagrant file.
> I downloaded the vagrant from [1] and downloaded a virtual box from [2].
> As this is my first time i didn't know how to do it correctly. So i
> installed the the vagrant and up it other location that there  was no any
> Rya vagrant file. so i got this [3]. seems it set up successfully.
>
> After that I copied the vagrant file from [4] and made a Vagrantfile in a
> local location. when i do vagrant up in that location i got this [5]. it
> says something went wrong.
> I don't know this because is my Internet connection, because it has some
> proxy settings. I will look about it. Any idea about this is appreciated.
>
> Thank you!
>
>
> [1]  https://www.vagrantup.com/ <https://www.vagrantup.com/>
> [2] https://www.virtualbox.org/wiki/Linux_Downloads
> [3]
> https://gist.github.com/AmilaWijayarathna/52aa5da9a9c6e952967b1db1b01a1701
> [4]
> https://github.com/DLotts/incubator-rya/blob/RYA-54_vagrant-cleanup-squ/extras/vagrantExample/src/main/vagrant/Vagrantfile
> [5]
> https://gist.github.com/AmilaWijayarathna/9dd9ce075d98524dad9a97eb1d521e99
>
> On Mon, Jun 13, 2016 at 11:22 PM, Adina Crainiceanu <ad...@usna.edu>
> wrote:
>
>> David, I'm travelling until Thursday. I'll try it then if Amila does not
>> do
>> it earlier.
>>
>> Thanks,
>> Adina
>>
>> On Mon, Jun 13, 2016 at 11:47 AM, David Lotts <dlo...@gmail.com> wrote:
>>
>> > Adina, Amila, and everyone:
>> >
>> > Adina: Thanks for the great feedback!
>> > I think I have resolved everything that you mention, and a few others.
>> > Are you able to run it again?
>> > I updated the readme.md also.
>> >
>> > It's in my Rya github branch "RYA-54_vagrant-cleanup-squ" :
>> >
>> >
>> >
>> https://github.com/DLotts/incubator-rya/blob/RYA-54_vagrant-cleanup-squ/extras/vagrantExample/src/main/vagrant
>> >
>> > Start-over instructions below.
>> >
>> > The pull request is here:
>> https://github.com/apache/incubator-rya/pull/47
>> > david.
>> >
>> >
>> > On Tue, May 17, 2016 at 10:54 AM, David Lotts <dlo...@gmail.com> wrote:
>> > Amila,
>> > I have re-worked the Vagrant Example.  There were some race conditions
>> and
>> > places where errors become lost or skipped over.
>> > [...old link removed...]
>> >
>> > It uses the same instructions.
>> > You can do the command:
>> >
>> > vagrant destroy
>> >
>> > To remove your last attempt.  Then use the new file and the same readme
>> to
>> > start over.
>> >
>> > The new version is made to be re-run and possible fix errors from the
>> last
>> > attempt -- so you could just copy this over your old version and type:
>> >
>> > vagrant provision
>> >
>> > Then follow the readme instructions.
>> > I am interested in your experience with this.
>> >
>>
>>
>>
>> --
>> 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/
>>
>
>
>
> --
>
> *Amila Wijayarathna*
> Undergraduate,
> Faculty of Information Technology,
> University of Moratuwa,
> Sri Lanka.
>

Rya-54 vagrant cleanup #47

[David Lotts]

Adina, Amila, and everyone:

Adina: Thanks for the great feedback!
I think I have resolved everything that you mention, and a few others.
Are you able to run it again?
I updated the readme.md also.

It's in my Rya github branch "RYA-54_vagrant-cleanup-squ" :

https://github.com/DLotts/incubator-rya/blob/RYA-54_vagrant-cleanup-squ/extras/vagrantExample/src/main/vagrant

Start-over instructions below.

The pull request is here:  https://github.com/apache/incubator-rya/pull/47
david.


On Tue, May 17, 2016 at 10:54 AM, David Lotts <dlo...@gmail.com> wrote:
Amila,
I have re-worked the Vagrant Example.  There were some race conditions and
places where errors become lost or skipped over.
[...old link removed...]

It uses the same instructions.
You can do the command:

vagrant destroy

To remove your last attempt.  Then use the new file and the same readme to
start over.

The new version is made to be re-run and possible fix errors from the last
attempt -- so you could just copy this over your old version and type:

vagrant provision

Then follow the readme instructions.
I am interested in your experience with this.

Re: using prefix in rest call

[David Lotts]

Make sure you are pulling from the *development*  branch!  --  Master is in
a bad state until our upcoming first release.
david.

On Fri, Jun 10, 2016 at 12:40 PM, David Lotts <dlo...@gmail.com> wrote:

> What error/response are you getting?
>
> I did this, should be equivalent to your query:
>
>
> http://192.168.33.10:8080/web.rya/queryrdf?query.infer===xml==PREFIX+d%3A+%3Chttp%3A%2F%2Flearningsparql.com%2Fns%2Fdata%23%3E%0D%0Aselect+*+where+{+d%3A0432+%3Fpredicate+%3Fobject+.+}
> <http://192.168.33.10:8080/web.rya/queryrdf?query.infer===xml==PREFIX+d%3A+%3Chttp%3A%2F%2Flearningsparql.com%2Fns%2Fdata%23%3E%0D%0Aselect+*+where+%7B+d%3A0432+%3Fpredicate+%3Fobject+.+%7D>
>
> Works fine for me.
>
> Here is what I get, nothing was matched as I expected:
>
>  xmlns='http://www.w3.org/2005/sparql-results#'>name='predicate'/>
>
>
>
> david.
>
> On Fri, Jun 10, 2016 at 10:42 AM, Puja Valiyil <puja...@gmail.com> wrote:
>
>> I didn't know of this limitation -- I have successfully used this in the
>> past.  How are you issuing the query -- through the jsp site that comes
>> with rya or through a browser call or programmatically?
>>
>> On Fri, Jun 10, 2016 at 9:42 AM, Ly, Kiet <kiet...@finra.org> wrote:
>>
>> > http://10.162.96.77:8000/web.rya/queryrdf?query=PREFIX d: <
>> > http://learningsparql.com/ns/data#>\n select * where { d:0432
>> ?predicate
>> > ?object . }
>> >
>> > It seems I can’t use prefix in REST call. Is this the limitation? It
>> works
>> > in blazegraph.
>> >
>> >
>> > 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: GSoC - community bonding period

[David Lotts]

Amila,
I have re-worked the Vagrant Example.  There were some race conditions and
places where errors become lost or skipped over.
I am going to do a pull request on this soon, but would be good if you
could try this version from my Rya github branch:

https://github.com/DLotts/incubator-rya/blob/RYA-54_vagrant-cleanup/extras/vagrantExample/src/main/vagrant/Vagrantfile

It uses the same instructions.
You can do the command:

vagrant destroy

To remove your last attempt.  Then use the new file and the same readme to
start over.

The new version is made to be re-run and possible fix errors from the last
attempt -- so you could just copy this over your old version and type:

vagrant provision

Then follow the readme instructions.
I am interested in your experience with this.
david lotts.

On Sat, May 14, 2016 at 7:53 AM, Amila Wijayarathna <
amwijayarat...@gmail.com> wrote:

> Hi Adina,
> I went through the vagrant file. And there is a line,
>
>
> *# soft linking the files doesn't seem to work in tomcat, so we copy them
> instead :(*
>
> *sudo cp
> rya.indexing.example-${RYA_EXAMPLE_VERSION}-distribution/dist/lib/*
> /var/lib/tomcat7/webapps/openrdf-workbench/WEB-INF/lib/*
>
> *sudo cp
> rya.indexing.example-${RYA_EXAMPLE_VERSION}-distribution/dist/lib/*
> /var/lib/tomcat7/webapps/openrdf-sesame/WEB-INF/lib/*
>
> But I was unable to do so because I cannot find */dist/lib/* .*
> Any guidelines about this is thoroughly appreciated.
>
> Thank you!
>
> On Mon, May 9, 2016 at 7:45 PM, Amila Wijayarathna <
> amwijayarat...@gmail.com
> > wrote:
>
> > Hi Adina,
> >
> > The files you mentioned are not existing in the directory.
> > I will go through your guidelines and vagrant file.
> >
> > Thank you!
> >
> > On Mon, May 9, 2016 at 7:29 PM, Adina Crainiceanu <ad...@usna.edu>
> wrote:
> >
> >> Based on your error and the vagrant readme file, I think the OpenRDF
> >> Workbench transformations are not installed.
> >>
> >> Try this - adapted for your computer instead of the vagrant VM:
> >> "OpenRDF Workbench requires a set of "transformations" for listing Rya
> in
> >> the OpenRDF Workbench Repository list. The transforms are in this
> >> directory: /var/lib/tomcat7/webapps/openrdf-workbench/transformations/
> >>
> >>1. Verify that this file exists: create-RyaAccumuloSail.xsl
> >>2. Verify that create.xsl has been updated for rya. (run: "cat
> >>create.xsl | grep Rya" and make sure there's some stuff there.)
> >>
> >> If these files do note exists, open the vagrant file and look for the
> >> line echo "Downloading Rya". Try working through those commands manually
> >> on your Vagrant VM."
> >>
> >> In particular, the lines for "# Download and install new templates for
> >> OpenRdf WorkBench" in the vagrant file might be the ones that you are
> >> missing.
> >>
> >> Please make detailed notes of what you are doing, so we can reproduce
> the
> >> process on a new machine - I'm tryiong to get an Amazon EC2 instance
> so  we
> >> can all have access to it.
> >>
> >>
> >> Adina
> >>
> >>
> >>
> >>
> >> On Mon, May 9, 2016 at 9:09 AM, Amila Wijayarathna <
> >> amwijayarat...@gmail.com> wrote:
> >>
> >>> Hi Adina,
> >>> As in the vagrant file i tried to connect Rya via  OpenRDF workbench to
> >>> insert data. When i create new repository in workbench  i have chose
> the
> >>> type. But there is no "Rya Accumulo Store"  type to chose as in the
> >>> vagrant file.
> >>> Any idea about this is thoroughly appriciated.
> >>>
> >>> Thank you!
> >>>
> >>> On Sat, May 7, 2016 at 9:36 PM, Adina Crainiceanu <ad...@usna.edu>
> >>> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> The screen shot for the web.rya/sparqlQuery.jsp looks correct. You
> >>>> should try to insert some data and see if you can query it back. You
> might
> >>>> be able to do an insert and select through the web.rya interface, but
> I'm
> >>>> not sure about the insert.
> >>>>
> >>>>
> >>>> The easiest way to do insert is through the openRDF Workbench
> interface.
> >>>> Look in the vagrant file to see how to set it up.
> >>>> Look in the Readme file for the vagrant example to see how to load
> some
> >>&g

Re: Rya Working Group: Temporal Indexing -- May 18, Noon Eastern

[David Lotts]

Adina,

*> Google Summer of Code project for Amila*Sure!  That would awesome!

We want to make sure that Amila can be heard and understood.  Last time it
was difficult to hear him clearly.
Would he be able to dial in to the same conference number below and do a
practice call today?  (Let us know what time)  Would there be a better
conference technology that he can use?

We can do the temporal indexing after the Fluo talk.  (There's plenty of
time for temporal :))  Also, if we can't get audio working at the last
minute, then we can have Temporal Indexing as a backup plan.

david lotts.

On Mon, May 16, 2016 at 1:56 PM, Adina Crainiceanu <ad...@usna.edu> wrote:

> For this meeting, could we change the agenda/add to it to talk about the
> Google Summer of Code project for Amila? As the coding period starts soon,
> this would be a good opportunity to get feedback/info from the others about
> the continuous integration and performance testing that he plans to do.
>
> Thank you,
> Adina
>
> On Mon, May 16, 2016 at 1:41 PM, David Lotts <dlo...@gmail.com> wrote:
>
> > All,
> >
> > The Rya working group is this Wednesday at noon.  This week we will be
> > going over:
> >
> >- Temporal indexing and queries,
> >- a little bit about Rya's Geo indexing, and
> >- a mentioning of Rya's full-text indexing.
> >
> > I am the implementer of the original temporal index code, so if you have
> > some ideas about an index you'd like to create, using or making tweaks to
> > these indexes, this session might be what you need to get started.
> >
> > No screen sharing this week, but we can use the following phone
> conference
> > for the discussion:
> >
> > Call-in toll-free number: 1-888-598-1409 <1-888-5981409>
> > Attendee access code: 7483409
> >
> > I'll send out slides at some point before the working group.
> >
> > Talk to you Wednesday!
> >
> > David Lotts
> >
>
>
>
> --
> 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/
>

Re: what is rya level of support for sparql 1.1 standard

[David Lotts]

Henri,

Getting internal RYA exceptions submitting valid sparql 1,1 queries:
>
That error looks like an empty SPARQL query.  Rya currently does not
support a query that matches everything.

Make sure that you are using the "develop" branch if you are building from
source.  Either that or deploy the VagrantExample.

---

As far as your question about standard SPARQL compliance, my understanding
is that it supports what RDF4J Sail implements.  (formerly OpenRDF,
Sesame)  You could check the release notes for the version of the SAIL
library as a dependency listed in the Rya pom.xml.

>From http://rdf4j.org/about.docbook?view

Sesame fully supports the SPARQL 1.1 query and update languages for
expressive querying and offers transpararent access to remote RDF
repositories using the exact same API as for local access.

david.