Howdy all-
I'm very pleased to announce that the Samza PMC has voted Boris
Shkolnik to be a Project Management Committee (PMC) Member. The PMC
is responsible for the overall health of a project andl for voting in
new committers and PMC members, as well as VOTEing on releases. Over
the past two
+1 (binding)
Ran tests, verified sig and md5. Looks good.
-Jakob
btw, were [CANCEL] emails sent out for the other RC votes? I don't
see any. Is a good idea to do so.
On 13 October 2016 at 09:54, Jagadish Venkatraman
wrote:
> +1 (non binding)
>
> On Wed, Oct 12, 2016 at 1:17 PM, Navina Ramesh
+1 binding.
Verified MD5, checked code, built and tested.
Good job, everyone.
-Jakob
On 4 October 2016 at 09:23, Jacob Maes wrote:
> +1 (non-binding)
>
> Downloaded and bin/check-all.sh on OSX
> Downloaded, built and ran unit tests on RHEL
>
> I got a checkstyle error when I tried to run bin/c
The big hurdle here is that Hello Samza (HS) should always be ready to
go and work right out of the box, whereas a fresh checkout of trunk
may (though hopefully doesn't) have issues. This is why HS by default
points to the last stable Samza release (and has to be re-branched to
track master on Sam
Hey Elias-
This is awesome work. Would be interested in opening JIRAs for the
changes you need so we can start to process them?
Thanks,
Jakob
On 30 November 2015 at 12:18, Roger Hoover wrote:
> Awesome. Thanks.
>
> On Sun, Nov 29, 2015 at 3:25 PM, Elias Levy
> wrote:
>
>> Roger,
>>
>> You a
I'm afraid I don't agree that we're anywhere near coming to a
consensus, or even that we're all agreeing on what we're discussing.
(I do totally agree that the discussion itself has been awesome both
in tone and content, though).
As Tim brought up and I mentioned, the Board is not big on subprojec
> This leads me to thinking that merging projects and communities might be a
> good idea: with the union of experience from both communities, we will
> probably build a better system that is better for users.
Is this what's being proposed though? Merging the projects seems like
a consequence of
Rewinding back to the beginning of this topic, there are effectively
three proposals on the table:
1) Chris' ideas for a direction towards a 2.0 release with an emphasis
on API and configuration simplification. This ideas are based on lots
of lessons learned from the 0.x branch and are worthy of
+1 (binding). Artifacts are good, tests pass, code looks good. Found
minor issue with test-patch (SAMZA-726), but doesn't affect release.
It's pretty standard to run weekend- or holiday-strattling votes for five days.
-Jakob
On 1 July 2015 at 20:49, Milinda Pathirage wrote:
> +1 for extendin
s/test-patch/check-all/
Guess which project I've been working on?
On 1 July 2015 at 21:22, Jakob Homan wrote:
> +1 (binding). Artifacts are good, tests pass, code looks good. Found
> minor issue with test-patch (SAMZA-726), but doesn't affect release.
>
> It's pre
As discussed, this vote has been CANCELED.
On 25 June 2015 at 16:34, Yan Fang wrote:
> no objection from me. :)
>
> Thanks,
>
> Fang, Yan
> yanfang...@gmail.com
>
> On Thu, Jun 25, 2015 at 4:18 PM, Yi Pan wrote:
>
>> Hi, all,
>>
>> I have been preparing for the new 0.9.1 RC1 and it is close to b
Good timing everybody, and very good work, Roger and Yan. Let's go
ahead and cancel this vote, get SAMZA-720 in and roll a new RC.
-jg
On 22 June 2015 at 10:59, Yi Pan wrote:
> Hi, Yan,
>
> Thanks a lot for the quick fix on the mentioned bugs. It seems the fix for
> SAMZA-720 is pretty localize
On 21 May 2015 at 23:38, Yi Pan wrote:
> if you can give a +1 to
> move forward quickly with 0.9.1 release, that would be great!
Done. Great job. Thanks.
Currently we have individual branches for each of the point releases
(0.8.1, 0.9.0, 0.9.1, etc). It may be better to have a single 0.9
branch and then demarcate the actual releases through git tags. This
way the branch becomes more stable over time as bug fixes are applied
(in a magical world whe
Hey Susan-
That volume of topics (or partitions) would be a significant burden
on both the Kafka cluster and underlying YARN cluster (for the Samza
job). A 'large number of partitions' even at places with huge Kafka
clusters is on the order of 512 or so. It sounds like you're trying
to use part
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/33305/#review81210
---
Ship it!
Ship It!
- Jakob Homan
On April 22, 2015, 8:11 a.m
This list of non-Scala projects to check is getting too long and difficult
to read. Can we just the relevant projects into a 'non-scala' map and check
for inclusion?
- Jakob Homan
On April 17, 2015, 3:47 a.m., Dan Harvey wrote:
>
> -
za-api/src/test/java/org/apache/samza/config/EnvironmentConfigRewriterTest.java
<https://reviews.apache.org/r/33305/#comment130508>
Need ASF header
- Jakob Homan
On April 17, 2015, 6:12 a.m., Dan Harvey wrote:
>
> ---
> Th
Yes, I removed the tests for JDK6 yesterday. We're 1.7 or above now
for development.
On 14 April 2015 at 12:47, Milinda Pathirage wrote:
> Hi Devs,
>
> Calcite dropped support for Java 1.6 in 1.1.0-incubating. I want to use
> Calcite 1.2.0-incubating-SNAPSHOT in samza-sql branch. Is it okay to u
Hey Dan-
I'd love for the Elastic Search stuff to be added to the main code, as
a separate module. Keeping these in the main source code keeps them
more likely to be maintained and correct.
The EvironemtnConfigRewriter can likely go in the same place as the
ConfigRewriter interface, since it does
think I am the only one signed
> the mentor in Samza project so far) are able to see it.
>
> Thanks,
>
> Fang, Yan
> yanfang...@gmail.com
>
> On Fri, Apr 10, 2015 at 11:59 AM, Jakob Homan wrote:
>>
>> Is this project proposal available for review? I get &#x
Yeah, this is fine. Incubator has a weird thing against running user
lists during Incubation. Now that we've gone TLP, we should probably
open an INFRA ticket to create a user list.
-jakob
On 8 April 2015 at 12:20, jeremy p wrote:
> Hello all,
>
> I am new to Samza. Super excited about the pr
an issue with the
>>> > > checker integration test, but I think it's best left for 0.10.0, so
>>> I'll
>>> > > open a JIRA to track that.
>>> > >
>>> > >
>>> > > On Mon, Mar 30, 2015 at 10:49 AM, Roger
een doing a lot of burn-in, and
>> > have found some issues with the torture tests in SAMZA-394. The issues
>> > appear to be with the tests themselves, not data-loss/correctness issues
>> in
>> > Samza, but I just want to make sure. Planning to run the burn-in over
That would be great. I've been trying to get to this but have failed.
I can definitely look at the release tomorrow.
-jg
On 27 March 2015 at 16:08, Yan Fang wrote:
> Hi guys,
>
> It has been 72 hours. We got +1 from Yi Pan. Do we extend the voting to
> this weekend ?
>
> Thanks,
> Fang, Yan
> y
On 18 March 2015 at 17:48, Chris Riccomini wrote:
> One thing I haven't seen, but might be relevant, is including partition
> counts in the topic.
Yeah, but then if you change the partition count later on, you've got
incorrect information forever. Or you need to create a new stream,
which might b
We've not yet had anyone running Samza on Windows, though there should
be nothing in the code to prevent this. There are no dos/powershell
batch scripts, so you'd need cygwin (or a wrapper like mobaxterm).
Patches to add this support directly would be welcome.
-jakob
On 13 February 2015 at 11:58
>>>
>> > >>>>>> Thanks
>> > >>>>>> Milinda
>> > >>>>>>
>> > >>>>>> On Mon, Feb 9, 2015 at 11:39 AM, Chris Riccomini <
>> > >>>> criccom...@apache.org>
>>
ave RB request based on another RB request (I have tried it
>> before). But what happens if the base RB request is cancelled/discarded? RB
>> is not designed to track the revision changes in a dependency chain.
>>
>>
>>
>> > Cheers,
>> > Chris
>&
> I want to avoid branches,
Just curious, any reason for this?
> and I also want to avoid revision control over JIRA
Eh? Not sure what this means...
Thanks,
jg
On 4 February 2015 at 17:11, Chris Riccomini wrote:
> Hey all,
>
> @Jakob, yeah I was thinking we'll follow our normal flow. RTC. I ju
This submodule will still be under the review-then-commit (RTC)
regime, correct?
On 4 February 2015 at 11:13, Yi Pan wrote:
> Just did the update w/ SAMZA-482.
>
> On Wed, Feb 4, 2015 at 10:31 AM, Chris Riccomini
> wrote:
>
>> I think so. There was some RB downtime, but it just got fixed. Yi, Na
/TestSamzaAppMasterTaskManager.scala
0442580
Diff: https://reviews.apache.org/r/22215/diff/
Testing
---
Existing and new unit. Now moving on to function.
Thanks,
Jakob Homan
32 matches
Mail list logo
