[ https://issues.apache.org/jira/browse/KAFKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481865#comment-14481865 ]
Rekha Joshi commented on KAFKA-1621: ------------------------------------ Hi.missed updating earlier. everything else was setup as https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review but the jira-client could not be installed (Mac 10.9.5, Python 2.7.5, pip 1.5.6), hence could not update review board. suggestion: why not review directly on git as rest of the apache projects? python kafka-patch-review.py --help Traceback (most recent call last): File "kafka-patch-review.py", line 10, in <module> from jira.client import JIRA ImportError: No module named jira.client pip install jira-python Downloading/unpacking jira-python Could not find any downloads that satisfy the requirement jira-python Cleaning up... No distributions at all found for jira-python Storing debug log for failure in /usr/local/.pip/pip.log sudo easy_install jira-python Searching for jira-python Reading http://pypi.python.org/simple/jira-python/ Couldn't find index page for 'jira-python' (maybe misspelled?) Scanning index of all packages (this may take a while) Reading http://pypi.python.org/simple/ No local packages or download links found for jira-python error: Could not find suitable distribution for Requirement.parse('jira-python') Think it could be related to security enabled on pip?, but I would prefer not to downgrade pip as used for my other projects as well. > Standardize --messages option in perf scripts > --------------------------------------------- > > Key: KAFKA-1621 > URL: https://issues.apache.org/jira/browse/KAFKA-1621 > Project: Kafka > Issue Type: Bug > Affects Versions: 0.8.1.1 > Reporter: Jay Kreps > Labels: newbie > > This option is specified in PerfConfig and is used by the producer, consumer > and simple consumer perf commands. The docstring on the argument does not > list it as required but the producer performance test requires it--others > don't. > We should standardize this so that either all the commands require the option > and it is marked as required in the docstring or none of them list it as > required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)