[jira] [Created] (KAFKA-1234) All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS)
Alex Gray created KAFKA-1234: Summary: All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS) Key: KAFKA-1234 URL: https://issues.apache.org/jira/browse/KAFKA-1234 Project: Kafka Issue Type: Improvement Components: config Affects Versions: 0.8.0 Reporter: Alex Gray Priority: Trivial We are using the distributed version of kafka: http://apache.mirrors.lucidnetworks.net/kafka/0.8.0/kafka_2.8.0-0.8.0.tar.gz And we would like to set some environment variables, particularly KAFKA_OPTS when the kafka service starts. In other words, when someone does a sudo service kafka start we would like to set some environment variables. We cannot do this *without* modifying either /etc/init.d/kafka or bin/kafka-run-class.sh, and we don't want to modify files that we don't own. The solution is to have kafka source in a user specific file that may have these environment variables set. I'm attaching the patch file to show you what I mean. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (KAFKA-1234) All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS)
[ https://issues.apache.org/jira/browse/KAFKA-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Gray updated KAFKA-1234: - Attachment: patch.txt Attaching patch file (I wasn't sure if I should attach the patch file or to put the contents of the patch file in the JIRA itself.) All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS) -- Key: KAFKA-1234 URL: https://issues.apache.org/jira/browse/KAFKA-1234 Project: Kafka Issue Type: Improvement Components: config Affects Versions: 0.8.0 Reporter: Alex Gray Priority: Trivial Attachments: patch.txt We are using the distributed version of kafka: http://apache.mirrors.lucidnetworks.net/kafka/0.8.0/kafka_2.8.0-0.8.0.tar.gz And we would like to set some environment variables, particularly KAFKA_OPTS when the kafka service starts. In other words, when someone does a sudo service kafka start we would like to set some environment variables. We cannot do this *without* modifying either /etc/init.d/kafka or bin/kafka-run-class.sh, and we don't want to modify files that we don't own. The solution is to have kafka source in a user specific file that may have these environment variables set. I'm attaching the patch file to show you what I mean. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (KAFKA-1234) All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS)
[ https://issues.apache.org/jira/browse/KAFKA-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13888339#comment-13888339 ] Alex Gray commented on KAFKA-1234: -- True, but the problem is that I don't want to set system wide env vars; I only want to set it for the specific service that I run. The service command strips out all environment variables (at least on centos or AWS OS), so unless the init.d file is sourcing in something, I don't think I can set those env vars... they will just get stripped out. Here is an explanation of the service command stripping out env vars: http://serverfault.com/questions/374404/service-command-and-environment-variables I haven't tried setting the vars in /etc/default, but I will try tomorrow. All kafka-run-class.sh to source in user config file (to set env vars like KAFKA_OPTS) -- Key: KAFKA-1234 URL: https://issues.apache.org/jira/browse/KAFKA-1234 Project: Kafka Issue Type: Improvement Components: config Affects Versions: 0.8.0 Reporter: Alex Gray Priority: Trivial Attachments: patch.txt We are using the distributed version of kafka: http://apache.mirrors.lucidnetworks.net/kafka/0.8.0/kafka_2.8.0-0.8.0.tar.gz And we would like to set some environment variables, particularly KAFKA_OPTS when the kafka service starts. In other words, when someone does a sudo service kafka start we would like to set some environment variables. We cannot do this *without* modifying either /etc/init.d/kafka or bin/kafka-run-class.sh, and we don't want to modify files that we don't own. The solution is to have kafka source in a user specific file that may have these environment variables set. I'm attaching the patch file to show you what I mean. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven repository
[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644742#comment-13644742 ] Alex Gray commented on KAFKA-133: - Silly question, but I just downloaded 0.8 branch and I see no pom.xml. I would like to locally build kafka and publish to our private local maven repo. Is this currently possible? Do I have to do something for the pom.xml to get generated. Sorry for the newbie question. I noticed that when I run ./sbt publish-local, the artifacts get pushed to my local repo: ~/.ivy2/local/org.apache/contrib_2.8.0 ~/.ivy2/local/org.apache/kafka_2.8.0 I would like to publish to our private local maven repo (which just so happens to be in S3), but I'm used to modifying a pom.xml to add the required plugins/repoID's/etc/etc/, hence the question on where the pom.xml is. Thanks! Publish kafka jar to a public maven repository -- Key: KAFKA-133 URL: https://issues.apache.org/jira/browse/KAFKA-133 Project: Kafka Issue Type: Improvement Affects Versions: 0.6, 0.8 Reporter: Neha Narkhede Labels: patch Fix For: 0.8 Attachments: KAFKA-133.patch, pom.xml The released kafka jar must be download manually and then deploy to a private repository before they can be used by a developer using maven2. Similar to other Apache projects, it will be nice to have a way to publish Kafka releases to a public maven repo. In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo, but ran into some authentication problems. It will be good to revisit this and get it resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven repository
[
https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645131#comment-13645131
]
Alex Gray commented on KAFKA-133:
-
Thanks Scott, for the links. Just searching for sbt s3 does not get too many
hits, but the best one by far is:
http://stackoverflow.com/questions/9958103/how-to-publish-to-amazon-s3-with-sbt
So far, from what I can tell, either copy the ivy jar and do the following (the
million dollar question is how to configure the setters):
{
val s3r = new org.springframework.aws.ivy.S3Resolver
// call its setters to configure it, see api docs above etc.
publishTo := Some(new sbt.RawRepository(s3r)
}
or use sbt-s3, which I haven't had any success in.
Nonetheless, I think I have enough to experiment with.
Thanks!
Publish kafka jar to a public maven repository
--
Key: KAFKA-133
URL: https://issues.apache.org/jira/browse/KAFKA-133
Project: Kafka
Issue Type: Improvement
Affects Versions: 0.6, 0.8
Reporter: Neha Narkhede
Labels: patch
Fix For: 0.8
Attachments: KAFKA-133.patch, pom.xml
The released kafka jar must be download manually and then deploy to a private
repository before they can be used by a developer using maven2.
Similar to other Apache projects, it will be nice to have a way to publish
Kafka releases to a public maven repo.
In the past, we gave it a try using sbt publish to Sonatype Nexus maven repo,
but ran into some authentication problems. It will be good to revisit this
and get it resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
