Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upKafka 0.10 support #282
Kafka 0.10 support #282
Conversation
yahoocla
commented
Aug 17, 2016
|
Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! |
yahoocla
commented
Aug 17, 2016
|
CLA is valid! |
mckn
commented
Sep 6, 2016
|
To start, good work with this project! Any plans on when this pull request will be accepted into master? |
magaton
commented
Sep 15, 2016
|
Hello, could you please tell when this will be merged. We are going with 0.10.0.1 in prod very soon and we desperately need a good monitoring tool. Thank you. |
chrisfabri
commented
Sep 16, 2016
|
dido |
bai
commented
Sep 16, 2016
|
Hey folks — any chance on getting this merged sometime soon? And thanks @tqh for pushing this, really helpful. |
davemcphee
commented
Sep 16, 2016
•
|
Just FYI, I've been running this pull in prod for 2 weeks now with great success. Until it's merged:
many thanks to @tqh ! |
| @@ -295,7 +295,7 @@ case class KafkaManagedOffsetCache(clusterContext: ClusterContext | |||
| lastUpdateTimeMillis = System.currentTimeMillis() | |||
| } catch { | |||
| case e: Exception => | |||
| warn("Failed to process a message from offset topic!", e) | |||
| warn(s"Failed to process a message from offset topic on cluster ${clusterContext.config.name}!", e) | |||
This comment has been minimized.
This comment has been minimized.
whithajess
Sep 18, 2016
•
Generally wouldn't look for something in a Exception case as it may not exist so maybe the ${clusterContext.config.name} should be removed
This comment has been minimized.
This comment has been minimized.
tqh
Sep 19, 2016
Author
Contributor
It already proved very convenient to me. Why do you want to hide helpful information?
This comment has been minimized.
This comment has been minimized.
whithajess
Sep 19, 2016
Do not want to hide it, but if you access a variable that doesn't exist in the Exception case then what will catch that exception?
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
kalibyrn
Oct 18, 2016
@whithajess, in general, you have a point that if a variable is undefined in a catch, then there's no point in catching the first exception if we just generate another one anyway. However, in this case ${clusterContext.config.name} is already used on line 242, and everything is wrapped in a try anyway. This change wouldn't be executed if ${clusterContext.config.name} wasn't defined.
whithajess left a comment
|
Maybe some of these changes are just to do with the libraries, but it does look like this change would break a lot of backwards compatibilities. Was this tested with anything but 0.10? |
| @@ -35,7 +35,7 @@ libraryDependencies ++= Seq( | |||
| "org.slf4j" % "log4j-over-slf4j" % "1.7.12", | |||
| "com.adrianhurt" %% "play-bootstrap3" % "0.4.5-P24", | |||
| "org.clapper" %% "grizzled-slf4j" % "1.0.2", | |||
| "org.apache.kafka" %% "kafka" % "0.9.0.1" exclude("log4j","log4j") exclude("org.slf4j", "slf4j-log4j12") force(), | |||
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
tqh
Sep 19, 2016
Author
Contributor
Kafka client is backwards complient with 0.9. Havn't checked for older versions. Tested with a 0.9 cluster.
|
|
||
| def send(message: String, partition: String = null): Unit = send(message.getBytes("UTF8"), if (partition == null) null else partition.getBytes("UTF8")) |
This comment has been minimized.
This comment has been minimized.
whithajess
Sep 18, 2016
again this else partition.getBytes("UTF8") removal looks like it would break backwards compatibility
This comment has been minimized.
This comment has been minimized.
r8o
commented
Sep 19, 2016
|
Lotlir On Wed, Aug 17, 2016, 1:43 PM Yahoo CLA Bot notifications@github.com
|
rosscdh
commented
Sep 23, 2016
|
+1 merge |
deepshikhagandhi
commented
Sep 23, 2016
|
+1 please merge |
vgrivel
commented
Sep 27, 2016
|
I'm also waiting for the merge |
JordyMoos
commented
Sep 30, 2016
•
|
Is there any progress on this PR? |
salyh
commented
Oct 5, 2016
|
I can confirm that this PR works great with Kafka 0.10. We use since two weeks now without any problems. |
salyh
commented
Oct 5, 2016
|
+1 please merge |
kevinleeTCA
commented
Oct 6, 2016
|
+1 nice work |
magaton
commented
Oct 13, 2016
|
please... |
|
I can confirm works with 0.10, but I had trouble on a 0.8.2 cluster using this version... It accepts the configuration but it doesn't see any broker in my cluster. Anyone tested against other versions? |
junkiebev
commented
Oct 21, 2016
|
+1 please |
antkudr
commented
Dec 22, 2016
|
+1 |
1 similar comment
mikhailmulyar
commented
Dec 22, 2016
|
+1 |
lpicanco
commented
Dec 23, 2016
|
Can someone merge? |
zhan-yl
commented
Dec 26, 2016
|
+1 please merge |
hubian
commented
Dec 28, 2016
|
please merge+1 |
Renkai
commented
Jan 4, 2017
|
please merge +1 |
techwhizbang
commented
Jan 4, 2017
|
if I'm reading correctly the reason it hasn't been merged is b/c of the Yahoo CLA agreement not being signed. did the author of this PR already sign it? @tqh? |
|
@techwhizbang You are not reading it correctly. I signed ages ago. It's because Yahoo still uses older Kafka from what I understand. The 'all checks have passed' has a check for CLA. |
shemeemsp7
commented
Jan 6, 2017
•
|
please merge |
hgfischer
commented
Jan 9, 2017
|
+ |
yanspirit
commented
Jan 17, 2017
|
please merge+1 |
1 similar comment
arisu1000
commented
Jan 17, 2017
|
please merge+1 |
sainat
commented
Jan 19, 2017
|
+1 |
massimodeluisa
commented
Jan 20, 2017
|
+1 please merge |
natewarr
commented
Jan 23, 2017
|
Has anyone tried this on 10.1.1? |
|
Anyone tried this on 0.8.x, 0.9.x to check backwards compatibility? |
|
I checked on Oct 18, 2016, and at least with 0.8.2 it doesn't work. I can have a look with current status but only with 0.8.2 cluster. In a couple of hours I'll say something |
sainat
commented
Jan 24, 2017
•
|
@natewarr I tested this branch on a single node kafka 0.10.1.1 broker. Set kafka version to 0.10.1.0, no issues so far. I am going to deploy a multi broker 0.10.1.1 cluster pretty soon, will keep you posted on how it goes. It works with 0.9.0.1 (multi broker and single broker cluster). |
|
Sorry for the delay, I had some fires and I didn't have time to check it until now. @patelh I can confirm It works on a 0.8.2 cluster. |
gumartinm
commented
Jan 27, 2017
•
|
@natewarr It also works on 0.10.1.1. |
rmangi
commented
Feb 8, 2017
|
Would love to have this merged in |
ackramer
commented
Feb 8, 2017
|
+1 yes please |
khou
commented
Feb 20, 2017
|
|
|
Are we okay to merge this? |
tqh commentedAug 17, 2016
Our changes to work with Kafka 0.10. It's not well tested, but seems to work ok.
Not tested at all is:
This is just to get the ball rolling...