JingsongLi opened a new pull request #18114:
URL: https://github.com/apache/flink/pull/18114
## What is the purpose of the change
Introduce `CatalogLock` for connectors, source & sink can use this lock to
do some global sync.
```
/**
* An interface that allows source and sink to use global lock to some
transaction-related things.
*/
@Internal
public interface CatalogLock extends Closeable {
/** Run with catalog lock. The caller should tell catalog the database
and table name. */
<T> T runWithLock(String database, String table, Callable<T> callable)
throws Exception;
/** Factory to create {@link CatalogLock}. */
interface Factory extends Serializable {
CatalogLock create();
}
}
```
And we need a interface to set lock to source&sink by catalog:
```
/**
* Source and sink implement this interface if they require {@link
CatalogLock}.
*/
@Internal
public interface RequireCatalogLock {
void setLockFactory(CatalogLock.Factory lockFactory);
}
```
## Brief change log
- Introduce `CatalogLock` and `RequireCatalogLock`
- Implement `HiveCatalogLock`
## Verifying this change
`HiveRunnerITCase.testCatalogLock`
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / **no** / don't
know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (**yes** / no)
- If yes, how is the feature documented? (not applicable / docs /
**JavaDocs** / not documented)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
