Enum MetaCommands 

pub(crate) enum MetaCommands {
    Pause,
    Resume,
    ResumeBackfill {
        job_id: Option<JobId>,
        fragment_id: Option<FragmentId>,
    },
    ClusterInfo,
    SourceSplitInfo {
        ignore_id: bool,
    },
    Reschedule {
        plan: Option<String>,
        revision: Option<u64>,
        from: Option<String>,
        dry_run: bool,
        resolve_no_shuffle: bool,
    },
    BackupMeta {
        remarks: Option<String>,
    },
    RestoreMeta {
        opts: RestoreOpts,
    },
    DeleteMetaSnapshots {
        snapshot_ids: Vec<u64>,
    },
    ListConnections,
    ListServingFragmentMapping,
    UnregisterWorkers {
        workers: Vec<String>,
        yes: bool,
        ignore_not_found: bool,
        check_fragment_occupied: bool,
    },
    ValidateSource {
        props: String,
    },
    SetCdcTableBackfillParallelism {
        table_id: u32,
        parallelism: u32,
    },
    AlterSourcePropertiesSafe {
        source_id: u32,
        props: String,
        reset_splits: bool,
    },
    ResetSourceSplits {
        source_id: u32,
    },
    InjectSourceOffsets {
        source_id: u32,
        offsets: String,
    },
}

Variants

Pause

pause the stream graph

Resume

resume the stream graph

ResumeBackfill

force resume backfill for troubleshooting

Fields

job_id: Option<JobId>

fragment_id: Option<FragmentId>

ClusterInfo

get cluster info

SourceSplitInfo

get source split info

Fields

ignore_id: bool

Reschedule

Reschedule the actors in the stream graph

The format is fragment_id-[worker_id:count]+[worker_id:count] You can provide either decreased worker_ids only or increased only, but decreased should be preceded by added when both are provided.

For example, for plan 100-[1:1]+[4:1] the follow request will be generated:

{
    100: WorkerReschedule {
        increased_actor_count: { 1: 1 },
        decreased_actor_count: { 4: 1 },
    }
}

Use ; to separate multiple fragment

Fields

plan: Option<String>

Plan of reschedule, needs to be used with revision

revision: Option<u64>

Revision of the plan

from: Option<String>

Reschedule from a specific file

dry_run: bool

Show the plan only, no actual operation

resolve_no_shuffle: bool

Resolve NO_SHUFFLE upstream

BackupMeta

backup meta by taking a meta snapshot

Fields

remarks: Option<String>

RestoreMeta

restore meta by recovering from a meta snapshot

Fields

opts: RestoreOpts

DeleteMetaSnapshots

delete meta snapshots

Fields

snapshot_ids: Vec<u64>

ListConnections

List all existing connections in the catalog

ListServingFragmentMapping

List fragment mapping for serving

UnregisterWorkers

Unregister workers from the cluster

Fields

workers: Vec<String>

The workers that needs to be unregistered, worker_id and worker_host:worker_port are both supported

yes: bool

Automatic yes to prompts

ignore_not_found: bool

The worker not found will be ignored

check_fragment_occupied: bool

Checking whether the fragment is occupied by workers

ValidateSource

Validate source interface for the cloud team

Fields

props: String

With properties in json format If privatelink is used, specify connection.id instead of connection.name

SetCdcTableBackfillParallelism

Fields

table_id: u32

parallelism: u32

AlterSourcePropertiesSafe

Alter source connector properties with pause/resume orchestration (UNSAFE) This operation pauses the source, updates properties, and resumes.

Fields

source_id: u32

Source ID to update

props: String

Properties to change in JSON format, e.g. ‘{“properties.bootstrap.server”: “new-broker:9092”}’

reset_splits: bool

Reset split assignments after property change (for major upstream changes)

ResetSourceSplits

Reset source split assignments (UNSAFE - admin only) Clears cached split state and triggers re-discovery from upstream.

Fields

source_id: u32

Source ID to reset

InjectSourceOffsets

Inject specific offsets into source splits (UNSAFE - admin only) WARNING: This can cause data duplication or loss!

Fields

source_id: u32

Source ID to inject offsets for

offsets: String

Split offsets in JSON format, e.g. ‘{“split-0”: “100”, “split-1”: “200”}’

Trait Implementations

impl FromArgMatches for MetaCommands

fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>

Instantiate Self from [ArgMatches], parsing the arguments as needed.

fn from_arg_matches_mut( __clap_arg_matches: &mut ArgMatches, ) -> Result<Self, Error>

Instantiate Self from [ArgMatches], parsing the arguments as needed.

fn update_from_arg_matches( &mut self, __clap_arg_matches: &ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

fn update_from_arg_matches_mut<'b>( &mut self, __clap_arg_matches: &mut ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

impl Subcommand for MetaCommands

fn augment_subcommands<'b>(__clap_app: Command) -> Command

Append to [Command] so it can instantiate Self via [FromArgMatches::from_arg_matches_mut]

fn augment_subcommands_for_update<'b>(__clap_app: Command) -> Command

Append to [Command] so it can instantiate self via [FromArgMatches::update_from_arg_matches_mut]

fn has_subcommand(__clap_name: &str) -> bool

Test whether Self can parse a specific subcommand