Skip to content

Conversation

@Buktoria
Copy link
Contributor

Adding missing documentation to the open-api spec for LoadTableResult configs for FileIO implementations GCS and ADLS.

@Buktoria Buktoria force-pushed the spec/document-gcs-and-adls-fileio-config branch 2 times, most recently from 0705115 to 67fc2f1 Compare June 27, 2024 22:07
@Buktoria Buktoria force-pushed the spec/document-gcs-and-adls-fileio-config branch from 67fc2f1 to 1ec8ead Compare June 27, 2024 22:08
Buktoria and others added 2 commits June 27, 2024 19:02
Co-authored-by: Marc Cenac <547446+mrcnc@users.noreply.github.com>
- `s3.access-key-id`: id for for credentials that provide access to the data in S3
- `s3.secret-access-key`: secret for credentials that provide access to data in S3
- `s3.session-token`: if present, this value should be used for as the session token
- `s3.remote-signing-enabled`: if `true` remote signing should be performed as described in the `s3-signer-open-api.yaml` specification

Choose a reason for hiding this comment

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

can we also add a key for expiration time for aws sts token ?

Copy link
Contributor

Choose a reason for hiding this comment

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

@stirupati I would suggest splitting that out in a separate PR, so we can purely focus on GCS/ADLS for this PR.

Copy link
Contributor

Choose a reason for hiding this comment

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

@Fokko created separate PR for the same #10873

- `gcs.oauth2.token`: String representation of the access token used for temporary access.
- `gcs.oauth2.token-expires-at`: A LONG that represents the date in Epoch milliseconds of when the token expires.
- `gcs.no-auth`: Boolean to explicitly configure "no authentication" for testing purposes using a GCS emulator
- `gcs.delete.batch-size`: Optional INT that configures the batch size used when deleting multiple files from a given GCS bucket. Defaults to 50.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we only limit this to configuration related to authentication? This is the case of AWS as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We could, but I would argue that we would still want those other configs documented in the spec somewhere for constancy sake for those working on their own FileIO implementations or Iceberg REST catalog implementations.

If we limit what is documented in this section to auth, where do you propose we put other config that could be returned?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Any thoughts on the above @Fokko?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hey @Buktoria Thanks for pinging me.

I think the more appropriate place is to have it under the GcsFileIO, similar to the S3FileIO.

@github-actions
Copy link

github-actions bot commented Nov 8, 2024

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Nov 8, 2024
@github-actions
Copy link

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@github-actions github-actions bot closed this Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants