[jira] [Updated] (KAFKA-717) scala 2.10 build support

2013-11-29 Thread Viktor Taranenko (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Viktor Taranenko updated KAFKA-717:
---

   Resolution: Duplicate
Fix Version/s: 0.8
   Status: Resolved  (was: Patch Available)

Yeah. Seems to be so

> scala 2.10 build support
> 
>
> Key: KAFKA-717
> URL: https://issues.apache.org/jira/browse/KAFKA-717
> Project: Kafka
>  Issue Type: Improvement
>  Components: packaging
>Affects Versions: 0.8
>Reporter: Viktor Taranenko
>  Labels: build
> Fix For: 0.8
>
> Attachments: 0001-KAFKA-717-Convert-to-scala-2.10.patch, 
> 0001-common-changes-for-2.10.patch, 0001-common-changes-for-2.10.patch, 
> 0002-java-conversions-changes.patch, 0002-java-conversions-changes.patch, 
> 0003-add-2.9.3.patch, 0003-add-2.9.3.patch, 
> 0004-Fix-cross-compile-of-tests-update-to-2.10.2-and-set-.patch, 
> KAFKA-717-complex.patch, KAFKA-717-patches-20130720.tgz, 
> KAFKA-717-simple.patch, kafka_scala_2.10.tar.gz
>
>




--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Created] (KAFKA-1153) typo in documentation introduction about partitioning

2013-11-29 Thread Joe Stein (JIRA)
Joe Stein created KAFKA-1153:


 Summary: typo in documentation introduction about partitioning
 Key: KAFKA-1153
 URL: https://issues.apache.org/jira/browse/KAFKA-1153
 Project: Kafka
  Issue Type: Bug
Reporter: Joe Stein


Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
9:45 AM (1 hour ago)

to users 
*'Not that partitioning means Kafka only provides a total order over
messages within a partition. This combined with the ability to partition
data by key is sufficient for the vast majority of applications. However,
if you require a total order over messages this can be achieved with a
topic that has only one partition, though this will mean only one consumer
process.'*

The first word should say *NOTE*, right?  Otherwise, I don't understand the
meaning.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (KAFKA-1153) typo in documentation introduction about partitioning

2013-11-29 Thread Joe Stein (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Stein updated KAFKA-1153:
-

Attachment: KAFKA-1153.patch

> typo in documentation introduction about partitioning
> -
>
> Key: KAFKA-1153
> URL: https://issues.apache.org/jira/browse/KAFKA-1153
> Project: Kafka
>  Issue Type: Bug
>Reporter: Joe Stein
> Attachments: KAFKA-1153.patch
>
>
> Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
> 9:45 AM (1 hour ago)
> to users 
> *'Not that partitioning means Kafka only provides a total order over
> messages within a partition. This combined with the ability to partition
> data by key is sufficient for the vast majority of applications. However,
> if you require a total order over messages this can be achieved with a
> topic that has only one partition, though this will mean only one consumer
> process.'*
> The first word should say *NOTE*, right?  Otherwise, I don't understand the
> meaning.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (KAFKA-1153) typo in documentation introduction about partitioning

2013-11-29 Thread Joe Stein (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Stein updated KAFKA-1153:
-

Status: Patch Available  (was: Open)

> typo in documentation introduction about partitioning
> -
>
> Key: KAFKA-1153
> URL: https://issues.apache.org/jira/browse/KAFKA-1153
> Project: Kafka
>  Issue Type: Bug
>Reporter: Joe Stein
> Attachments: KAFKA-1153.patch
>
>
> Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
> 9:45 AM (1 hour ago)
> to users 
> *'Not that partitioning means Kafka only provides a total order over
> messages within a partition. This combined with the ability to partition
> data by key is sufficient for the vast majority of applications. However,
> if you require a total order over messages this can be achieved with a
> topic that has only one partition, though this will mean only one consumer
> process.'*
> The first word should say *NOTE*, right?  Otherwise, I don't understand the
> meaning.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Resolved] (KAFKA-1152) ReplicaManager's handling of the leaderAndIsrRequest should gracefully handle leader == -1

2013-11-29 Thread Jun Rao (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jun Rao resolved KAFKA-1152.


Resolution: Fixed

Thanks for the patch. +1 and committed to trunk.

> ReplicaManager's handling of the leaderAndIsrRequest should gracefully handle 
> leader == -1
> --
>
> Key: KAFKA-1152
> URL: https://issues.apache.org/jira/browse/KAFKA-1152
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 0.8
>Reporter: Swapnil Ghike
>Assignee: Swapnil Ghike
> Fix For: 0.8.1
>
> Attachments: KAFKA-1152.patch, KAFKA-1152_2013-11-28_10:19:05.patch, 
> KAFKA-1152_2013-11-28_22:40:55.patch
>
>
> If a partition is created with replication factor 1, then the controller can 
> set the partition's leader to -1 in leaderAndIsrRequest when the only replica 
> of the partition is being bounced. 
> The handling of this request with a leader == -1 throws an exception on the 
> ReplicaManager which prevents the addition of fetchers for the remaining 
> partitions in the leaderAndIsrRequest.
> After the replica is bounced, the replica first receives a 
> leaderAndIsrRequest with leader == -1, then it receives another 
> leaderAndIsrRequest with the correct leader (which is the replica itself) due 
> to OfflinePartition to OnlinePartition state change. 
> In handling the first request, ReplicaManager should ignore the partition for 
> which the request has leader == -1, and continue addition of fetchers for the 
> remaining partitions. The next leaderAndIsrRequest will take care of setting 
> the correct leader for that partition.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (KAFKA-1153) typos in documentation

2013-11-29 Thread Joe Stein (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Stein updated KAFKA-1153:
-

Summary: typos in documentation  (was: typo in documentation introduction 
about partitioning)

> typos in documentation
> --
>
> Key: KAFKA-1153
> URL: https://issues.apache.org/jira/browse/KAFKA-1153
> Project: Kafka
>  Issue Type: Bug
>Reporter: Joe Stein
> Attachments: KAFKA-1153.patch
>
>
> Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
> 9:45 AM (1 hour ago)
> to users 
> *'Not that partitioning means Kafka only provides a total order over
> messages within a partition. This combined with the ability to partition
> data by key is sufficient for the vast majority of applications. However,
> if you require a total order over messages this can be achieved with a
> topic that has only one partition, though this will mean only one consumer
> process.'*
> The first word should say *NOTE*, right?  Otherwise, I don't understand the
> meaning.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (KAFKA-1153) typos in documentation

2013-11-29 Thread Joe Stein (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Stein updated KAFKA-1153:
-

Description: 
Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
9:45 AM (1 hour ago)

to users 
*'Not that partitioning means Kafka only provides a total order over
messages within a partition. This combined with the ability to partition
data by key is sufficient for the vast majority of applications. However,
if you require a total order over messages this can be achieved with a
topic that has only one partition, though this will mean only one consumer
process.'*

The first word should say *NOTE*, right?  Otherwise, I don't understand the
meaning.

...

Marc Labbe via kafka.apache.org 
12:57 PM (12 minutes ago)

to users 
while we're at it... I noticed the following typos in
section 4.1 Motivation (
http://kafka.apache.org/documentation.html#majordesignelements)

"we knew" instead of "we new"

Finally in cases where the stream is fed into other data systems for
serving we new the system would have to be able to guarantee
fault-tolerance in the presence of machine failures.


"led us" instead of "led use"

Supporting these uses led use to a design with a number of unique elements,
more akin to a database log then a traditional messaging system. We will
outline some elements of the design in the following sections.

  was:
Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
9:45 AM (1 hour ago)

to users 
*'Not that partitioning means Kafka only provides a total order over
messages within a partition. This combined with the ability to partition
data by key is sufficient for the vast majority of applications. However,
if you require a total order over messages this can be achieved with a
topic that has only one partition, though this will mean only one consumer
process.'*

The first word should say *NOTE*, right?  Otherwise, I don't understand the
meaning.


> typos in documentation
> --
>
> Key: KAFKA-1153
> URL: https://issues.apache.org/jira/browse/KAFKA-1153
> Project: Kafka
>  Issue Type: Bug
>Reporter: Joe Stein
> Attachments: KAFKA-1153.patch
>
>
> Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
> 9:45 AM (1 hour ago)
> to users 
> *'Not that partitioning means Kafka only provides a total order over
> messages within a partition. This combined with the ability to partition
> data by key is sufficient for the vast majority of applications. However,
> if you require a total order over messages this can be achieved with a
> topic that has only one partition, though this will mean only one consumer
> process.'*
> The first word should say *NOTE*, right?  Otherwise, I don't understand the
> meaning.
> ...
> Marc Labbe via kafka.apache.org 
> 12:57 PM (12 minutes ago)
> to users 
> while we're at it... I noticed the following typos in
> section 4.1 Motivation (
> http://kafka.apache.org/documentation.html#majordesignelements)
> "we knew" instead of "we new"
> 
> Finally in cases where the stream is fed into other data systems for
> serving we new the system would have to be able to guarantee
> fault-tolerance in the presence of machine failures.
> 
> "led us" instead of "led use"
> 
> Supporting these uses led use to a design with a number of unique elements,
> more akin to a database log then a traditional messaging system. We will
> outline some elements of the design in the following sections.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (KAFKA-1153) typos in documentation

2013-11-29 Thread Joe Stein (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Stein updated KAFKA-1153:
-

Attachment: KAFKA-1153.patch

> typos in documentation
> --
>
> Key: KAFKA-1153
> URL: https://issues.apache.org/jira/browse/KAFKA-1153
> Project: Kafka
>  Issue Type: Bug
>Reporter: Joe Stein
> Attachments: KAFKA-1153.patch
>
>
> Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
> 9:45 AM (1 hour ago)
> to users 
> *'Not that partitioning means Kafka only provides a total order over
> messages within a partition. This combined with the ability to partition
> data by key is sufficient for the vast majority of applications. However,
> if you require a total order over messages this can be achieved with a
> topic that has only one partition, though this will mean only one consumer
> process.'*
> The first word should say *NOTE*, right?  Otherwise, I don't understand the
> meaning.
> ...
> Marc Labbe via kafka.apache.org 
> 12:57 PM (12 minutes ago)
> to users 
> while we're at it... I noticed the following typos in
> section 4.1 Motivation (
> http://kafka.apache.org/documentation.html#majordesignelements)
> "we knew" instead of "we new"
> 
> Finally in cases where the stream is fed into other data systems for
> serving we new the system would have to be able to guarantee
> fault-tolerance in the presence of machine failures.
> 
> "led us" instead of "led use"
> 
> Supporting these uses led use to a design with a number of unique elements,
> more akin to a database log then a traditional messaging system. We will
> outline some elements of the design in the following sections.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (KAFKA-1153) typos in documentation

2013-11-29 Thread Joe Stein (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Stein updated KAFKA-1153:
-

Attachment: (was: KAFKA-1153.patch)

> typos in documentation
> --
>
> Key: KAFKA-1153
> URL: https://issues.apache.org/jira/browse/KAFKA-1153
> Project: Kafka
>  Issue Type: Bug
>Reporter: Joe Stein
> Attachments: KAFKA-1153.patch
>
>
> Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
> 9:45 AM (1 hour ago)
> to users 
> *'Not that partitioning means Kafka only provides a total order over
> messages within a partition. This combined with the ability to partition
> data by key is sufficient for the vast majority of applications. However,
> if you require a total order over messages this can be achieved with a
> topic that has only one partition, though this will mean only one consumer
> process.'*
> The first word should say *NOTE*, right?  Otherwise, I don't understand the
> meaning.
> ...
> Marc Labbe via kafka.apache.org 
> 12:57 PM (12 minutes ago)
> to users 
> while we're at it... I noticed the following typos in
> section 4.1 Motivation (
> http://kafka.apache.org/documentation.html#majordesignelements)
> "we knew" instead of "we new"
> 
> Finally in cases where the stream is fed into other data systems for
> serving we new the system would have to be able to guarantee
> fault-tolerance in the presence of machine failures.
> 
> "led us" instead of "led use"
> 
> Supporting these uses led use to a design with a number of unique elements,
> more akin to a database log then a traditional messaging system. We will
> outline some elements of the design in the following sections.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Updated] (KAFKA-1153) typos in documentation

2013-11-29 Thread Jun Rao (JIRA)

 [ 
https://issues.apache.org/jira/browse/KAFKA-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jun Rao updated KAFKA-1153:
---

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Thanks for the patch. +1 and committed to the website.

> typos in documentation
> --
>
> Key: KAFKA-1153
> URL: https://issues.apache.org/jira/browse/KAFKA-1153
> Project: Kafka
>  Issue Type: Bug
>Reporter: Joe Stein
> Attachments: KAFKA-1153.patch
>
>
> Dan Hoffman hoffman...@gmail.com via kafka.apache.org 
> 9:45 AM (1 hour ago)
> to users 
> *'Not that partitioning means Kafka only provides a total order over
> messages within a partition. This combined with the ability to partition
> data by key is sufficient for the vast majority of applications. However,
> if you require a total order over messages this can be achieved with a
> topic that has only one partition, though this will mean only one consumer
> process.'*
> The first word should say *NOTE*, right?  Otherwise, I don't understand the
> meaning.
> ...
> Marc Labbe via kafka.apache.org 
> 12:57 PM (12 minutes ago)
> to users 
> while we're at it... I noticed the following typos in
> section 4.1 Motivation (
> http://kafka.apache.org/documentation.html#majordesignelements)
> "we knew" instead of "we new"
> 
> Finally in cases where the stream is fed into other data systems for
> serving we new the system would have to be able to guarantee
> fault-tolerance in the presence of machine failures.
> 
> "led us" instead of "led use"
> 
> Supporting these uses led use to a design with a number of unique elements,
> more akin to a database log then a traditional messaging system. We will
> outline some elements of the design in the following sections.



--
This message was sent by Atlassian JIRA
(v6.1#6144)