8592dd2878Update to suggest confluent-kafka-dotnet client
Magnus Edenhill
2017-02-24 09:37:28 +0100
8c53608db6Adding a note to README.md
Soumyajit Sahu
2016-10-31 09:46:51 -0700
f872d77639Created library as digitally signed as its required to be installed in the GAC for Sql Server Integration Services
Andy Fenna
2016-09-29 15:18:05 +0100
88161da4afUpdate log4net
Chris Andrews
2016-07-20 15:20:17 -0500
e44b9735d1Update KafkaSimpleManager.cs
Maxime Caron
2016-05-18 10:47:58 -0700
31c682f7abRemove retry loop inside KafkaSimpleManager.RefreshMetadata
Maxime Caron
2016-05-18 10:47:08 -0700
88d6356e64When FetcherRunnable detects about outOfRange, it tries to fix the issue by bump up both fectedoffset and consumedoffset ahead to the valid one. As Fetcher thread don't own and shouldn't own the consumedoffset, the consumerIterator who is the actual owner of consumedoffset update the consumedoffset back to the position it actually consumed. In the next iteration of Fetcher thread, it detects that the lag between fectedoffset consumedoffset is big enough so it stop fetching more. It is true during normal case, but it is not true when the fetchedoffset being manually set ahead instead of fetched ahead.
YixuanLiu
2016-05-16 17:00:47 -0700
5452efc41fSet the ConsumedOffsetOutOfRange value only if it get changed
YixuanLiu
2016-05-13 10:23:35 -0700
2c6d52080fConsumedOffset is handled incorrectly when an OffsetOutOfRange error is received by the fetcher When FetcherRunnable detects about outOfRange, it tries to fix the issue by bump up both fectedoffset and consumedoffset ahead to the valid one. As Fetcher thread don't own and shouldn't own the consumedoffset, the consumerIterator who is the actual owner of consumedoffset update the consumedoffset back to the position it actually consumed. In the next iteration of Fetcher thread, it detects that the lag between fectedoffset consumedoffset is big enough so it stop fetching more. It is true during normal case, but it is not true when the fetchedoffset being manually set ahead instead of fetched ahead. The fix is first, FetcherRunnable shouldn't just set the consumedoffset as it doesn't own how far it consumed. Then, when FetcherRunnable detects about outofrange error, it signal PartitionTopicInfo about ConsumedOffsetOutOfRange error and cleared the fetcher buffer as those buffered message are invalid on broker. During the next iteration of the fetcher thread, if the lag is big enough or there is outofrange error, keep fetching. When it successfully fetched, it can clear the ConsumedOffsetOutOfRange error in PartitionTopicInfo.
Yixuan Liu
2016-05-12 17:51:33 -0700
e27e82ab3dRemove unnecessary null check to avoid confusion.
Jordan Beacham
2016-05-06 12:00:49 -0500
00251b9b27Updated nuspec's log4net dependency version
mhorstma
2016-05-05 10:07:14 -0700
ff355e93a6Merge remote-tracking branch 'upstream/master' into log4netRevert
mhorstma
2016-05-05 10:03:19 -0700
d23ae4b248Reverted log4net package references back to 1.2.10
mhorstma
2016-05-05 09:16:50 -0700
749229207bOptimization and bubble up the ProducerResponseStatus to producer.Send method.
Jordan Beacham
2016-05-04 16:40:18 -0500
5649dc2d5cMerge pull request #52 from mhorstma/nugetCleanup
mhorstma
2016-05-04 10:21:48 -0700
2e0727d752Added AssemblyVersion attribs to assemblyinfo.cs
mhorstma
2016-05-03 14:23:02 -0700
e25388861dCleaning up assemblyinfo.cs project references
mhorstma
2016-05-03 13:41:58 -0700
5fcf4f0f29Updating nuspec to use assembly version. Updating log4net dependency version.
mhorstma
2016-05-03 11:29:08 -0700
00746efcf3Merge pull request #48 from dtauzell/log4net-update
mhorstma
2016-05-02 17:17:49 -0700
c26ac28a6censure consumed offset doesn't go past end of topic... this was causing an offset out of range error.
Ducas Francis
2016-04-29 15:44:20 +1000
7ba6c98081Add support for 0.9.0 and 0.10.0 protocols
Greg Fodor
2016-03-06 00:49:32 -0800
a9159ea043change Connect() to use async connect call and honor receiveTimeoutMs as connectionTimeout
danielli90
2016-04-19 11:08:57 -0700
9a44d90cf91) Fix log loss scenario during rebalance, 2) use api version 0 instead of 1, 3) Some minor performance improvement and bug fixes
Som Sahu
2016-04-04 11:22:21 -0700
f32eb7b5edRenaming to CSharpClient-for-Kafka
Razvan Iamandii
2016-04-18 10:11:26 -0700
2066c70ff0Modify Repo name and references to CSharpKafkaClient instead of Kafkanet
Razvan Iamandii
2016-04-14 13:58:57 -0700
d761482719Deleted commented out files section
mhorstma
2016-04-01 11:46:46 -0700
d87ac15b97Removing explicit assembly references from nuspec
mhorstma
2016-04-01 11:25:32 -0700
2afb96895asetup partition info with consumedOffset = auto.offset.reset - 1 for new consumer group
Ducas Francis
2016-03-31 11:36:22 +1100
3760e213d2add fetch wait max ms and fetch min bytes to consumer configuration
Ducas Francis
2016-03-28 15:05:15 +1100
ea9d0acb1ause kafka message stream interface in zookeeper consumer connector interface
Ducas Francis
2016-03-28 14:02:58 +1100
04e9f34365addition of the zookeeperconsumerconnector interface, this is to allow mocking for unit tests
geoff tsai
2016-03-14 09:21:32 +1100
84fdbedf2fextract interface for KafkaMessageStream and ConsumerIterator
Ducas Francis
2016-03-16 17:59:12 +1100
b3c1b07bd5expose producer method to send multiple producerdata in single operation on interface
Ducas Francis
2016-03-16 16:32:25 +1100
ae5ced6852override setting position of fetch offset with flag
Ducas Francis
2016-03-09 10:47:16 +1100
07658e60f6[PVS-Studio] ConsumeGroupFindNewLeaderSleepIntervalMs variable assigned to itself
jthelin
2016-03-05 10:48:32 -0800
a1676b3a9bAfter a rebalance set consumedOffset=commitedOffset and NOT consumedOffset=fetchOffset which could lead to data loss. Don't commit offset if it already commited modified: src/KafkaNET.Library/Consumers/ZookeeperConsumerConnector.cs modified: src/KafkaNET.Library/ZooKeeperIntegration/Listeners/ZKRebalancerListener.cs
Som Sahu
2016-02-23 17:37:23 -0800
77a8133acdraise a ConsumerRebalanceFinished event from ZKRebalancerListener after rebalance with owned partitions
Ducas Francis
2016-04-13 15:14:43 +1000
4ab7f2a444Update to use log4n 2.0.3 (also called 2.0.15). The current version used, 1.2.10, is not compatible with later versions of log4net.
Dave Tauzell
2016-04-08 13:47:45 -0500
186b9cd2c31) Fix log loss scenario during rebalance, 2) use api version 0 instead of 1, 3) Some minor performance improvement and bug fixes
Som Sahu
2016-04-04 11:22:21 -0700
1b84ef3c7aAdd factory method for parsers, clean up tests
Greg Fodor
2016-04-02 21:18:08 -0700
Ducas Francis
Christopher Andrews
Andrew Fenna
Karlen Simonyan
John Stark
Maxime Caron
Greg Fodor
Jordan Beacham
aakarshit
Soumyajit Sahu
Magnus Edenhill
Andy Fenna
Chris Andrews
YixuanLiu
Jordan Beacham
Razvan Iamandii
mhorstma
Ducas Francis
danielli90
Som Sahu
Razvan Iamandii
geoff tsai
jthelin
Emmanuel Payet
Alexandr Nikitin
AlgorithmsAreCool
hannakim123
The Gitter Badger
Dave Tauzell