Add compression to C# client
Key: KAFKA-153
URL: https://issues.apache.org/jira/browse/KAFKA-153
Project: Kafka
Issue Type: Improvement
Components: clients
Affects Versions: 0.7
Reporter
[
https://issues.apache.org/jira/browse/KAFKA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Hauser updated KAFKA-153:
--
Status: Patch Available (was: Open)
> Add compression to C# client
>
>
[
https://issues.apache.org/jira/browse/KAFKA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Hauser updated KAFKA-153:
--
Attachment: KAFKA-153.patch
> Add compression to C# client
>
>
>
On Oct 10, 2011, at 5:46 PM, Chris Burroughs wrote:
> On 10/02/2011 12:16 PM, Alan D. Cabrera wrote:
>> I assume that our first release will be 0.6. Is that correct?
>
> Could someone close the old 0.6 jira milestone?
You and all the developers should have the powers to manage the versions.
I don't think it matters too much but it makes sense to me to keep them in
root. Up to you.
It wouldn't surprise me if there was some kind of documentation specifying
where it should be found but I was unable to google it.
Regards,
Alan
On Oct 10, 2011, at 8:04 PM, Neha Narkhede wrote:
> Al
Alan,
Where should the KEYS file be ? in root or trunk ?
Thanks,
Neha
On Mon, Oct 10, 2011 at 7:13 PM, Henry Saputra wrote:
> Hi Neha, thanks for the reply.
> Could you please confirm this with Alan? I am sure he said it should
> be in root but just in case.
>
> Thanks,
>
> Henry
>
> On Mon, Oc
Hi Neha, thanks for the reply.
Could you please confirm this with Alan? I am sure he said it should
be in root but just in case.
Thanks,
Henry
On Mon, Oct 10, 2011 at 7:02 PM, Neha Narkhede wrote:
> I wasn't aware it should be in root level, so I added it to trunk. Let
> me move it to root.
>
>
I wasn't aware it should be in root level, so I added it to trunk. Let
me move it to root.
Thanks,
Neha
On Mon, Oct 10, 2011 at 6:59 PM, Henry Saputra wrote:
> I remember Alan said it should be in root level. Why is there another
> one in trunk?
>
> - Henry
>
> On Mon, Oct 10, 2011 at 5:44 PM,
I remember Alan said it should be in root level. Why is there another
one in trunk?
- Henry
On Mon, Oct 10, 2011 at 5:44 PM, Chris Burroughs
wrote:
> We have two KEYS files at root/KEYS and trunk/KEYS.
>
> Which is the correct location?
>
[
https://issues.apache.org/jira/browse/KAFKA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-152:
--
Resolution: Fixed
Fix Version/s: 0.7
Status: Resolved (was: Patch Available)
+1 for the patch
On 10/02/2011 12:16 PM, Alan D. Cabrera wrote:
> I assume that our first release will be 0.6. Is that correct?
Could someone close the old 0.6 jira milestone?
We have two KEYS files at root/KEYS and trunk/KEYS.
Which is the correct location?
[
https://issues.apache.org/jira/browse/KAFKA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-91:
-
Attachment: k91-v1.txt
This magic incantation appears to work.
> zkclient does not
[
https://issues.apache.org/jira/browse/KAFKA-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-91:
-
Status: Patch Available (was: Open)
> zkclient does not show up in pom
> -
[
https://issues.apache.org/jira/browse/KAFKA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-152:
--
Status: Patch Available (was: Open)
> Include payload size in DumpLogSegments
> ---
[
https://issues.apache.org/jira/browse/KAFKA-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Burroughs updated KAFKA-152:
--
Attachment: k152-v1.txt
> Include payload size in DumpLogSegments
>
Include payload size in DumpLogSegments
---
Key: KAFKA-152
URL: https://issues.apache.org/jira/browse/KAFKA-152
Project: Kafka
Issue Type: Improvement
Components: core
Reporter: Chris
[
https://issues.apache.org/jira/browse/KAFKA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124275#comment-13124275
]
Neha Narkhede commented on KAFKA-143:
-
I'll fix the LICENSE files.
For the FSF copyrig
Hi, Everyone,
As we are getting close to releasing Kafka for the very first time in
Apache, we need to fix all the license headers per Apache requirement.
Currently, it seems that the headers for the cpp client are automatically
generated and can't be easily fixed. Can someone (in particular, the
On 10/09/2011 04:10 PM, Neha Narkhede wrote:
> I wondered if it was lying around from the time when Kafka was hosted
> on github. Thought we have forgotten to clean it up when we moved to
> Apache.
Ah okay, makes sense. I added it in r1153592 for git (and git-svn) users.
Will restore.
[
https://issues.apache.org/jira/browse/KAFKA-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124100#comment-13124100
]
Chris Burroughs commented on KAFKA-142:
---
Sorry, I meant the *dependencies* of clients
[
https://issues.apache.org/jira/browse/KAFKA-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124099#comment-13124099
]
Chris Burroughs commented on KAFKA-143:
---
- LICENSE files need to have the "Copyright
22 matches
Mail list logo