Closed OlivierZembri closed 4 months ago
@kristoffSC @grzegorz8 For enterprise usages, this is a critical need regarding data protection policy. Could you please review, and, if you'll agree with the PR, release a new version to include the new capability?
@OlivierZembri Thank you for this contribution, the time and effort you putted into it. I have merge it to master.
@kristoffSC Thanks a lot! Could you please release this (in 0.14.0)? Please don't wait for some other PR to be merged, we need this very urgently... cc @grzegorz8
@AdrianVasiliu Version is released but there was an issue with maven publish build. Some problems with java doc generation for new classes. I will take a look at it in evening.
@kristoffSC The release seems still unavailable in the maven repo. Can we hope for a short-term solution?
@AdrianVasiliu Hi, 0.14.0 went through, Should be available on maven. I also added https://github.com/getindata/flink-http-connector/pull/97 to that release
@kristoffSC Great, happy about both news, thanks a lot :-) I suppose the availability on maven will take a bit of more time (on maven repo side), for now the artifact isn't yet available.
@AdrianVasiliu I think it may be already available to download via maven (to use as dependency in the project) even though it is not visible on maven-central page.
I've noticed that there is usually around 1, 2 days of delay between publish and when side is updated.
It works now :-) All good, thanks!
The documentation related to Custom request/response callback states that the default SLF4J logger can be overridden by a custom implementation for HttpSink.
There is no such mechanism in place to override the default SLF4J logger for used for HTTP lookup source connector.
This mechanism would be quite useful to change the verbosity of the message and the level at which they are logged thereby avoiding leak of sensible information conveyed by processed events for example.