Hi Connor, Unfortunately, the wiki has a separate user list from the Jira project. You’ll have to create a user in the wiki and then let us know the I’d so we can give you edit permission (so you can create the KIP).
Thanks! -John On Tue, Mar 31, 2020, at 13:38, Connor Penhale wrote: > Hi Chris, > > No problem! My customer understands they need to push their Kafka > release up to current ASAP, but they need to know which release they'd > be likely targeting to have this kind of feature. I'll go through the > KIP process and submit that. Should I use this as an opportunity now to > ask for permission to "Create KIP" in JIRA? My user ID is the email I > submitted the Improvement with. > > Thanks again! > Connor > > On 3/31/20, 12:30 PM, "Christopher Egerton" <chr...@confluent.io> wrote: > > Hi Connor, > > Thanks for the contribution! It looks like the feature you've > implemented > changes public interface, which means that a KIP would be required > in order > to merge them into Kafka. You can find more information about what > kinds of > changes require KIPs, what a KIP should consist of, and the process > for > creating one at > > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals > . > > Additionally, if the changes constitute a feature addition (which it > appears yours do), they're generally not applicable for backporting, and > should therefore be targeted against the latest branch of Kafka (i.e., > trunk) and will only be viable for inclusion in future releases. The > earliest possible release that such changes could be included in would be > 2.6, since the KIP deadline has already passed for the upcoming 2.5 > release. > > Hope this helps! > > Cheers, > > Chris > > On Tue, Mar 31, 2020 at 11:12 AM Connor Penhale <cpenh...@perforce.com> > wrote: > > > Hi Everyone! > > > > I’ve submitted a contribution for suppressing detailed exception > messages > > from Kafka Connect here: > https://issues.apache.org/jira/browse/KAFKA-9766, > > with a pull request here: https://github.com/apache/kafka/pull/8355. I > > was hoping to get some feedback on the code, and see if there’s > anything I > > can do to help this feature become part of Kafka! We have a customer > that > > really wants this feature, because their security team for PCI-DSS is > > unhappy with how Kafka Connect handles things like malformed JSON, as an > > example. Eager to work with everyone! > > > > Thanks! > > Connor > > > > Connor Penhale | Enterprise Architect, OpenLogic > (https://openlogic.com/) > > Perforce (https://www.perforce.com/) > > Support: +1 866.399.6736 > > > > > > > > This e-mail may contain information that is privileged or confidential. > If > > you are not the intended recipient, please delete the e-mail and any > > attachments and notify us immediately. > > > > > > > CAUTION: This email originated from outside of the organization. Do > not click on links or open attachments unless you recognize the sender > and know the content is safe. > > > > This e-mail may contain information that is privileged or confidential. > If you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > >
