+1 (non-binding)
On Mon, Oct 6, 2014 at 5:21 PM, Sharad Agarwal wrote:
> Following the discussion earlier in the thread
> https://www.mail-archive.com/general@incubator.apache.org/msg45208.html
> I would like to call a Vote for accepting Lens as a new incubator project.
>
> The proposal is avail
On Tue, Oct 7, 2014 at 2:46 PM, jan i wrote:
> My intentation was to raise a concern, NOT to block the release (I did on
> purpose give a 0 and not -1). I am sorry if you feel its an over-statement,
> but honestly for me failing unit tests and not checking a version
> dependency (in case of older
On Sun, Oct 5, 2014 at 5:35 PM, Alan D. Cabrera wrote:
> I'm happy to do it again.
Thanks!!!
Roman.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apac
On Tue, Oct 7, 2014 at 2:46 PM, jan i wrote:
> > 4.) And lastly, as Julian mentioned on the thread that the set of fixes
> > might not be complete yet,
> > I think we need more time before we can merge these changes in to a
> release
> > with confidence to
> > support a new platform.
> >
>
> I ag
Jan,
Your concern was a valid one and definitely one worth explanation.
Please do not take my response as a rant from an upset soul :), rather an
explanation
towards why we chose to do what we did. I apologize if I sounded like one.
We are, sometime, limited by the tools that we use and one such
Hi
First let me make it clear I am not a java specialist, and secondly big
thanks to both of you for explaining more in detail what the problem is.
On 7 October 2014 21:24, Aditya wrote:
> Hi Jan,
>
> The issue was discussed on the release voting thread and there seems to be
> an agreement
>
On Tue, Oct 7, 2014 at 1:59 AM, Harald Kraemer
wrote:
> So, after this wall of text, there are two questions from me:
>
> a) is this project interesting enough for everyone? :)
> b) Are there people who would volunteer to coach me and my team through the
> proposal and the incubator?
This sounds
On Mon, Oct 6, 2014 at 4:51 AM, Sharad Agarwal wrote:
> Following the discussion earlier in the thread
> https://www.mail-archive.com/general@incubator.apache.org/msg45208.html
> I would like to call a Vote for accepting Lens as a new incubator project.
>
> The proposal is available at:
> https://
Hi Jan,
The issue was discussed on the release voting thread and there seems to be
an agreement
in the community that it may not be worth holding the release to include
Java 8 support
since
1.) Among most of the users, as evident on the vote thread, very few are
running Java 8
in dev and test env
On Tue, Oct 7, 2014 at 8:41 AM, jan i wrote:
> It seems (from the vote thread) you already have solved the problem, but
> dont want to wait for a respin, can you please at least explain why the
> project is under such a time constraint, that 72 hours is too long to wait
> to make good quality.
>
The unit test was only on Java 1.8. That problem will be resolved in the
next release which will be in roughly a month from now. The current
primary target of Drill is 1.7.
The number of reviewers for the release is an indication of how the
community doesn't view Java 1.8 as a critical platform
Hi.
I have had a look at your release and it looks good, I could not find any
formal errors.
But I took a closer look at the release vote thread, because a failing unit
test is a serious bad quality signal for me.
Whenever I test new software, I download it, build it, then run all test
cases to
Hey Harold
Those pull requests came after mine, see carbon#139 [1]. Nice catch in
698, in ours we took a different approach and loaded a custom finder within
the database plugin [2] itself. Looking forward to comparing notes and
helping where I can
-Jake
[1]: https://github.com/graphite-project/
Hi,
am I looking at the right pull requests with graphite-project/carbon#210
and #216?
Quite interesting. Sadly, I don't think I could provide exactly that python
API with our existing storage input frontend.
Just look out for the issues we fixed in
https://github.com/graphite-project/graphite-w
Hi Harald
I have been working on a similar project which enables carbon to have a
plugable backend storage system that leverages Apache Cassandra for
storage. I opened pull requests in both carbon and graphite for the
plugable backend portion and the Cassandra backend is still in the works.
Your pr
Harald Kraemer wrote on Tue, Oct 07, 2014 at 10:59:35 +0200:
> Thus, the first thought of bifroest was born: Why don't we take the good
> parts of Cyanide, a solid distributed database, such as Apache Cassandra,
> and the good parts of carbon and toss them in a big stew?
>
> That's what we did, an
Hi Harald,
it looks very interesting.
Don't hesitate to ping me if you need any help.
Regards
JB
On 10/07/2014 10:59 AM, Harald Kraemer wrote:
Hi,
we have been allowed to open-source one of our company internal projects -
currently called Bifroest. Bifroest is a storage backend for graphite-
Hi
Bifroest sounds like a very interesting project and within my field of
experience. I have worked about 3/4 year to implement circonus in ASF (It
was then decided for good reasons not to use it for alerting), and before
that I designed SCADA systems to monitor/control electrical grids.
today I
Hi,
we have been allowed to open-source one of our company internal projects -
currently called Bifroest. Bifroest is a storage backend for graphite-web,
based on Apache Cassandra. I'm quite happy about this, and now I'm in the
process of finding the best options and means to do so. This mail isn
19 matches
Mail list logo
