Re: Workflow for Rya contributors - please comment

Josh: thanks for the advice, info, and links. Adina: I added two components that I copied from accumulo [1]: "examples" and "docs". Let me know if you think these are useful. Feel free to change/remove/merge/rename them. All: Also, I added an issue to clean up the docs structure [2] and

Re: commits@rya list?

I concur. commits@rya and notifications@rya. How do we do this? Also, how do we ping infrastructure to let them know that it hasn't been pushed to github? As for the 49 emails: yeah, we saw that on the initial commit from Puja, too. RYA-7 updated all of the License headers, so we essentially

Re: January 2016 Report

3:54 PM, "Adina Crainiceanu" <ad...@usna.edu> wrote: > > > I think it looks great. > > > > Thanks! > > Adina > > > > On Thu, Dec 31, 2015 at 2:01 PM, Aaron D. Mihalik < > aaron.miha...@gmail.com > > > > > wrote: &g

Re: Bad Git Commit / Advice?

tor-rya.git' On Tue, Dec 22, 2015 at 12:21 PM Josh Elser <josh.el...@gmail.com> wrote: > Since there's still no force-push on master (AFAIK), just use `git > revert` on master. > > Aaron D. Mihalik wrote: > > I've made the first big mistake on the git repo for Rya. > >

Re: Bad Git Commit / Advice?

gt; > > Sent from my iPhone > > > >> On Dec 22, 2015, at 7:19 PM, Sean Busbey<bus...@apache.org> wrote: > >> > >> When y'all say "cutting a 3.2.10 release" do you mean going through the > ASF > >> incubator process for having a

"newbie" label on Jira Issues

Puja and I were discussing having issues in JIRA that are pretty straightforward to fix and would provide a good way to get new developers' feet wet on the code base. I looked at the Accumulo JIRA and it seems like they label this as 'newbie' issues. I think we should adopt this convention as

Bad Git Commit / Advice?

I've made the first big mistake on the git repo for Rya. Basically, I pulled in three of the latest commits onto master instead of develop. Now Master is ahead of develop (and the POM on master 3.2.10-SNAPSHOT instead of 3.2.9). What's the best way to remedy this? I'm tempted to cut a 3.2.10

Re: "newbie" label on Jira Issues

good point. I'll update confluence/jira. On Sun, Dec 20, 2015 at 10:24 PM Sean Busbey <bus...@apache.org> wrote: > I'd recommend going with something like "beginner" instead, as "newbie" can > carry a negative connotation. > On Dec 18, 2015 9:11 AM, "Aa

Re: Maven Build Error

Hey Fan! Thanks for downloading Rya and testing it out. It appears that you must use Maven 3 (for kinda a funny reason... it'll hit the apache repo by default), and it appears that there are some test issues with mvm.rya.accumulo.AccumuloRyaDAOTest. You should be able to build rya using this

Re: Maven Build Error

It seems like some of the Rya files were not downloaded properly. Open the vagrant file and look for the line "echo "Downloading Rya"". Try working through those commands manually on your VMs.

Re: RYA-83

The Spark analogy is a great one and I really like the "limit n" use case. I think we should aim to implement that use case (and give a useful message when someone queries without a "limit n"). The only caveat is that is a lot easier said than done. I don't think the "limit n" is exposed in a

Rya Office Hour Slides on Confluence

It got a bit tedious to dig though dev for the slide decks, so I added a Confluence page for the slides at: https://cwiki.apache.org/confluence/display/RYA/Rya+Office+Hours

Re: MR bulk loading turtle files

You should be all set. But be careful with file splits. You can't split a turtle file at an arbitrary line (like you can with an NTriple file). --Aaron On Wed, Jun 22, 2016 at 10:40 AM Ly, Kiet wrote: > I look at the MR bulk loading tool, BulkNtripsInputTool, which support

Re: Meet RYA people on a conference

Hey Adam, I can't speak for everyone, but I don't think we currently have a specific conference lined up. That being said, Caleb presented at Accumulo Summit last year [1], and we'll definitely attend and probably submit an abstract for next year. Puja and I were also throwing around ideas

Re: Another question about assigning bugs in jira

Interesting... "Administrators" are not assignable users. "Commiters" are, though. Would it be bad if I added "administrators" as "commiters"? I'm going to assume it's not bad, and we can undo it later. More importantly, did something change? On Mon, Feb 29, 2016 at 11:53 AM Puja Valiyil

Re: Running into some issues with the installation of ryavagrant on Windows 7

Thanks Mason. Eric has submitted a PR [1] to fix this. If you can test it out and it works for you, I'll pull it into the apache fork. https://github.com/apache/incubator-rya/pull/27 On Thu, Mar 10, 2016 at 7:10 PM Mason Tran wrote: > Thanks Josh, I will give that

Rya Working Group (April 6, Noon Eastern)

All, Just a reminder that we have the Rya Working Group tomorrow. This will be an introduction for developers to get up and running with Rya. We'll go through downloading the code, building, and stepping through the Rya Examples on Accumulo. We're still having issues with Google Hangouts.

Re: Looking towards our next IPMC report

amp; mvn release:perform` as a Maven project. > > > * Try to take some help from other projects [1], [2], [3] for starters. > > > * Ask questions if you get stuck :) > > > > > > - Josh > > > > > > [1] http://accumulo.apache.org/releasing.html >

Re: Integrate jenkins to Apache-rya incuabator.

Josh Elser wrote: > > Yeah, there's some shenanigans you can do to allow posts from an address > > that isn't subscribed. I'll have to find the instructions again, though. > > I don't recall what they were anymore. > > > > Aaron D. Mihalik wrote: > >> Tha

Re: Work on populate website for Rya RYA-42

Yeah. Googling for "ostrich clipart" or "ostrich drawing" turns up a lot of good ideas too. On Tue, Apr 5, 2016 at 8:23 PM Puja Valiyil wrote: > Here's a picture of a rhea from Wikipedia David: > https://en.m.wikipedia.org/wiki/Rhea_(bird) > Sorry for the semi useless input

Re: Integrate jenkins to Apache-rya incuabator.

;> reporter configuration. Switched that and kicked a job. >> >> Josh Elser wrote: >>> From your console output: >>> >>> "No emails were triggered." >>> >>> https://builds.apache.org/job/incubator-rya-develop/6/console >

Re: locality groups

No... it does not. We've run into extreme use cases where a graph is created for each statement (as means of providing properties for a statement). In that case, Accumulo would not be happy if Rya created a locality group for each graph. --Aaron On Thu, Mar 24, 2016 at 9:29 AM Brian McBride

Re: Spark RDD

You should take a look at the Pig script processing in Rya [1][2] and the Fluo work that was just checked in [3]. The accumulo.pig transforms a SPARQL query in to a Pig script which later becomes a series of map-reduce jobs. The rya.pcj.fluo is very similar, but uses a mini-batch approach to

Re: Rya Working Group tomorrow

All, We are going to have another "Rya Working Group" discussion today at Noon (Eastern). Email me if you would like to participate and I will send you the telecon info directly. Hopefully, this will be the last time that we use a telecon line. Next time, (Wed April 6), we'll try to get this

Re: Rya Working Group Slides

, 2016 at 2:23 PM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > ... trying a smaller attachment (sorry for all of the noise). > > > On Wed, Apr 20, 2016 at 2:16 PM Aaron D. Mihalik <aaron.miha...@gmail.com> > wrote: > >> ... trying the attachment again. >

Re: Rya Working Group Slides

... trying a smaller attachment (sorry for all of the noise). On Wed, Apr 20, 2016 at 2:16 PM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > ... trying the attachment again. > > > On Wed, Apr 20, 2016 at 2:07 PM Meier, Caleb <caleb.me...@parsons.com> > wrote: &g

Re: rdf4j-workbench

Hey John, Sorry that I missed this email. I believe the template that you're looking for is here: https://github.com/apache/incubator-rya/blob/master/extras/indexing/src/main/resources/org/openrdf/repository/config/RyaAccumuloSail.ttl On Wed, Jan 11, 2017 at 8:55 PM, John Smith

Re: Timestamps and Cardinality in Queries

deep vs wide: A property path query is probably your best bet. Something like: for the following data: s:EventA p:causes s:EventB s:EventB p:causes s:EventC s:EventC p:causes s:EventD This query would start at EventB and work it's way up and down the chain: SELECT * WHERE { (|^)* ?s .

Re: Timestamps and Cardinality in Queries

t; > > > >> On Thu, Feb 23, 2017 at 2:00 PM, Liu, Eric <eric@capitalone.com> > > wrote: > > >> > > >> Cool, thanks for the help. > > >> By the way, the link to the Rya Manual is outdated on the > > rya.apache.org > > >>

Re: Timestamps and Cardinality in Queries

I put up a "limit per node" example here [1] and Rya behaves as I expected. Strangely, OpenRDF does not :/ Unfortunately, the join between the two inner "SELECT" statements is not the more efficient MultipleBindingSetsIterator. Instead, the join is the less efficient OpenRDF Join. --Aaron [1]

Re: answered: RAT complains about tinkerpop.rya

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

Re: InterruptedException

nice if I can set parameter > when sending query, for instance, 1 hour time as > ‘query.infer=false=3600’ > > On 1/19/17, 11:08 AM, "Aaron D. Mihalik" <aaron.miha...@gmail.com> wrote: > > Note that the link was supposed to be to line #86 of > RdfControlle

Re: Timestamps and Cardinality in Queries

ric@capitalone.com> wrote: > Hm, maven runs now, but it’s getting this error in the Mongo tests: > http://pastebin.com/Mt928ane > > On 3/1/17, 12:30 PM, "Aaron D. Mihalik" <aaron.miha...@gmail.com> wrote: > > That's really strange. Can you hi

Re: Timestamps and Cardinality in Queries

relationships possible, and this is our current > naïve way of doing so. > > > > Do you want to have a short call about this? I think it’d be easier to > explain/answer questions over the phone. I’m free pretty much any time > 1pm-5pm PST tomorrow (3/1). > > > > Thanks

Understanding Apache Staging Repo Rules?

I built and pushed 3.2.10-RC1 last night and it appears that it failed Staging Repo Validation. You can see the staging repo artifacts here: https://repository.apache.org/#stagingRepositories and the repo is orgapacherya-1000 I closed the staging repo and Nexus notes that the "[Close] operation

Re: here we go again

Adina has it as dev-subscr...@rya.incubator.apache.org on the Rya website. http://rya.incubator.apache.org/community/ On Wed, Aug 31, 2016 at 7:28 AM Puja Valiyil wrote: > Hey Andrew, > I think you send an email to subscribe-...@rya.incubator.apache.org. It > might need to

Meetup/Incubator Report Add

Adina/Puja: I gave an impromptu lighting talk about Rya last night at the DC Graph Database Meetup. We should add that to the next incubator report. https://www.meetup.com/graphdb-baltimore/events/233370193/ Thank you Adina for a nice website to point everyone to, and thanks Caleb for the

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

n configuration for it. > > Aaron D. Mihalik wrote: > > Apache rat is failing. Delete .\DEPENDENCIES > > > > It does not have a license header (is that required for that file?) > > On Sat, Sep 10, 2016 at 3:11 PM Adina Crainiceanu<ad...@usna.edu> > wrote: > >

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

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 wrote: > In support of

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

lease IMHO. > david. > > On Mon, Sep 12, 2016 at 12:04 PM, Aaron D. Mihalik < > aaron.miha...@gmail.com> > 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 rele

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

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

Re: Understanding Apache Staging Repo Rules?

ontaining your public signature? > > I see http://pgp.mit.edu/pks/lookup?op=vindex=0xC3CC40CAF50EAE1A, > is that they key you used to sign the artifacts? > > Aaron D. Mihalik wrote: > > I built and pushed 3.2.10-RC1 last night and it appears that it failed > > Staging Repo

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

> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check > (check-licenses) on project rya-project: Too many files with unapproved > license: 1 See RAT report in: > /home/adina/RyaRelease3.2.10/rya-project-3.2.10/target/rat.txt -> [Help 1]

[VOTE] Release Rya (Incubating) version 3.2.10

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

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

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 wrote: > Hi David, > > A number of the geo-dependencies are likely from the geo-indexing (which > uses GeoMesa (Apache 2.0) which uses

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

> > > On Sep 14, 2016, at 8:05 PM, Josh Elser <els...@apache.org> wrote: > > > > > > I would have said that this is only kosher when you have an alternative > > to the incompatibly licensed software. Is the indexer actually optional > (I > > don't have enough c

[RESULT] [VOTE] Release Rya (Incubating) version 3.2.10 RC1 Failed

Hello, The vote to release Rya (Incubating) version 3.2.10 RC1 has failed. The results are as follows: -1 (binding): Josh Elser, Adina Crainiceanu -1 (non binding): David Lotts, Caleb Meier Below is the list of JIRA tasks blocking successful release. These tasks should address the concerns

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

irst 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 pleas

Re: [DISCUSS] Path forward for release

rom my iPhone > On Oct 6, 2016, at 10:16 PM, Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > > After reviewing the PR that David submitted, it's concerning the number of > projects that would fall into this "optional" bin. Some users probably > consider these &qu

Re: [DISCUSS] Path forward for release

Fri, Oct 7, 2016 at 10:42 AM Puja Valiyil <puja...@gmail.com> wrote: > I'm fine with that. > > On Fri, Oct 7, 2016 at 9:29 AM, Aaron D. Mihalik <aaron.miha...@gmail.com> > wrote: > > > Can we remove tinkerpop.rya? I thought that this was part of the query > > bas

Review PR 100

Caleb/Kevin/Puja: Can you all review Keith's Fluo update PR? [1] I'd like to pull it in before I perform the "optional" profile. I'm taking a look at it now, but I'd like one of you all to review it as well. --Aaron [1] https://github.com/apache/incubator-rya/pull/100

Re: [DISCUSS] Path forward for release

After reviewing the PR that David submitted, it's concerning the number of projects that would fall into this "optional" bin. Some users probably consider these "core" functions (e.g. reasoning and web): Here the modules that need to be removed from the build in order to remove the geotools

Re: [DISCUSS] Path forward for release

I second Puja's confusion. I've been going off this article [1] from gnu.org: """ The LGPL and Java ... The typical arrangement for Java is that each library an application uses is distributed as a separate JAR (Java Archive) file. Applications use Java's “import” functionality to access

Re: Release Advice (Strange Build Failure Behavior)

blocking you from making a release? > You'll be building the release locally anyways [1]. > > [1] http://www.apache.org/dev/release.html#owned-controlled-hardware > > Aaron D. Mihalik wrote: > > Caleb and I went to cut a RC yesterday, and it seems like the build is in >

Re: Status of the release

ache/spark/pull/14695 [1] https://cwiki.apache.org/confluence/display/RYA/Contributing+to+Rya On Thu, Aug 18, 2016 at 9:14 AM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > Go ahead and pull in changes. That branch is in a bad state and will be > deleted. Caleb and I will re

Re: Status of the release

to master > > with similar language. I usually try to include a reasoning. > > > > > > > > On Thu, Aug 18, 2016 at 8:53 AM, Aaron D. Mihalik< > aaron.miha...@gmail.com> > > wrote: > > > >> Puja are you still using the "Commit Process for

Re: Move off of Gitflow

I'm going to implement this now. I'm going to test out the GitHub PR "closes" feature when I pull in David's build fix PR [1] [1] https://github.com/apache/incubator-rya/pull/80 On Wed, Aug 24, 2016 at 12:55 PM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > I put a ta

Re: Rya Working Group today

Thanks Puja. I'd like to discuss at least two issues: RYA-164 - Move off of Gitflow: https://issues.apache.org/jira/browse/RYA-164 RYA-163 PCJDetails Test Failures on non-EST TimeZones: https://issues.apache.org/jira/browse/RYA-163 On Wed, Aug 24, 2016 at 8:28 AM Puja Valiyil

Move off of Gitflow

I put a task in JIRA to "Move off of GitFlow" and during the working group we decided that this should be opened up for discussion on the Dev list. Concretely, I'm proposing merging "develop" into "master" and removing the "develop" branch. If I don't hear any anything "nay"s in the next day or

[VOTE] Release Apache Rya (Incubating) version 3.2.10 RC3

The Apache Rya community has voted and approved the proposed release of Apache Rya 3.2.10 (Incubating) RC3. 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.

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

Hello, The vote to release Rya (Incubating) version 3.2.10 RC3 has passed with 3 +1 votes. +1 (binding): Josh Elser Seetharam Venkatesh Sergio Fernández I will promote the artifacts to the central repo and copy them to dist/release --Aaron

Re: RC2 Release Status

re for a reason... > > Aaron D. Mihalik wrote: > > All, > > > > I'm maintaining a small spreadsheet of issues [1] we need to resolve for > > RC2. It is essentially a finer grained copy of what we have in Jira at > > RYA-184 [2] (in order to keep track of merges and w

Re: [DISCUSS] Path forward for release

Thanks Josh. I was satisfied with Puja's commits as well, so I'm going to pull those into master, create a new JIRA task for the dependencies that you mentioned, and add those to RYA-184. On Wed, Oct 12, 2016 at 2:34 PM Josh Elser wrote: > Thanks for putting this together,

Re: [DISCUSS] Path forward for release

d, Oct 12, 2016 at 2:54 PM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > Thanks Josh. I was satisfied with Puja's commits as well, so I'm going to > pull those into master, create a new JIRA task for the dependencies that > you mentioned, and add those to RYA-184. > >

Re: findbugs-annotations?

oenix/blob/master/pom.xml#L864 On Mon, Oct 17, 2016 at 2:58 PM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > I meant "fluo has a transitive dependency on findbugs:jsr305". I agree > that findbugs-annotations is good and jsr305 is bad. > > On Mon, Oct 17, 2016

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

Hello, The vote to release Rya (Incubating) version 3.2.10 RC1 has failed. -1 (binding): Aaron Mihalik Caleb Meier The following Jira tasks have been created to capture the issues blocking a successful release: RYA-200 Remove findbugs:jsr305 Dependency [1] The following Jira task have been

[VOTE] Release Rya (Incubating) version 3.2.10 RC3

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://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-3.2.10-rc3/ Ancillary artifacts such as poms, jars,

Re: Storage structure question

Good questions. Putting all of the information in the Row ID seems like a common pattern for composite indices in Accumulo, but I went back to the original Rya Paper [1] to pull out the reasoning: """ All the data for the triple resides in the Accumulo Row ID. This offers several benefits: 1) by

Re: Importing BSD 3-Clause

change the code - its covered by various CCLAs I > have on file; that includes moving copyright statements. > > Andy > > On 02/11/16 21:02, Aaron D. Mihalik wrote: > > Great info. Thanks Josh! > > > > On Wed, Nov 2, 2016 at 4:57 PM, Josh Elser <els..

Re: Post-3.2.10 release steps (was Re: [RESULT] [VOTE] Release Rya (Incubating) version 3.2.10 RC3)

imer boilerplate Do ensure that you send from your apache.org message as the message to annou...@apache.org will (likely?) be rejected otherwise. Has anyone put together release notes on the website? Aaron D. Mihalik wrote: > Hello, > > The vote to release Rya (Incubating) version 3.

Re: Importing BSD 3-Clause

Great info. Thanks Josh! On Wed, Nov 2, 2016 at 4:57 PM, Josh Elser <els...@apache.org> wrote: > > Aaron D. Mihalik wrote: > >> Mentors, >> >> We have a PR [1] that imports existing code from another project and the >> code is BSD 3-Clause Licensed.

Importing BSD 3-Clause

Mentors, We have a PR [1] that imports existing code from another project and the code is BSD 3-Clause Licensed. What's the process for including a slightly modified version of this source code into Rya? I did a bit of research into other Apache projects and it seems like this is fine if we

Re: [jira] [Created] (RYA-202) Remove tinkerpop.rya

We were using a very old version of Tinkerpop (pre Apache) and it contained some LGPL files. I assume that upgrading to the Apache version will fix the LGPL dependency issues that that we are having with the pre Apache version of TInkerpop. All of the "keep the schema graph in memory to be used

RC2 Release Status

All, I'm maintaining a small spreadsheet of issues [1] we need to resolve for RC2. It is essentially a finer grained copy of what we have in Jira at RYA-184 [2] (in order to keep track of merges and whatnot). If anyone is interested in working on RC2, check RYA-184 or this spreadsheet for an

Re: [DISCUSS] Java package change before the first ASF release?

irst release, they would occur on a > much more regular period. So I don't think it's a big deal to wait until > we have a 4.0 release, and keep 3.2.10 as the current packaging. > > Sent from my iPhone > > > On Oct 12, 2016, at 5:05 AM, Aaron D. Mihalik <aaron.miha...@gmail.co

[VOTE] Release Rya (Incubating) version 3.2.10 RC2

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://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-3.2.10-rc2/ Ancillary artifacts such as poms, jars,

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

hearing it and we'll include any additional changes in RC3. --Aaron [1] I misread "No, it's not ok :)" as "No, it's ok :)" On Sun, Oct 16, 2016 at 11:41 PM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > I am pleased to be calling this vote for the source releas

Re: findbugs-annotations?

indbugs-annotations from these > > dependencies. Whether or not you replace in c.g.s.f:findbugs-annotations > > instead is up to you (not sure if you would run into problems) > > > > Aaron D. Mihalik wrote: > >> Anyone know where I can find a repo for this artifact: &

findbugs-annotations?

Anyone know where I can find a repo for this artifact: com.github.stephenc.findbugs:findbugs-annotations:3.0.1-1 stephenc lists the Repositories here [1] but I can't find the latest release in those mentioned repos (i.e. here [2] or here [3]) I don't think we'll have this resolved for RC2, but

Re: findbugs-annotations?

c/findbugs-annotations > It appears to be apache 2, though aaron you should verify. > > On Mon, Oct 17, 2016 at 11:19 AM, Aaron D. Mihalik < > aaron.miha...@gmail.com> > wrote: > > > fluo has a transitive dependency on findbugs-annotations, not direct. > > > > My i

Added Jenkins Build on Incoming Pull Requests

All, I added a Jenkins job to build PRs as they come in. The Jenkins job is here [1] and you can see an example of a failing PR build here [2]. I'll close the failing PR in the next couple of days. Right now, Jenkins builds the optional profile and runs the junit tests (but skips the

LGPL Compatability (again) for Direct vs. Transitive Dependencies

As we discussed before, a direct dependency on a LGPL licensed jar is prohibited, but are transitive dependencies prohibited? For instance, Rya Geoindexing depends on Geomesa (Apache 2.0 licensed) and Geomesa depends on Geotools (LGPL licensed). I believe that we get into trouble in Rya

Re: LGPL Compatability (again) for Direct vs. Transitive Dependencies

it was pretty clear last time). If > the Geo-Indexing module that Rya provides is 'optional', the dependency > is OK, but I believe you still must not bundle it (e.g. uber.jar) in a > release, it would be something users can build themselves if they accept > the terms of the lgpl.

Re: Speed of queries using ORDER BY

Bad news: this query probably won't be very fast on Rya, but please don't let that discourage you from trying it out. Let us know if you need assistance. Good news: your query is fairly simple and it could be fast. Rya isn't going to do well on this query for a couple reasons: (1) Rya doesn't

Re: next release of Rya?

Hey Adina, I think this is a good idea. Thanks for sending this out and getting the process started. I'm able to support another release, but I think it would be more useful if someone else was the release manager. I'm available to work with a committer to get ready for the release and to

Re: Issues with git

Try the instructions here: https://github.com/apache/incubator-rya/tree/RYA-INFRA-PUSH On Tue, Apr 4, 2017 at 9:36 AM Puja Valiyil wrote: > Hey everyone, > > I merged three pull requests today, #121, #146, and #147. The last merge > had an error message reported with the

rya.export?

Is there a tool to export a Rya Accumulo store to an RDF file? rya.export seemed promising, but it really seems like a merge tool, not an export tool. --Aaron

master is in a bad state.

Is someone working on this? RAT doesn't like this file: Unapproved licenses: /home/jenkins/jenkins-slave/workspace/incubator-rya-master/extras/rya.pcj.fluo/rya.pcj.functions.geo/src/main/resources/META-INF/services/org.openrdf.query.algebra.evaluation.function.Function failed build:

Re: master is in a bad state.

too much -- the optionals build passes. Andrew is on it. > > On Mon, Mar 13, 2017 at 11:39 AM, Aaron D. Mihalik < > aaron.miha...@gmail.com> > wrote: > > > Is someone working on this? > > > > RAT doesn't like this file: > > > > Unapproved license

Re: Timestamps and Cardinality in Queries

m/apache/incubator-rya/blob/master/pom.xml > > On 3/1/17, 6:09 AM, "Aaron D. Mihalik" <aaron.miha...@gmail.com> wrote: > > Repos: The locationtech repo is up [1]. The issue is that your local > .m2 > repo is in a bad state. Maven is trying to get the apache pom

Re: Installing Rya from Sources

It looks like the mapreduce uses a profile to build the shaded jar. Try building with something like this: mvn clean install -Pmr On Fri, Jul 28, 2017 at 8:52 AM Matteo Cossu wrote: > Hello everybody, > I am trying to install Rya on a cluster, but I have some problems. > I

Breaking out Integration Tests

Hey devs, Some integration tests that are causing issues with the build. These are blocking us from committing PRs to apache master. Unfortunately, these issues are more than just test failures. Instead, they are causing the JVMs to die or the build to timeout. I put in a JIRA task to break

Re: SPARQL query without restriction issue

Hey Michelle, This behavior was fixed in 3.2.11. Since we don't have a 3.2.11 release yet, can you checkout out master and try it out? Here's the PR that fixed the issue: https://github.com/apache/incubator-rya/pull/136 --Aaron On Tue, Jul 18, 2017 at 8:02 AM Michele Polonioli <

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

David: Cool preview site! On Thu, Jul 27, 2017 at 8:30 PM David Lotts wrote: > 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.

Re: Podling Report Reminder - July 2017

Also, thanks for knocking out the report :) On Sat, Jul 1, 2017 at 10:18 AM Aaron D. Mihalik <aaron.miha...@gmail.com> wrote: > Email gene...@incubator.apache.org and ask for wiki editing karma. E.g.: > https://lists.apache.org/thread.html/af653849ec832b03df2e375c926e4958c68cb2c5b14f

Re: Podling Report Reminder - July 2017

Email gene...@incubator.apache.org and ask for wiki editing karma. E.g.: https://lists.apache.org/thread.html/af653849ec832b03df2e375c926e4958c68cb2c5b14f407ec4ab382c@%3Cgeneral.incubator.apache.org%3E On Sat, Jul 1, 2017 at 1:54 AM David Lotts wrote: > I was not able to log

Re: Github's disappearing mirrors

nope, the PRs are still there. On Fri, Apr 28, 2017 at 5:06 PM Puja Valiyil <puja...@gmail.com> wrote: > Does that mean we lost active pull requests? That's disappointing if so > > Sent from my iPhone > > > On Apr 28, 2017, at 4:20 PM, Aaron D. Mihalik <aaron

Github's disappearing mirrors

It appears that our mirror is gone, too :( https://github.com/apache/incubator-rya now points to "This repository is empty" I'll let infra know. --Aaron -- Forwarded message - From: Chris Lambertus Date: Fri, Apr 28, 2017 at 3:35 PM Subject: Github's

Re: Build failing

Hey Lynne, We renamed a project so you need to clean your dirs. Try running git clean -df On Mon, Aug 7, 2017 at 9:29 AM Lynne Lawrence wrote: > Hi folks, > > My Rya builds have been failing for the past couple of nights due to RAT > problems. > > I build with the

Re: Send feature descriptions for the release

on 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

  1   2   >