ferenc-csaky commented on code in PR #42: URL: https://github.com/apache/flink-connector-http/pull/42#discussion_r3259579262
########## docs/content.zh/docs/connectors/table/http.md: ########## @@ -87,12 +87,12 @@ The Flink connector does have some changes that you need to be aware of if you a * Existing java applications will need to be recompiled to pick up the new flink package names. * Existing application and SQL need to be amended to use the new connector option names. The new option names do not have - the _com.getindata.http_ prefix, the prefix is now _http_. +the _com.getindata.http_ prefix, the prefix is now _http_. * The name of the connector and the identifiers of components that are discovered have been changed, so that the GetInData jar file can co-exist - with this connector's jar file. Be aware that if you have created custom pluggable components; you will need to recompile against this connector. -* Note that the `http-generic-json-url` query creator now processes HTTP bodies differently using `http.request.body-template`. -* Note that if you were incorrectly using `gid.connector.http.request.query-param-fields` with POST or PUT did not give an error. This connector corrects the behaviour so specifying `http.request.query-param-fields` with POST or PUT does give an error. -* The GetInData HTTP connector was built against Flink version 1, so works with that level of Flink and also Flink version 2. This connector is built against and supports Flink 2.2. +with this connector's jar file. Be aware that if you have created custom pluggable components; you will need to recompile against this connector. +* Note that the `http-generic-json-url` query creator now processes HTTP bodies differently using `http.request.body-template`. Review Comment: Can we eliminate trailing whitespaces in both `http.md` on any line that may be affected? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
