[FLINK-33465] Make SingleThreadFetcherManager and FutureCompletingBlockingQueue as PublicEvolving.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.18.0
• Component/s: Connectors / Parent
• Assignee: Unassigned
• Reporter: Hongshun Wang
• Created: 06/Nov/23 08:29
• Updated: 26/Jan/24 03:31
• Resolved: 26/Jan/24 03:27

Description

As discussed in FLINK-31324, though the SingleThreadFetcherManager is annotated as Internal, it actually acts as some-degree public API, which is widely used in many connector projects:
flink-cdc-connector, flink-connector-mongodb and so on.

More over, even the constructor of 
`SingleThreadMultiplexSourceReaderBase`  (which is PublicEvolving) includes the params of `SingleThreadFetcherManager`  and `FutureCompletingBlockingQueue` .That means that the `SingleThreadFetcherManager` and 
`FutureCompletingBlockingQueue`have already been exposed to users for a long time and are widely used.

 

public SingleThreadMultiplexSourceReaderBase(
    FutureCompletingBlockingQueue<RecordsWithSplitIds<E>> elementsQueue,
    SingleThreadFetcherManager<E, SplitT> splitFetcherManager,
    RecordEmitter<E, T, SplitStateT> recordEmitter,
    Configuration config,
    SourceReaderContext context)
{ super(elementsQueue, splitFetcherManager, recordEmitter, config, context); }
 

 
Therefore, why not make SingleThreadFetcherManager and FutureCompletingBlockingQueue PublicEvolving?

Issue Links

• duplicates: FLINK-34196 FLIP-389 Annotate SingleThreadFetcherManager as PublicEvolving.