We wanted to do a scrub to make sure nothing fouo was part of the code base
prior to importing.
Does anyone have an opinion or is there an official policy on versioning? Do
we start fresh (1.0) or keep with our existing versions (next release would be
3.2.9)?
Thanks,
Puja
Sent from my iPhone
Has the git repo been set up yet? If so I can take on importing the code
within the next week.
Sent from my iPhone
> On Oct 9, 2015, at 1:32 PM, Josh Elser wrote:
>
> It would be great if one of the initial members capable of doing this could
> take ownership of the work to get the code out
Dumb question -- is there a nice github/gitlab interface for the apache git?
On Fri, Oct 16, 2015 at 11:03 AM, Josh Elser wrote:
> It should be your ASF credentials (the one that lets you log into
> https://id.apache.org).
>
> I'll push such a branch just to unblock things.
>
>
> Adina Crainicea
Hi Sean,
Do you have an example we can "draw from"? I'm sorry if this is in the
documentation somewhere. Also, Adina do you want to handle this or do you
want me to? I'm fine with either once I have an example.
Update on code import: will happen today by noon -- just wanted to make an
announcem
So the code is up! We still need to rebrand the package names though.
On Wed, Oct 28, 2015 at 1:58 PM, wrote:
> Repository: incubator-rya
> Updated Branches:
> refs/heads/master 013d2968d -> b8bea9b77
>
>
> initial commit
>
>
> Project: http://git-wip-us.apache.org/repos/asf/incubator-rya/rep
ample from MADLib
> which
> is a new incubator project. I can only work on the report this weekend. If
> you have time before that, please do it, otherwise I'll do it Saturday.
>
> Thanks,
> Adina
>
> On Wed, Oct 28, 2015 at 8:35 AM, Puja Valiyil wrote:
>
> > Hi Se
All,
We (David Lotts and I) were going to start working on updating the license
headers this week. Do we just run the perl scripts referenced here:
http://www.apache.org/legal/src-headers.html
Is there anything else we should do? I think that Adina already vetted the
dependencies. I'd like to g
The committer also needing code reviewed is consistent with how we did things
on github. The only exception were trivial fixes (I can't think of an example
now but I'm sure it happened).
Sent from my iPhone
> On Nov 17, 2015, at 7:46 PM, Adina Crainiceanu wrote:
>
> All, I started a wiki pag
Looks good Adina. You could mention some of the other features that people are
working on (inconsistency detection, cloning, delete support for secondary
indices).
Sent from my iPhone
> On Nov 27, 2015, at 8:57 PM, Adina Crainiceanu wrote:
>
> Hi all,
>
> I started the report for December.
What's the process we're following here? Should someone other than Aaron
review it, or can he merge the pull request directly?
Also I created a bug against Rya backed by Mongo DB -- I put the component
as "mongodao".
On Tue, Dec 1, 2015 at 3:18 PM, ASF GitHub Bot (JIRA)
wrote:
>
> [
> https
> wrote:
>
>> I'm reviewing it, but others should also. This is a big one, and I'm not
>> familiar with testing everything.
>> david.
>>
>> -Original Message-
>> From: Puja Valiyil [mailto:puja...@gmail.com]
>> Sent: Tuesday, Decembe
Commits go to commits. Aaron had also wanted to set up an issues list where
things related to jira and automated build related email traffic would go.
Sent from my iPhone
> On Dec 3, 2015, at 3:04 AM, Sean Busbey wrote:
>
> Heya folks,
>
> We have a commits@rya list, but right now all the co
+1
Sent from my iPhone
> On Dec 4, 2015, at 8:25 PM, "Hatfield, Jesse"
> wrote:
>
> +1
>
> -Original Message-
> From: Adina Crainiceanu [mailto:ad...@usna.edu]
> Sent: Friday, December 04, 2015 8:10 PM
> To: dev@rya.incubator.apache.org
> Subject: Re: [VOTE] create new mailing list
I'm ok cutting a 3.2.10 release as long as it has all the outstanding pull
requests pulled in. All should be fine if you pull in those pull requests into
develop too right before cutting a release?
Sent from my iPhone
> On Dec 22, 2015, at 5:45 PM, "Aaron D. Mihalik"
> wrote:
>
> yep, maste
Yes-- though I'm not sure how involved that is.
Sent from my iPhone
> On Dec 22, 2015, at 7:19 PM, Sean Busbey wrote:
>
> When y'all say "cutting a 3.2.10 release" do you mean going through the ASF
> incubator process for having a release?
>> On Dec 22, 2015 16:45, "Aaron D. Mihalik" wrote:
t
>>> to create, comment, vote, or watch issues.
>>> Only developers can edit, prioritize, schedule and resolve issues.
>>> ---
>>> According to http://www.apache.org/foundation/glossary.html
>>> 'Developers are also known as "contributo
Are there any errors in the logs from the map reduce jobs?
Sent from my iPhone
> On Jan 10, 2016, at 1:50 PM, Josh Elser wrote:
>
> Hi Guillaume,
>
> Guillaume wrote:
>> Hi all,
>>
>> I would like to test your tool.
>> So I downloaded the sources from GitHub then compiled them without any
>>
a jira account
> a contributor, if we wanted to reduce the friction for assigning
> tickets to new folks.
>
>> On Thu, Jan 7, 2016 at 9:57 PM, Puja Valiyil wrote:
>> Thanks Josh!
>>
>>> On Thu, Jan 7, 2016 at 10:42 PM, Josh Elser wrote:
>>>
>>
I don't think there are issues, though the primary method I've loaded data has
been through insert statements in sparql. Let us know how it goes!
Sent from my iPhone
> On Jan 20, 2016, at 3:19 PM, christian rasmussen
> wrote:
>
> All,
>
> I need to load a bunch of data into a RYA/Mongo inst
I don't think setting up some Jenkins jobs would be difficult. There's a nice
GUI for Jenkins that guides you through it and since we cleaned up the poms
recently it should be straight forward.
Does apache have a Jenkins server we could use?
Sent from my iPhone
> On Feb 18, 2016, at 2:23 PM, A
David and I tried to compile a process for creating a release -- we didn't
get that far. The main thing blocking us at this point is the whole
process for signing a release, no one we knew had a public key and then
David and I got lost/confused when trying to generate and register one.
All of this
Hi Chris,
Two questions:
1. Is this on the dev or master branch?
2. I'll check out a fresh copy and see if I can recreate. The nat error
usually only happens the second time you run mvn clean install, so I'm
wondering if there was an issue with any of the recent merges. I'm on travel
right
Hey everyone,
I can't assign bugs to myself anymore (or anyone for that matter). I
wanted to pick up RYA-34 (the issue with inference on Mongo). Can someone
assign it to me and then I can mark it as in progress?
Thanks,
Puja
Hi everyone,
We've been having regular meetings to discuss Rya development among some of
the developers, and we would like to open them up to the rest of the Rya
development community. These meetings are intended to be an opportunity to
discuss current development and get feedback on larger design
an summarize
> the meeting after on the mailing list. Remember: "if it didn't happen on a
> mailing list, it didn't happen!".
>
>
> Puja Valiyil wrote:
>
>> Hi everyone,
>> We've been having regular meetings to discuss Rya development among som
Hey everyone,
Attached are some discussion slides. I'm interested in hearing everyone's
thoughts on the future. Again, please email me if you would like to
participate -- I'll send you the call in information directly.
Thanks,
Puja
On Wed, Mar 9, 2016 at 9:32 AM, Puja Valiyil w
Hi Edward,
If you check out the indexing example project, there's a pretty nice example,
the RyaDirectExample. Aaron also put together a quick start VM-- I think it's
under extras/vagrant example or something like that. Let us know if you need
any more help.
Thanks,
Puja
Sent from my iPhone
Hi Amila,
It might also be worth someone pointing you to the Apache Jenkins site. That
is where we would want the build to be run.
Maybe one of the mentors can point you to the right place?
Sent from my iPhone
> On Mar 25, 2016, at 11:04 AM, Amila Wijayarathna
> wrote:
>
> Hi Mark,
> Thank y
I think by default some of the Lubm queries return nothing if you don't have
inference enabled. Caleb might remember exactly which ones.
Sent from my iPhone
> On Mar 25, 2016, at 8:59 PM, Lotts, David wrote:
>
> A few suggestions:
> 1. Clone from the latest development branch, not the Master.
This is mostly my fault-- I had thought that having these would spur more
development, but the fact that Aaron and my office blocks google hangouts has
made this difficult. I'll see about distributing my work telecon line-- that
would allow for the meeting to be recorded as well.
Also, we have
Here's a picture of a rhea from Wikipedia David:
https://en.m.wikipedia.org/wiki/Rhea_(bird)
Sorry for the semi useless input here.
Sent from my iPhone
> On Apr 5, 2016, at 3:35 PM, Lotts, David wrote:
>
> Adina,
> I see you have taken on RYA-42 "populate website for Rya".
> Funny, I just freed
you both read the jenkins guidelines:
>> >>>
>> >>> http://wiki.apache.org/general/Jenkins
>> >>>
>> >>> in particular, the mandatory job settings and the need to subscribe to
>> >>> infrastructure@apache and builds@ap
All,
Just a reminder that we have the Rya working group tomorrow. This week we
will be going over potential methods of improving client configuration of
Rya through a centralized administration mechanism. I'm not going to set
up a webex, but we can use the following line for tomorrow's discussion
Oops, let's include the date and time this time!
Rya Working Group
Wednesday, May 4, 2016
12:00 pm | Eastern Daylight Time (New York, GMT-04:00) | 1 hr
Call-in toll-free number: 1-888-5981409
Attendee access code: 7483409
On Tue, May 3, 2016 at 4:35 PM, Puja Valiyil wrote:
> All,
All,
Here are some slides to shape today's discussion.
Thanks,
Puja
On Tue, May 3, 2016 at 11:11 PM, Josh Elser wrote:
> Thanks for sending this out as always! I'll do my best to try to drop in
> and say hello :)
>
> Puja Valiyil wrote:
>
>> Oops, let's
-computed joins.
On Thu, May 5, 2016 at 4:58 PM, Sean Busbey wrote:
> any notes from the discussion?
>
> On Wed, May 4, 2016 at 9:50 AM, Puja Valiyil wrote:
> > All,
> > Here are some slides to shape today's discussion.
> > Thanks,
> > Puja
> >
>
Integrating Travis ci sounds good! Some tests don't run well on my Windows box
so that would be super useful!
Beyond that we had said integrating some performance benchmarking into the
infrastructure was a good use of his time?
Sent from my iPhone
> On May 9, 2016, at 1:58 PM, Adina Crainiceanu
Hi everyone,
Sorry for the late notice -- holiday weekend still has me thinking its
Monday!
We will be holding our bi-monthly working group meeting tomorrow. Caleb
and I had thought that having an overview of the use of Fluo would be a
useful topic. We thought that even if Keith Turner couldn't j
Hi Henri,
If you send us your sparql query, we may be able to point you to some query
optimizations that could improve performance.
If you don't want to share the exact query, you can reword the
predicates/constants so that they aren't sensitive. We would only care
about the general graph structur
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 wrote:
> http://10.162.96.77:8000/web.rya/queryrdf?qu
Hi Kiet,
I've been meaning to post on your ticket. This is a deliberate feature for Rya
that is intended to avoid inadvertently starting a full table scan. Since the
data stored in Rya may be extremely large since it is intended for cloud based
systems, the exception is intentionally thrown.
Hi everyone,
Sorry for the short notice but we will be holding our bi-monthly working group
meeting tomorrow. I was going to put together some notes on how inference is
implemented.
Time: 12:00 pm est, June 15
Phone number: 888-598-1409;7483409
Thanks,
Puja
>
Hi Kiet,
I'm not sure that a lot of us can disclose over the dev list a lot of the
places that Rya is currently running operationally.
As far as your other questions, I'm not aware of any hard limitations
though I'm not sure I understood the question -- maybe Aaron or Adina (or
someone else) might
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
mult
sbey wrote:
> >
> > > if the PPMC is considering new committer additions, it's worth noting
> > > in the report.
> > > especially since the situation described under community development
> > > sounds like we ought to be.
> > >
> > >
Hi everyone,
Something came up at work for tomorrow so I will not be able to lead the
Rya Office Hours discussion tomorrow. Since Adina is also out tomorrow, I
was going to suggest we cancel this week and reconvene in two weeks. If
someone would like to lead the discussion tomorrow instead, pleas
Hi Pranav,
There are three optimizations you can make to speed up ingest speeds:
1. Bypass the SAIL layer and ingest data through MapReduce
2. Turn off flushing on the AccumuloRyaDAO so that it does not flush after
each triple. This is done through setting flush to false on the
AccumuloRdfConfig
Aaron had signed himself up a few months ago, I'm not sure how far he got
though.
Sent from my iPhone
> On Jul 31, 2016, at 2:00 AM, Sean Busbey wrote:
>
> Hi folks!
>
> Anyone up for acting as the community's first release manager? It's
> been a while, and working through the process of doin
Hi everyone,
Tomorrow is the next Rya Working Group meeting. When we last met (a month
ago), we had discussed having a discussion about the new DynamoDB backend
for Rya. I'm fine with leading that discussion, but I was wondering if
anyone would rather we talk about something else. Perhaps a stat
if we can talk about the release
> tomorrow. Maybe we can figure out what needs to be done and see how
> everyone can help with the release.
>
> Thanks,
> Adina
>
> On Tue, Aug 9, 2016 at 10:20 AM, Puja Valiyil
> wrote:
>
> > Hi everyone,
>
Aaron and Caleb talked about the status of the release. They described the
remaining steps and outlined what they are planning to do this week to for
creating the release. Aaron had a question about gpg maven tools.
We spent some time talking through Jira and how as a community we need to
docume
I think what Josh said is in line with what we were thinking. The thought
would be that if any design work is done before starting a feature, that
design work would be posted to confluence or the dev list so that the
entire community has an opportunity to comment on it. There isn't an
expectation
Hey Aaron and Caleb,
I saw that there was a release branch. Should we hold off on merging
things into develop while you are working on the release? I had put off
merging pull requests while you guys were actively working so that it
wouldn't be adding work, but there are a lot of requests at this
ll in changes. That branch is in a bad state and will be
> > deleted. Caleb and I will resume the release today.
> >
> > On Thu, Aug 18, 2016 at 9:00 AM Puja Valiyil wrote:
> >
> >> Hey Aaron and Caleb,
> >> I saw that there was a release branch. Should w
Sorry for the short notice, but we will hold the Rya Working Group today at
12 PM EST.
We will be reviewing bugs in jira. In two weeks, we were planning on
having a talk about persistence in Rya and the architecture/pattern for
adding a new backend. If there is something of more interest to the g
Hey Andrew,
I think you send an email to subscribe-...@rya.incubator.apache.org. It might
need to say subscribe in the message subject.
Sent from my iPhone
> On Aug 30, 2016, at 6:50 PM, Smith, Andrew wrote:
>
> Add to dev list?
> Andrew
Hi Pranav,
I think this is likely due to the fact that filters are being evaluated client
side (so it's possible you are bringing back all 110 million triples multiple
times in your query). Can you send us your query so we can verify?
Sent from my iPhone
> On Sep 6, 2016, at 8:49 AM, Meier, Cal
ia.org/resource/List')).
> ?pages ?property ?objects .
> }
>
> Can you please provide me with some direction for using free text index or
> pre-computed joins to perform free text search .
>
>
>
> On Tuesday 06 September 2016 06:58 PM, Puja Valiyil wrote:
>
>&g
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
wrote:
> Yeah, that sounds possible. I don't like the idea of having
The indexer project has a set of configurable optional extension to Rya.
Things like support for geosparql, support for free text indexing, and support
for precomputed joins (which is where the fluo integration comes in). These
are extensions that by default are turned off. They can really in
wants these capabilities, they need the indexer
> project and all of the incompatibly licensed dependencies that come along
> with it.
> ________
> From: Puja Valiyil [puja...@gmail.com]
> Sent: Wednesday, September 14, 2016 9:49 PM
> To: dev@rya.inc
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.incuba
Hi everyone,
Sorry for the short notice, but we were supposed to have the Rya working
group today.
Time: 12 PM EST
Call in: 18885981409; 7483409#
For an agenda, I was thinking that we could discuss what is remaining for
the release and see if someone can claim responsibility for finishing up
the f
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 ma
Wouldn't that also take out precomputed joins? And are we absolutely
> > sure we don't want indexing? It seems important, couldn't we make geo
> > optional?
> >
> > Sent from my T-Mobile 4G LTE device
> >
> > -- Original message--
>
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:
vid.
>>
>> 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,
>&g
> On Fri, Oct 7, 2016 at 7:39 AM Puja Valiyil wrote:
>
> The reasoning here is not the query based inference-- it is the external
> reasoner that runs on map reduce.
> I need to double check but I think the dependency is due to referencing a
> config Utilities class that should be
file" solution and remove
> tinkerpop.rya. I'll post the PR to the dev list and give let people
> comment on the PR. I'll look at PR over the weekend if if there aren't any
> issues, I'll pull it into apache master on Sunday.
>
> --Aaron
>
> On Fri,
I'm not the best person to look at it -- Kevin would be but he isn't
available for a while. Caleb do you have time?
On Fri, Oct 7, 2016 at 11:09 AM, Aaron D. Mihalik
wrote:
> Caleb/Kevin/Puja:
>
> Can you all review Keith's Fluo update PR? [1]
>
> I'd like to pull it in before I perform the "o
I created a pull request with #2 implemented. Any comments would be
appreciated.
https://github.com/apache/incubator-rya/pull/101
On Fri, Oct 7, 2016 at 11:06 AM, Puja Valiyil wrote:
> Hey,
> I started trying to implement #2. Give me 10 minutes and I'll push it and
> you can st
t; to both the source code and binary forms of the geo-related artifacts
>>>> that you are currently bundling in Rya. GPL is forcing that the source
>>>> code for those artifacts be available, but is not implying that the
>>>> license only applies to the code in source form.
>>
-1 I think we should wait. I'd like us to have one non-breaking official
release on Apache before we start adding changes that will greatly effect end
users. Dramatically changing the Api seems like a bad idea since users will
have no choice but to update.
Theoretically once we get past the f
3.2.9 to 3.2.10. This would be along those lines and not
> present any significant API changes.
>
>> On Wed, Oct 12, 2016 at 8:30 AM Puja Valiyil wrote:
>>
>> -1 I think we should wait. I'd like us to have one non-breaking official
>> release on Apache befor
Yea findbugs-annotations is not LGPL:
https://github.com/stephenc/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
wrote:
> fluo has a transitive dependency on findbugs-annotations, not direct.
>
> My issue is that
+1 (binding)
Looked like the issues preventing the earlier release were resolved.
On Mon, Oct 24, 2016 at 3:29 PM, Aaron D. Mihalik
wrote:
> This is a gentle reminder to everyone to provide some feedback on the
> release candidate. We need at least another binding vote to continue this
> proces
Hi Merida!
That is great news -- welcome! Please take a look at Jira, and see if you
would like to work on any of the tasks that are currently unassigned.
Aaron put together a nice write up on how to contribute:
https://cwiki.apache.org/confluence/display/RYA/Contributing+to+Rya
Please email the
You both should take a look at the entity centric index -- it uses the column
family and column qualifier to store triple info outside of the row key. We
have looked at alternate storage schemes, they have been largely abandoned due
a desire to not disrupt existing users (which may have tools
I think a jira ticket and then add Adina as a watcher. She knows the process
for updating (I'm not sure everyone has permissions but I might be wrong).
Sent from my iPhone
> On Dec 14, 2016, at 2:25 PM, John Smith wrote:
>
> There is a broken link on the Rya web site and I'd like to push a fi
Looks great Adina! I thought we had invited/added more committers than
David this quarter-- am I mistaken?
On Sunday, January 1, 2017, Adina Crainiceanu wrote:
> Hi all,
>
> Happy New Year!! I hope everyone had a chance to enjoy the holidays.
>
> Below is the first draft of the podling report d
Hi John,
It's not possible to use the core Rya indices to support the graphx api--
there is a requirement for uniqueness in vertices that is not possible to
support using the core indices. To support graphx efficiently, all of the
assertions on a node of the graph must be stored on a single accum
me kind of) a Rya addon to
> Accumulo for this to work?
>
> On Mon, Jan 9, 2017 at 7:39 PM, Puja Valiyil > wrote:
>
> > Hi John,
> > It's not possible to use the core Rya indices to support the graphx api--
> > there is a requirement for uniqueness in vertic
I'm not sure if the sparql extension in itself would make Janus/Titan
equivalent to Rya-- Rya provides a no SQL backend for sail graphs and a
sparql extension wouldn't necessarily ensure you can interact with Titan as
if it was a sail repository. I imagine the sparql support in
Titan/Janus would
Even with rya details enabled, the version triple will be added (for backwards
compatibility). I'm confused over why this is an issue-- it's a single triple
in a triple store that's intended to scale to millions if not billions.
Sent from my iPhone
> On Jan 17, 2017, at 1:19 PM, Chilton, Kevin
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 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" >
No there isn't commercial support currently. Many of the current
developers work on Rya professionally, so if there was interest for
commercial support, it would probably be pretty easy to put something
together :)
On Tuesday, January 24, 2017, Ly, Kiet wrote:
> Beside community support from Ry
Hey John,
I'm pretty sure your pull request was merged-- it was pulled in through another
pull request. If not, sorry-- I thought it had been merged and then just not
closed. I was going to spend some time doing merges tomorrow so I can get it
tomorrow.
Sent from my iPhone
> On Feb 23, 201
ure if it was
>> removed in later iterations or whether it would be useful for your use
>> case. First Rya paper
>> https://www.usna.edu/Users/cs/adina/research/Rya_CloudI2012.pdf discusses
>> time ranges (Section 5.3 at the link above)
>>
>> Adina
>>
Sorry -- this is me. Well, more like this is me trusting the build server
too much -- the optionals build passes. Andrew is on it.
On Mon, Mar 13, 2017 at 11:39 AM, Aaron D. Mihalik
wrote:
> Is someone working on this?
>
> RAT doesn't like this file:
>
> Unapproved licenses:
>
> /home/jenkin
Awesome! Let us know what we can do to help put the talk together!
Sent from my iPhone
> On Mar 17, 2017, at 9:36 AM, Aaron D. Mihalik wrote:
>
> Congrats Adina!
>
>> On Fri, Mar 17, 2017 at 9:21 AM Adina Crainiceanu wrote:
>>
>> Hi,
>>
>> I'm happy to announce that "Apache Rya- A Scalable
Hey could someone look into this? I run the on demand build before merging
anything so I'm not sure what the deal is.
Sent from my iPhone
Begin forwarded message:
> From: Apache Jenkins Server
> Date: March 27, 2017 at 4:45:42 PM EDT
> To: notificati...@rya.incubator.apache.org
> Subject: inc
Hey everyone,
I merged three pull requests today, #121, #146, and #147. The last merge
had an error message reported with the push:
efrror: RPC failed; result=18, HTTP code = 200
atal: The remote end hung up unexpectedly
error: error in sideband demultiplexer
All of the changes are in the apache
he/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 push:
> > efrror: RPC
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 wrote:
>
> It appears that our mirror is gone, too :(
>
> https://github.com/apache/incubator-rya
>
> now points to "This repository is empty"
>
> I'
I can assign the ticket but was this ever resolved? I think the resolution
last time was to add people to a Jira user set manually.
Sent from my iPhone
> On May 3, 2017, at 7:04 PM, Jonathan Wonders wrote:
>
> Hi All,
>
> I'm looking to pick up issue RYA-67 but cannot self-assign based on n
There aren't any critical bug fixes, so now is just as good a time as any.
Sent from my iPhone
> On May 4, 2017, at 5:20 PM, Aaron D. Mihalik wrote:
>
> Yeah, I'll take another shot at it and iron out the process a bit more :)
>
> However, I won't have time until next week. Are there any spec
ight be a good idea to ignore them and
> reference an issue number so its clear why they are disabled.
>
> - AccumuloGetInstanceDetailsIT
> - AccumuloUninstallIT
> - AccumuloLoadStatementsFileIT
> - PrecompJoinOptimizerIntegrationTest
> - PrecompJoinOptimizerTest2
>
&
Hi Murtaza,
Rya had an official release in October of last year. We are currently
discussing having an updated release within the next couple of months. I can
find a link to the release if it is not linked from the apache website.
Sent from my iPhone
> On May 29, 2017, at 9:51 AM, Murtaza Kanc
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 auto
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.ap
1 - 100 of 161 matches
Mail list logo
