[ https://issues.apache.org/jira/browse/KAFKA-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated KAFKA-5946: -------------------------- Description: During the development of KAFKA-5657, there were several iterations where method call didn't match what the connector parameter actually represents. [~ewencp] had used connType as equivalent to connClass because Type wasn't used to differentiate source vs sink. [~ewencp] proposed the following: {code} It would help to convert all the uses of connType to connClass first, then standardize on class == java class, type == source/sink, name == user-specified name. {code} was: During the development of KAFKA-5657, there were several iterations where method call didn't match what the connector parameter actually represents. [~ewencp] had used connType as equivalent to connClass because Type wasn't used to differentiate source vs sink. [~ewencp] proposed the following: It would help to convert all the uses of connType to connClass first, then standardize on class == java class, type == source/sink, name == user-specified name. > Give connector method parameter better name > ------------------------------------------- > > Key: KAFKA-5946 > URL: https://issues.apache.org/jira/browse/KAFKA-5946 > Project: Kafka > Issue Type: Improvement > Reporter: Ted Yu > Priority: Major > Labels: connector > > During the development of KAFKA-5657, there were several iterations where > method call didn't match what the connector parameter actually represents. > [~ewencp] had used connType as equivalent to connClass because Type wasn't > used to differentiate source vs sink. > [~ewencp] proposed the following: > {code} > It would help to convert all the uses of connType to connClass first, then > standardize on class == java class, type == source/sink, name == > user-specified name. > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)