Skip to content

NIFI-15911 Add Web Client Service for Snowflake Ingest Service - #11369

Merged
pvillard31 merged 2 commits into
apache:mainfrom
exceptionfactory:NIFI-15911
Jun 25, 2026
Merged

NIFI-15911 Add Web Client Service for Snowflake Ingest Service#11369
pvillard31 merged 2 commits into
apache:mainfrom
exceptionfactory:NIFI-15911

Conversation

@exceptionfactory

Copy link
Copy Markdown
Contributor

Summary

NIFI-15911 Adds a Web Client Service Provider property to the StandardSnowflakeIngestManagerProviderService in order to support Proxy Servers and other configuration features for HTTP operations.

The additional property is required, and property migration methods add a default StandardWebClientServiceProvider implementation when the Snowflake Ingest Manager Provider Service does not have one configured. This enables upgrades to existing flows without requiring manual configuration.

The implementation changes replace direct use of the Java HttpClient with the equivalent WebClientService methods defined in the nifi-web-client-api module. Updated unit tests exercise the property migration behavior.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000
  • Pull request contains commits signed with a registered key indicating Verified status

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using ./mvnw clean install -P contrib-check
    • JDK 21
    • JDK 25

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

try {
return objectMapper.readValue(responseBodyStream, InsertReport.class);
} catch (final JsonProcessingException e) {
final byte[] responseBodyBytes = responseBodyStream.readAllBytes();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When readValue fails to parse, has the response stream already been consumed, so the body included in the error message would be empty?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, thanks! I pushed an update to read the response body as a string regardless of status code.

@pvillard31 pvillard31 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @exceptionfactory - LGTM

@pvillard31
pvillard31 merged commit af81f18 into apache:main Jun 25, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants