Re: [VOTE] KIP-79 - ListOffsetRequest v1 and search by timestamp methods in new consumer.

2016-09-18 Thread Becket Qin
Thanks everyone for the votes, I want to mention a minor change made to the interface. To ensure the accordance with KIP-45, we have changed the "earliestOffset()" and "latestOffset()" method to take Collection instead of Set. Thanks, Jiangjie (Becket) Qin On Sun, Sep 18, 2016 at 5:53 PM,

RE: Kafka usecase

2016-09-18 Thread Lohith Samaga M
Hi Achintya, 1. Kafka can be used as a message store. 2. What is the message arrival rate per second? 3. What is the SLA for the messages to be processed? 4. If your messages arrive faster than they are consumed, you will get a backlog of messages. In that case,

Kafka usecase

2016-09-18 Thread Ghosh, Achintya (Contractor)
Hi there, We have an usecase where we do a lot of business logic to process each message and sometime it takes 1-2 sec, so will be Kafka fit in our usecase? Thanks Achintya

Re: [VOTE] KIP-79 - ListOffsetRequest v1 and search by timestamp methods in new consumer.

2016-09-18 Thread Neha Narkhede
+1 (binding) On Wed, Sep 14, 2016 at 9:57 AM Bill Bejeck wrote: > +1 > > On Tue, Sep 13, 2016 at 11:08 PM, Jason Gustafson > wrote: > > > +1 and thanks for the great proposal! > > > > On Fri, Sep 9, 2016 at 4:38 PM, Becket Qin wrote:

Build failed in Jenkins: kafka-trunk-jdk7 #1552

2016-09-18 Thread Apache Jenkins Server
See Changes: [ismael] MINOR: Fix reference to argument in `LogSegment.translateOffset` -- [...truncated 13302 lines...] org.apache.kafka.streams.processor.internals.StreamThreadTest >

Build failed in Jenkins: kafka-trunk-jdk7 #1551

2016-09-18 Thread Apache Jenkins Server
See -- [...truncated 13643 lines...] org.apache.kafka.streams.processor.internals.StreamThreadTest > testMaybeCommit PASSED org.apache.kafka.streams.processor.internals.StreamThreadTest >

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

2016-09-18 Thread Apache Jenkins Server
See Changes: [ismael] MINOR: Fix reference to argument in `LogSegment.translateOffset` -- [...truncated 3559 lines...] kafka.integration.SaslSslTopicMetadataTest >

[GitHub] kafka pull request #1876: Matched method comment argument name to actual arg...

2016-09-18 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1876 --- 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

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

2016-09-18 Thread Apache Jenkins Server
See Changes: [jason] KAFKA-2063; Bound fetch response size (KIP-74) -- [...truncated 3055 lines...] kafka.log.CleanerTest > testCleanSegments STARTED kafka.log.CleanerTest > testCleanSegments

Build failed in Jenkins: kafka-trunk-jdk7 #1550

2016-09-18 Thread Apache Jenkins Server
See Changes: [jason] KAFKA-2063; Bound fetch response size (KIP-74) -- [...truncated 5590 lines...] kafka.api.PlaintextProducerSendTest > testSendCompressedMessageWithLogAppendTime STARTED

Re: ProducerRecord/Consumer MetaData/Headers

2016-09-18 Thread Michael Pearce
Hi Ismaelj Thanks, my wiki user is michael.andre.pearce. Re the link thanks again, actually indeed we started off trying to do this after we lost the ability to use the key to hold metadata once the compaction feature came, but it actually abusing the payload isn't imo a great solution, and

[jira] [Updated] (KAFKA-2063) Bound fetch response size (KIP-74)

2016-09-18 Thread Jason Gustafson (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2063: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull

[GitHub] kafka pull request #1812: KIP-74: Add fetch response size limit and implemen...

2016-09-18 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1812 --- 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

[GitHub] kafka pull request #1878: MINOR: Add `KafkaServerStartable` constructor over...

2016-09-18 Thread ijuma
GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1878 MINOR: Add `KafkaServerStartable` constructor overload for compatibility We added the `reporters` parameter as part of KIP-74: Cluster Id. You can merge this pull request into a Git repository by

[GitHub] kafka pull request #1877: Use pre-calculated value in trace message

2016-09-18 Thread lukezaparaniuk
GitHub user lukezaparaniuk opened a pull request: https://github.com/apache/kafka/pull/1877 Use pre-calculated value in trace message Replaced the math.min(size, sizeInBytes) call with the count variable that has already been calculated within the writeTo method You can merge this

[GitHub] kafka pull request #1876: Matched method comment argument name to actual arg...

2016-09-18 Thread lukezaparaniuk
GitHub user lukezaparaniuk opened a pull request: https://github.com/apache/kafka/pull/1876 Matched method comment argument name to actual argument name Changed the lowerBound argument reference in the summary comment of the translateOffset method to match the actual argument name:

[jira] [Commented] (KAFKA-4190) kafka-reassign-partitions does not report syntax problem in json

2016-09-18 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15500558#comment-15500558 ] ASF GitHub Bot commented on KAFKA-4190: --- GitHub user chemikadze opened a pull request:

[jira] [Created] (KAFKA-4190) kafka-reassign-partitions does not report syntax problem in json

2016-09-18 Thread Nikolay Sokolov (JIRA)
Nikolay Sokolov created KAFKA-4190: -- Summary: kafka-reassign-partitions does not report syntax problem in json Key: KAFKA-4190 URL: https://issues.apache.org/jira/browse/KAFKA-4190 Project: Kafka

[GitHub] kafka pull request #1875: KAFKA-4190 kafka-reassign-partitions does not repo...

2016-09-18 Thread chemikadze
GitHub user chemikadze opened a pull request: https://github.com/apache/kafka/pull/1875 KAFKA-4190 kafka-reassign-partitions does not report syntax problem in json When specifying invalid json file, kafka-reassign-partitions fails with error "file is empty" instead of reporting

Re: ProducerRecord/Consumer MetaData/Headers

2016-09-18 Thread Ismael Juma
Hi Mike, If you give me your wiki user name, I can give you the required permissions to post a KIP. This is definitely a big change and there is no clear consensus if changing the Kafka message format is the right way (it would be good not to pay the cost if you don't need it) or if it should be

Re: Permission to edit KIP pages

2016-09-18 Thread Ismael Juma
Hi KN, What's your wiki user name? Ismael On Sun, Sep 18, 2016 at 3:02 AM, Khurrum Nasim wrote: > Hi, > > I wanted to edit a KIP page and would like to get the permission for that. > Currently I don't have edit authorization. It does not show me an option to > edit. >

Re: ProducerRecord/Consumer MetaData/Headers

2016-09-18 Thread Michael Pearce
Hi All, (again) If it helps the discussion, and almost ready patch implementing this is available here: https://github.com/michaelandrepearce/kafka The biggest/most core change is obviously the kafka.message.Message object. Some key bits in this implementation is the server side, and