Support access to s3 using an IDbroker (KNOX) provider

[exalate-issue-sync]

Users will be able to add an option {{-configure_s3_using_s3a}} that will automatically apply their S3A configuration to S3 configuration. This should resolve the primary issue of using IDbroker as a provider (would be used in environments where S3A is configured anyway).

[exalate-issue-sync]

Michal Kurka commented: [~accountid:5c355702a217aa69bce55831] the implementation included in H2O release 3.32.1.3 had a bug and h2odriver with option {{-configure_s3_using_s3a}} doesn’t work (you can specify the option but it won’t do anything).

The workaround is to pass the option directly to h2o-core:

{noformat}hadoop jar h2odriver.jar -n 1 -mapperXmx 10g -J -configure_s3_using_s3a{noformat}

(the trick is to add {{-J}} option)

This will be fixed in 3.32.1.4 but the -J trick will keep working.

[exalate-issue-sync]

Michal Kurka commented: Fixed here: [https://github.com//pull/5509|https://github.com//pull/5509|smart-link]

[h2o-ops]

JIRA Issue Details

Jira Issue: PUBDEV-8135
Assignee: Michal Kurka
Reporter: Joseph Granados
State: Closed
Fix Version: 3.36.0.1
Attachments: N/A
Development PRs: Available

[h2o-ops]

Linked PRs from JIRA

#5489
#5490
#5498
#5509