refactor: remove col_index_mapping when replacing table

[BugenZhao]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

#21499 eliminated the need for using ColIndexMapping for deriving the dispatcher after replacing a table. In last PR (#21681), we further eliminated the need for using it to rewrite the indexes. As a result, we can remove this field from the request of ReplaceTable now.

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• I have checked the Release Timeline and Currently Supported Versions to determine which release branches I need to cherry-pick this PR into.

Documentation

• My PR needs documentation updates.

Release note

[BugenZhao]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• refactor: remove col_index_mapping when replacing table #21685 👈 (View in Graphite)
• feat(meta): rewrite index after ALTER COLUMN TYPE #21681
• test: add tests for ALTER COLUMN TYPE with downstream jobs #21686
• feat(meta): consider types when resolve dispatcher output mapping  #21662
• feat(streaming): support mapping column type in dispatcher #21661
• feat(meta): enrich dispatcher output indices to support storing type mapping information #21645
• refactor(meta): avoid using frontend generated ColumnIndexMapping when constructing new dispatcher for replacement #21499
• feat(dashboard): display metadata for index itself besides index table #21680
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull Request Overview

This PR removes the now-unnecessary col_index_mapping parameter and related logic from table replacement handling. Key changes include removing the use of ColIndexMapping in multiple modules (RPC client, meta, and frontend) as well as updating proto definitions accordingly.

Reviewed Changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/rpc_client/src/meta_client.rs	Removed ColIndexMapping usage from replace_job and related calls
src/meta/src/rpc/ddl_controller.rs	Eliminated col_index_mapping parameter from job replacement API
src/meta/src/controller/streaming_job.rs	Removed col_index_mapping parameters in job finishing methods
src/meta/service/src/ddl_service.rs	Dropped col_index_mapping processing in extracting replace table info
src/frontend (various files)	Updated function signatures and calls to omit col_index_mapping
proto/ddl_service.proto	Removed table_col_index_mapping field from proto request messages

Comments suppressed due to low confidence (2)

src/rpc_client/src/meta_client.rs:642

• Since ColIndexMapping is no longer needed in the ReplaceJobPlanRequest, ensure that all internal and external documentation is updated to reflect that this parameter is removed.

table_col_index_mapping: ColIndexMapping,

proto/ddl_service.proto:372

• Remove or update comments referencing table_col_index_mapping so that the proto definition clearly reflects the new API without this field.

catalog.ColIndexMapping table_col_index_mapping = 2;