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

+1 (non-binding) Verified checksums match for source release. I found a couple issues with flaky integration tests, but they can probably just be logged in JIRA. I had no issues when I used docker to verify the build with this command: docker run -it --rm -v /path/to/blank-m2-cache:/root/.m2 \

Re: 4.x branch for RDF4j updates.

I just wanted to clarify what is meant by support. I see a couple different ways this could be done. I'm pretty sure we're all talking about Process 1 below, but wanted to get a discussion going on what we're proposing. If we're considering Process 2 or 3, I think we need to be more explicit

Re: Failed build from master

Jorge, Master looks to be ok right now. There are a number of reasons why RAT might complain. Files generated by your IDE might be the culprit, or builds using different combinations of profiles might also be the culprit. You'd have to send out the rat.txt file to know for sure. For a fix, the

Re: 4.x branch for RDF4j updates.

The simplest thing for the community is to have a single branch of development that is being supported/maintained. Otherwise we're always forward/backporting new features that apply to both versions which is a pain. I do think we should push a 3.x branch so we can always do a future 3.2.13

Re: Loading Rya via Map/Reduce is this the best I can do?

Geoffry, Take a look at the RdfFileInputTool [1] in the rya.mapreduce module. It doesn't look like the shaded jar was uploaded to maven, so you will likely need to build that artifact yourself by including the "-P mr" profile when building Rya. There are instructions for loading data with the

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

+1 (non-binding) Verified sigs/checksums match for source release and maven artifacts. Built on CentOS 7.3.1611 with Maven 3.3.9 and Oracle JDK 1.8.0_144 on a fresh repo. Also built with -P geoindexing,benchmark,giraph The only potential blocker I see is the Windows issues, but I'm fine marking

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

+1 (non-binding) Verified sigs/checksums match for source release and maven artifacts. Built with maven clean install on MacOS X 10.11.6 with Maven 3.2.5 and Oracle JDK 1.8.0_72 against a blank repo. Also built with -P geoindexing,benchmark. I have concerns about the Apache Giraph license

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

I'm not voting yet, but I did run a license check and got a hit on this: (GNU Lesser Public License) FindBugs-Annotations (com.google.code.findbugs:annotations:2.0.2 - http://findbugs.sourceforge.net/) which comes from Apache Giraph [INFO] org.apache.rya:rya.giraph:jar:3.2.12-incubating [INFO] +-

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

+1 (non-binding) Verified sigs/checksums match for source release and maven artifacts. Built with all tests on CentOS 7.3.1611 with Maven 3.3.9 and Oracle JDK 1.8.0_144 on a fresh repo. Also built with -P geoindexing,benchmark. On Tue, Sep 26, 2017 at 1:27 PM, David Lotts

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

s 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 1

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

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>

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

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 r

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

-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.functions.geo/pom.xml: 3.2.11-incubating-SNAPSHOT

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

+0 (non binding) Sorry for the tardy vote. Found a UX nit on the rya.shell during verification testing. Filed and fixed under RYA-362. > On 9/2/17 1:08 AM, David Lotts wrote: > >> I am pleased to be calling this vote for the source release of Apache Rya >> (Incubating), version 3.2.11. >>

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

Sep 6, 2017 at 1:16 PM, Billie Rinaldi <bil...@apache.org> wrote: > On Wed, Sep 6, 2017 at 10:12 AM, Jeff Dasch <hcs...@gmail.com> wrote: > > > Billie, > > > > We also have some generated source (jaxb related) that is getting an > Apache > > License h

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

Billie, We also have some generated source (jaxb related) that is getting an Apache License header with a copyright line to The Apache Software Foundation from the org.codehaus.mojo:license-maven-plugin. Does generated source fall under the category of "A file without any degree of creativity"

[jira] [Created] (RYA-19) Type-o in MongoDBRyaDAO

Jeff Dasch created RYA-19: - Summary: Type-o in MongoDBRyaDAO Key: RYA-19 URL: https://issues.apache.org/jira/browse/RYA-19 Project: Rya Issue Type: Bug Components: dao Affects Versions