[GitHub] kafka pull request #3520: MINOR: Typo error corrected in the KStream Javadoc...

2017-07-11 Thread Kamal15
GitHub user Kamal15 opened a pull request:

https://github.com/apache/kafka/pull/3520

MINOR: Typo error corrected in the KStream Javadoc.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Kamal15/kafka stream_doc

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/3520.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3520


commit 2bf60f90a3c53ffb08fe488b151f09eca8437b1b
Author: Kamal C 
Date:   2017-07-11T10:19:02Z

MINOR: Typo error corrected in the KStream Javadoc.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka-site pull request #66: New landing page for Streams API

2017-07-11 Thread miguno
Github user miguno commented on a diff in the pull request:

https://github.com/apache/kafka-site/pull/66#discussion_r126674750
  
--- Diff: 0110/streams/index.html ---
@@ -18,56 +18,192 @@
 
 
 

[GitHub] kafka-site pull request #66: New landing page for Streams API

2017-07-11 Thread miguno
Github user miguno commented on a diff in the pull request:

https://github.com/apache/kafka-site/pull/66#discussion_r126674877
  
--- Diff: 0110/streams/index.html ---
@@ -18,56 +18,192 @@
 
 
 

[GitHub] kafka pull request #2562: MINOR: Update docstring for "offsets.retention.min...

2017-07-11 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/2562


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: [DISCUSS] KIP-173: Add prefix to StreamsConfig to enable setting default internal topic configs

2017-07-11 Thread Matthias J. Sax
I think, it might be helpful to add a "admin." prefix, too. For configs
for StreamsKafkaClient and later AdminClient.

Can so picky back this on this KIP or should we do a new KIP?


-Matthias

On 7/10/17 6:45 PM, Guozhang Wang wrote:
> Thanks Damian. LGTM.
> 
> Guozhang
> 
> On Mon, Jul 10, 2017 at 1:35 PM, Damian Guy  wrote:
> 
>> Thanks Guozhang, i added a couple of example usages to the KIP
>>
>> On Fri, 30 Jun 2017 at 17:06 Guozhang Wang  wrote:
>>
>>> Thanks for the proposal Damian.
>>>
>>> The PR looks promising to me. One minor comment for the wiki page is that
>>> you can add some example on how to call the proposed interface (e.g. the
>>> ones you added in unit test in the PR).
>>>
>>> Another question is that this variable will not be included in the web
>> docs
>>> in `toHtmlTable` unfortunately, but I do not have a better approach
>> either.
>>> So maybe we can do no better than manually change the web docs for
>>> educating users.
>>>
>>>
>>> Guozhang
>>>
>>>
>>> On Fri, Jun 30, 2017 at 4:18 AM, Damian Guy 
>> wrote:
>>>
 Hi,

 I've put together what will hopefully be a not too contentious KIP to
 enable the setting of default configs for streams internal topics via
 StreamsConfig.

 You can find the KIP here:
 https://cwiki.apache.org/confluence/display/KAFKA/KIP-
 173%3A+Add+prefix+to+StreamsConfig+to+enable+setting+default+internal+
 topic+configs
 There is a PR here: https://github.com/apache/kafka/pull/3459

 Thanks,
 Damian

>>>
>>>
>>>
>>> --
>>> -- Guozhang
>>>
>>
> 
> 
> 



signature.asc
Description: OpenPGP digital signature


Re: [VOTE] KIP 130: Expose states of active tasks to KafkaStreams public API

2017-07-11 Thread Matthias J. Sax
Florian,

I guess you can close this vote.


-Matthias

On 6/30/17 12:26 AM, Sriram Subramanian wrote:
> +1
> 
> On Fri, Jun 30, 2017 at 12:10 AM, Damian Guy  wrote:
> 
>> I know i voted before, but now my vote is binding so...
>>
>> +1 (binding)
>>
>> On Thu, 18 May 2017 at 23:46 Matthias J. Sax 
>> wrote:
>>
>>> +1
>>>
>>> On 5/18/17 8:26 AM, Bill Bejeck wrote:
 +1

 On Thu, May 18, 2017 at 6:54 AM, Florian Hussonnois <
>>> fhussonn...@gmail.com>
 wrote:

> Hi all,
>
> I've finally found time to update the KIP. The toString() is annotated
>>> as
> deprecated. I have also rebase the PR with the current trunk.
> So sorry to have been so long on this KIP.
>
> Thanks.
>
> 2017-04-24 18:56 GMT+02:00 Guozhang Wang :
>
>> Florian, could you also add the part of deprecating
> `KafkaStreams.toString`
>> in your KIP as well?
>>
>>
>> Guozhang
>>
>> On Fri, Apr 21, 2017 at 8:32 AM, Damian Guy 
> wrote:
>>
>>> +1
>>>
>>> On Fri, 21 Apr 2017 at 09:06 Eno Thereska 
>> wrote:
>>>
 +1 (non-binding)

 Thanks
 Eno

> On 21 Apr 2017, at 05:58, Guozhang Wang 
> wrote:
>
> +1. Thanks a lot for the KIP!
>
> Guozhang
>
> On Wed, Apr 5, 2017 at 1:57 PM, Florian Hussonnois <
 fhussonn...@gmail.com>
> wrote:
>
>> Hi All,
>>
>> I would like to start the vote for the KIP-130 :
>>
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP+
>> 130%3A+Expose+states+of+active+tasks+to+KafkaStreams+public+API
>>
>> Thanks,
>>
>> --
>> Florian HUSSONNOIS
>>
>
>
>
> --
> -- Guozhang


>>>
>>
>>
>>
>> --
>> -- Guozhang
>>
>
>
>
> --
> Florian HUSSONNOIS
>

>>>
>>>
>>
> 



signature.asc
Description: OpenPGP digital signature


Build failed in Jenkins: kafka-trunk-jdk8 #1802

2017-07-11 Thread Apache Jenkins Server
See 


Changes:

[jason] MINOR: Update docstring for "offsets.retention.minutes" config

--
[...truncated 4.70 MB...]

org.apache.kafka.streams.kstream.internals.KStreamKStreamLeftJoinTest > 
testWindowing PASSED

org.apache.kafka.streams.kstream.internals.KTableForeachTest > testForeach 
STARTED

org.apache.kafka.streams.kstream.internals.KTableForeachTest > testForeach 
PASSED

org.apache.kafka.streams.kstream.internals.KTableForeachTest > testTypeVariance 
STARTED

org.apache.kafka.streams.kstream.internals.KTableForeachTest > testTypeVariance 
PASSED

org.apache.kafka.streams.kstream.internals.KStreamPrintTest > 
testPrintKeyValueWithName STARTED

org.apache.kafka.streams.kstream.internals.KStreamPrintTest > 
testPrintKeyValueWithName PASSED

org.apache.kafka.streams.kstream.internals.GlobalKTableJoinsTest > 
shouldInnerJoinWithStream STARTED

org.apache.kafka.streams.kstream.internals.GlobalKTableJoinsTest > 
shouldInnerJoinWithStream PASSED

org.apache.kafka.streams.kstream.internals.GlobalKTableJoinsTest > 
shouldLeftJoinWithStream STARTED

org.apache.kafka.streams.kstream.internals.GlobalKTableJoinsTest > 
shouldLeftJoinWithStream PASSED

org.apache.kafka.streams.kstream.internals.AbstractStreamTest > 
testShouldBeExtensible STARTED

org.apache.kafka.streams.kstream.internals.AbstractStreamTest > 
testShouldBeExtensible PASSED

org.apache.kafka.streams.kstream.internals.KStreamMapValuesTest > 
testFlatMapValues STARTED

org.apache.kafka.streams.kstream.internals.KStreamMapValuesTest > 
testFlatMapValues PASSED

org.apache.kafka.streams.kstream.internals.KStreamFlatMapTest > testFlatMap 
STARTED

org.apache.kafka.streams.kstream.internals.KStreamFlatMapTest > testFlatMap 
PASSED

org.apache.kafka.streams.kstream.internals.WindowedStreamPartitionerTest > 
testCopartitioning STARTED

org.apache.kafka.streams.kstream.internals.WindowedStreamPartitionerTest > 
testCopartitioning PASSED

org.apache.kafka.streams.kstream.internals.WindowedStreamPartitionerTest > 
testWindowedSerializerNoArgConstructors STARTED

org.apache.kafka.streams.kstream.internals.WindowedStreamPartitionerTest > 
testWindowedSerializerNoArgConstructors PASSED

org.apache.kafka.streams.kstream.internals.WindowedStreamPartitionerTest > 
testWindowedDeserializerNoArgConstructors STARTED

org.apache.kafka.streams.kstream.internals.WindowedStreamPartitionerTest > 
testWindowedDeserializerNoArgConstructors PASSED

org.apache.kafka.streams.kstream.internals.KStreamKTableLeftJoinTest > testJoin 
STARTED

org.apache.kafka.streams.kstream.internals.KStreamKTableLeftJoinTest > testJoin 
PASSED

org.apache.kafka.streams.kstream.internals.UnlimitedWindowTest > 
shouldAlwaysOverlap STARTED

org.apache.kafka.streams.kstream.internals.UnlimitedWindowTest > 
shouldAlwaysOverlap PASSED

org.apache.kafka.streams.kstream.internals.UnlimitedWindowTest > 
cannotCompareUnlimitedWindowWithDifferentWindowType STARTED

org.apache.kafka.streams.kstream.internals.UnlimitedWindowTest > 
cannotCompareUnlimitedWindowWithDifferentWindowType PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullMapperOnMapValues STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullMapperOnMapValues PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullPredicateOnFilter STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullPredicateOnFilter PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullOtherTableOnJoin STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullOtherTableOnJoin PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullSelectorOnGroupBy STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullSelectorOnGroupBy PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullJoinerOnLeftJoin STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullJoinerOnLeftJoin PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > testStateStore 
STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > testStateStore 
PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowEmptyFilePathOnWriteAsText STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowEmptyFilePathOnWriteAsText PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullOtherTableOnLeftJoin STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullOtherTableOnLeftJoin PASSED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shouldNotAllowNullSelectorOnToStream STARTED

org.apache.kafka.streams.kstream.internals.KTableImplTest > 
shou

[GitHub] kafka pull request #3472: MINOR: Upgraded RocksDB to 5.3.6

2017-07-11 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/kafka/pull/3472


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Created] (KAFKA-5582) Log compaction with preallocation enabled does not trim segments

2017-07-11 Thread Jason Aliyetti (JIRA)
Jason Aliyetti created KAFKA-5582:
-

 Summary: Log compaction with preallocation enabled does not trim 
segments
 Key: KAFKA-5582
 URL: https://issues.apache.org/jira/browse/KAFKA-5582
 Project: Kafka
  Issue Type: Bug
Affects Versions: 0.10.1.1
 Environment: Linux, Windows
Reporter: Jason Aliyetti


Unexpected behavior occurs when a topic is configured to preallocate files and 
has a retention policy of compact.

When log compaction runs, the cleaner attempts to gather groups of segments to 
consolidate based on the max segment size.  
When preallocation is enabled all segments are that size and thus each 
individual segment is considered for compaction.

When compaction does occur, the resulting cleaned file is sized based on that 
same configuration.  This means that you can have very large files on disk that 
contain little or no data which partly defeats the point of compacting. 

The log cleaner should trim these segments to free up disk space.  That way 
they would free up disk space and be able to be further compacted on subsequent 
runs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[GitHub] kafka-site pull request #66: New landing page for Streams API

2017-07-11 Thread derrickdoo
Github user derrickdoo commented on a diff in the pull request:

https://github.com/apache/kafka-site/pull/66#discussion_r126789920
  
--- Diff: 0110/streams/index.html ---
@@ -18,56 +18,192 @@
 
 
 

Build failed in Jenkins: kafka-trunk-jdk8 #1803

2017-07-11 Thread Apache Jenkins Server
See 


Changes:

[damian.guy] MINOR: Upgraded RocksDB to 5.3.6

--
[...truncated 3.79 MB...]

org.apache.kafka.common.security.scram.ScramMessagesTest > 
validServerFirstMessage PASSED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
invalidServerFinalMessage STARTED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
invalidServerFinalMessage PASSED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
invalidClientFirstMessage STARTED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
invalidClientFirstMessage PASSED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
validClientFinalMessage STARTED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
validClientFinalMessage PASSED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
invalidServerFirstMessage STARTED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
invalidServerFirstMessage PASSED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
validServerFinalMessage STARTED

org.apache.kafka.common.security.scram.ScramMessagesTest > 
validServerFinalMessage PASSED

org.apache.kafka.common.security.ssl.SslFactoryTest > 
testSslFactoryWithoutPasswordConfiguration STARTED

org.apache.kafka.common.security.ssl.SslFactoryTest > 
testSslFactoryWithoutPasswordConfiguration PASSED

org.apache.kafka.common.security.ssl.SslFactoryTest > testClientMode STARTED

org.apache.kafka.common.security.ssl.SslFactoryTest > testClientMode PASSED

org.apache.kafka.common.security.ssl.SslFactoryTest > 
testSslFactoryConfiguration STARTED

org.apache.kafka.common.security.ssl.SslFactoryTest > 
testSslFactoryConfiguration PASSED

org.apache.kafka.common.security.kerberos.KerberosNameTest > testParse STARTED

org.apache.kafka.common.security.kerberos.KerberosNameTest > testParse PASSED

org.apache.kafka.common.security.auth.KafkaPrincipalTest > 
testPrincipalNameCanContainSeparator STARTED

org.apache.kafka.common.security.auth.KafkaPrincipalTest > 
testPrincipalNameCanContainSeparator PASSED

org.apache.kafka.common.security.auth.KafkaPrincipalTest > 
testEqualsAndHashCode STARTED

org.apache.kafka.common.security.auth.KafkaPrincipalTest > 
testEqualsAndHashCode PASSED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForServerWithListenerNameOverride STARTED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForServerWithListenerNameOverride PASSED

org.apache.kafka.common.security.JaasContextTest > testMissingOptionValue 
STARTED

org.apache.kafka.common.security.JaasContextTest > testMissingOptionValue PASSED

org.apache.kafka.common.security.JaasContextTest > testSingleOption STARTED

org.apache.kafka.common.security.JaasContextTest > testSingleOption PASSED

org.apache.kafka.common.security.JaasContextTest > 
testNumericOptionWithoutQuotes STARTED

org.apache.kafka.common.security.JaasContextTest > 
testNumericOptionWithoutQuotes PASSED

org.apache.kafka.common.security.JaasContextTest > testConfigNoOptions STARTED

org.apache.kafka.common.security.JaasContextTest > testConfigNoOptions PASSED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForServerWithWrongListenerName STARTED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForServerWithWrongListenerName PASSED

org.apache.kafka.common.security.JaasContextTest > testNumericOptionWithQuotes 
STARTED

org.apache.kafka.common.security.JaasContextTest > testNumericOptionWithQuotes 
PASSED

org.apache.kafka.common.security.JaasContextTest > testQuotedOptionValue STARTED

org.apache.kafka.common.security.JaasContextTest > testQuotedOptionValue PASSED

org.apache.kafka.common.security.JaasContextTest > testMissingLoginModule 
STARTED

org.apache.kafka.common.security.JaasContextTest > testMissingLoginModule PASSED

org.apache.kafka.common.security.JaasContextTest > testMissingSemicolon STARTED

org.apache.kafka.common.security.JaasContextTest > testMissingSemicolon PASSED

org.apache.kafka.common.security.JaasContextTest > testMultipleOptions STARTED

org.apache.kafka.common.security.JaasContextTest > testMultipleOptions PASSED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForClientWithListenerName STARTED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForClientWithListenerName PASSED

org.apache.kafka.common.security.JaasContextTest > testMultipleLoginModules 
STARTED

org.apache.kafka.common.security.JaasContextTest > testMultipleLoginModules 
PASSED

org.apache.kafka.common.security.JaasContextTest > testMissingControlFlag 
STARTED

org.apache.kafka.common.security.JaasContextTest > testMissingControlFlag PASSED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForServerWithListenerNameAndFallback STARTED

org.apache.kafka.common.security.JaasContextTest > 
testLoadForServerWithListenerNameAndFallback PASSED

org.apache.kafka.common

[jira] [Created] (KAFKA-5583) Provide a "OS independent" file rename and delete mechanism

2017-07-11 Thread M. Manna (JIRA)
M. Manna created KAFKA-5583:
---

 Summary: Provide a "OS independent" file rename and delete 
mechanism
 Key: KAFKA-5583
 URL: https://issues.apache.org/jira/browse/KAFKA-5583
 Project: Kafka
  Issue Type: Improvement
  Components: clients, core
Affects Versions: 0.10.2.1
 Environment: Windows
Reporter: M. Manna


This is related to 
[KAFKA-1194|https://issues.apache.org/jira/browse/KAFKA-1194] and specific to 
Windows. I thought it would be better to address this as a KIP item since it's 
OS platform specific.

Quite a lot of unit tests run on Windows platform fails after gradle build 
because of the same. Could I please request you to put some thought whether 
considering a platform-independent way of handling file renaming and deletion? 






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: [DISCUSS] KIP-167: Add interface for the state store restoration process

2017-07-11 Thread Bill Bejeck
Guozhang, thanks for the comments, I've updated the KIP.


Bill

On Wed, Jul 5, 2017 at 10:10 PM, Guozhang Wang  wrote:

> Bill,
>
> Thanks for the updated KIP. From your WIP PR I think one piece of
> information that still need to be included in the KIP is that the library
> will check the type of the restoreCallback in runtime, and if it is
> extending StateRestoreListener it will also execute its functions at the
> runtime. SO StateRestoreListener's APIs will be called in two places:
>
> 1) if the instance-level listener is set, then triggered on each poll call;
> 2) if the state-store-level callback is extending the listener, then
> triggered for each poll call that is restoring that specific store.
>
> Otherwise it may be still confusing to readers.
>
>
> Guozhang
>
>
> On Fri, Jun 30, 2017 at 2:08 PM, Bill Bejeck  wrote:
>
> > Hi Eno,
> >
> > Thanks for the comment.
> >
> > Depending on how users implement the `onBatchRestore` it could
> potentially
> > slow down the restoration.
> >
> > However IMHO it shouldn't present an issue as in practice I suspect users
> > simply want a status update of how far along the restoration process has
> > progressed.
> >
> > But having said that, other than documenting users need to keep
> processing
> > in `onBatchRestore` to an absolute minimum I don't have any good ideas on
> > how to mitigate that situation ATM (making the call to `onBatchRestore`
> in
> > an async manner? but adds complexity).  WDYT?
> >
> > Thanks,
> > Bill
> >
> > On Fri, Jun 30, 2017 at 12:37 PM, Eno Thereska 
> > wrote:
> >
> > > Thanks Bill,
> > >
> > > My only remaining question is whether we expect that calling
> > > `onBatchRestore` after each `poll` could slow down the restoration?
> > >
> > > Thanks
> > > Eno
> > >
> > >
> > > > On Jun 30, 2017, at 4:27 PM, Bill Bejeck  wrote:
> > > >
> > > > Damian,
> > > >
> > > > Thanks for comments.  I've updated the KIP with the abstract classes.
> > > >
> > > > Thanks,
> > > > Bill
> > > >
> > > > On Fri, Jun 30, 2017 at 9:57 AM, Damian Guy 
> > > wrote:
> > > >
> > > >> Thanks for the updated KIP Bill.
> > > >>
> > > >> In the PR you have AbstractBatchingRestoreCallback and
> > > >> AbstractNotifyingRestoreCallback which are both in public packages,
> > so
> > > are
> > > >> part of the API. I think you need to add those to the KIP to round
> it
> > > off.
> > > >>
> > > >> Otherwise LGTM.
> > > >>
> > > >> Thanks,
> > > >> Damian
> > > >>
> > > >> On Fri, 30 Jun 2017 at 12:39 Bill Bejeck  wrote:
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> I updated the KIP yesterday and reposted on the original thread,
> but
> > I
> > > >>> think it may get lost in the shuffle.  I'd like to have one more
> > round
> > > of
> > > >>> discussion on the KIP found here:
> > > >>>
> > > >>>
> > > >>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> > > >> 167%3A+Add+interface+for+the+state+store+restoration+process
> > > >>>
> > > >>> There's also an initial PR here :
> > > >>> https://github.com/apache/kafka/pull/3325
> > > >>>
> > > >>
> > >
> > >
> >
>
>
>
> --
> -- Guozhang
>


[VOTE] KIP-167: Add interface for the state store restoration process

2017-07-11 Thread Bill Bejeck
All,

With another round of discussion completed, I'd like to start the vote on
KIP-167

 now.

Thanks,
Bill


Re: [VOTE] KIP-167: Add interface for the state store restoration process

2017-07-11 Thread Bill Bejeck
Mistakenly replied to this thread, putting the vote on a separate one.

On Tue, Jul 11, 2017 at 3:43 PM, Bill Bejeck  wrote:

> All,
>
> With another round of discussion completed, I'd like to start the vote on
> KIP-167
> 
>  now.
>
> Thanks,
> Bill
>


[VOTE] KIP-167: Add interface for the state store restoration process

2017-07-11 Thread Bill Bejeck
All,

With another round of discussion completed, I'd like to start the vote on
KIP-167

 now.

Thanks,
Bill


[VOTE] KIP-167: Add interface for the state store restoration process

2017-07-11 Thread Bill Bejeck
All,

With another round of discussion completed, I'd like to start the vote on
KIP-167

 now.

Thanks,
Bill


[GitHub] kafka-site pull request #66: New landing page for Streams API

2017-07-11 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/kafka-site/pull/66


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] kafka-site issue #66: New landing page for Streams API

2017-07-11 Thread guozhangwang
Github user guozhangwang commented on the issue:

https://github.com/apache/kafka-site/pull/66
  
LGTM. Merging to asf-site.

@derrickdoo Could you file a corresponding PR against `kafka` trunk branch? 
I will merge it then to both trunk and 0.11.0 branches.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[ANNOUNCE] New Kafka PMC member Jason Gustafson

2017-07-11 Thread Guozhang Wang
Hi Everyone,

Jason Gustafson has been very active in contributing to the Kafka community
since he became a Kafka committer last September and has done lots of
significant work including the most recent exactly-once project. In
addition, Jason has initiated or participated in the design discussion of
more than 30 KIPs in which he has consistently brought in great judgement
and insights throughout his communication. I am glad to announce that Jason
has now become a PMC member of the project.

Congratulations, Jason!

-- Guozhang


Re: [ANNOUNCE] New Kafka PMC member Jason Gustafson

2017-07-11 Thread Vahid S Hashemian
Great news. Congratulations Jason!

--Vahid



From:   Guozhang Wang 
To: "dev@kafka.apache.org" 
Date:   07/11/2017 10:32 PM
Subject:[ANNOUNCE] New Kafka PMC member Jason Gustafson



Hi Everyone,

Jason Gustafson has been very active in contributing to the Kafka 
community
since he became a Kafka committer last September and has done lots of
significant work including the most recent exactly-once project. In
addition, Jason has initiated or participated in the design discussion of
more than 30 KIPs in which he has consistently brought in great judgement
and insights throughout his communication. I am glad to announce that 
Jason
has now become a PMC member of the project.

Congratulations, Jason!

-- Guozhang