Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-11838] please ignore this PR #18275

Conversation

rmetzger
Copy link
Contributor

@rmetzger rmetzger commented Jan 5, 2022

This is for testing issues with CI

galenwarren and others added 27 commits January 5, 2022 09:16
Add new project for GS file system and recoverable writer. This includes FileSystemFactory SPI wireup, but with no recoverable writer (yet).
Add interfaces to abstract away direct access to the Google Storage API, both to simplify that access and to make it mockable.
…orage

Add GSBlobStorage, an implementation of BlobStorage against the Google Storage API.
Add some utility functions used by the recoverable writer. Includes unit tests.
Add MockBlobStorage, an implementation of BlobStorage against an in-memory store.
Implements RecoverableWriter against the BlobStorage abstraction and wires up HadoopFileSystem.createRecoverableWriter for GS. Includes unit tests.
Rename BlobStorage and GSBlobStorage to GSBlobStorage and GSBlobStorageImpl
Rename BlobStorage.write to BlobStorage#writeBlob
Remove ability to specify blob content type
Introduce GSBlobIdentifier abstraction
Remove BlobId normalization (no longer needed)
Move nested interfaces/classes to bottom
Add count<=32 precondition for GSBlobStorageImpl#compose
Other code improvements
…base classes for new scheme/project

Remove unnecessary config options
Better handle optional config options
Change WRITER_CHUNK_SIZE to use .memoryType() instead of .intType() and add check that value is multiple of 256KB
Make HadoopFileSystem and FileSystem aware of gs: scheme and flink-gs-fs-hadoop project
…ements

Refactor utilities
Validate gs scheme in parseUri
Remove GSRecoverableWriteState, replace with immutable GSResumeRecoverable and private state in GSRecoverableFsDataOutputStream
Fix commit, commitAfterRecovery, cleanupRecoverableState, and requiresCleanupOfRecoverableState to implement proper commit and cleanup algorithms
Exclude javax.annotation-api artifact because of its GPLv2 license, which cannot be included in Flink artifacts. Everything seems to build and run fine without it.
…w feedback

Remove unnecessary throw clauses
Inline call to preconditions.checkNotNull
Use unmodifiable list for component object ids in GSResumeRecoverable
Overload GSBlobStorage#writeBlob to allow setting chunk size, remove setChunkSize on GSBlobStorage#WriteChannel
…ing separating commit vs. resume recoverables

Separate commit vs. resume recoverables
Refactor utility functions
Add javadoc comments
@flinkbot
Copy link
Collaborator

flinkbot commented Jan 5, 2022

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@flinkbot
Copy link
Collaborator

flinkbot commented Jan 5, 2022

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit a659f92 (Wed Jan 05 20:27:53 UTC 2022)

Warnings:

  • 2 pom.xml files were touched: Check for build and licensing issues.
  • No documentation files were touched! Remember to keep the Flink docs up to date!

Mention the bot in a comment to re-run the automated checks.

Review Progress

  • ❓ 1. The [description] looks good.
  • ❓ 2. There is [consensus] that the contribution should go into to Flink.
  • ❓ 3. Needs [attention] from.
  • ❓ 4. The change fits into the overall [architecture].
  • ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.


The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

@rmetzger
Copy link
Contributor Author

rmetzger commented Jan 5, 2022

@zentol zentol closed this Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants