[fix](partition) Comment out some exceptions with partition equal to …#28702
[fix](partition) Comment out some exceptions with partition equal to …#28702yiguolei merged 2 commits intoapache:masterfrom
Conversation
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run buildall |
|
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
|
TeamCity be ut coverage result: |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
…0 and return In some scenarios, the partition id in the table meta is 0, but the rowset meta partition is not 0, (apache#28055) PR check partition id will caused be failed to start when upgrade meta like this ``` { "table_id": 1266302, "partition_id": 0, "tablet_id": 1289222, "schema_hash": 816078096, "shard_id": 949, "creation_time": 1684805433, "cumulative_layer_point": -1, "tablet_state": "PB_RUNNING", "schema": { "keys_type": "DUP_KEYS", "column": [ ... ], "num_short_key_columns": 1, "num_rows_per_row_block": 1024, ... "skip_write_index_on_load": false }, "rs_metas": [ { "rowset_id": 0, "partition_id": 1289193, "tablet_id": 1289222, "tablet_schema_hash": 816078096, "newest_write_timestamp": 1684805433, ... "segments_overlap_pb": "NONOVERLAPPING" } ], "in_restore_mode": false, "tablet_uid": { "hi": -4301918259617109775, "lo": 2820124814688031668 }, "preferred_rowset_type": "BETA_ROWSET", "tablet_type": "TABLET_TYPE_DISK", "replica_id": 1812028, "enable_unique_key_merge_on_write": false, "binlog_config": { "enable": false, "ttl_seconds": 9223372036854775807, "max_bytes": 9223372036854775807, "max_history_nums": 9223372036854775807 }, "compaction_policy": "size_based", "time_series_compaction_goal_size_mbytes": 1024, "time_series_compaction_file_count_threshold": 2000, "time_series_compaction_time_threshold_seconds": 3600 } ```
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
|
TPC-H test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
github-actions
bot
added
the
approved
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
apache#28702) * [fix](partition) Comment out some exceptions with partition equal to 0 and return In some scenarios, the partition id in the table meta is 0, but the rowset meta partition is not 0, (apache#28055) PR check partition id will caused be failed to start when upgrade meta like this ``` { "table_id": 1266302, "partition_id": 0, "tablet_id": 1289222, "schema_hash": 816078096, "shard_id": 949, "creation_time": 1684805433, "cumulative_layer_point": -1, "tablet_state": "PB_RUNNING", "schema": { "keys_type": "DUP_KEYS", "column": [ ... ], "num_short_key_columns": 1, "num_rows_per_row_block": 1024, ... "skip_write_index_on_load": false }, "rs_metas": [ { "rowset_id": 0, "partition_id": 1289193, "tablet_id": 1289222, "tablet_schema_hash": 816078096, "newest_write_timestamp": 1684805433, ... "segments_overlap_pb": "NONOVERLAPPING" } ], "in_restore_mode": false, "tablet_uid": { "hi": -4301918259617109775, "lo": 2820124814688031668 }, "preferred_rowset_type": "BETA_ROWSET", "tablet_type": "TABLET_TYPE_DISK", "replica_id": 1812028, "enable_unique_key_merge_on_write": false, "binlog_config": { "enable": false, "ttl_seconds": 9223372036854775807, "max_bytes": 9223372036854775807, "max_history_nums": 9223372036854775807 }, "compaction_policy": "size_based", "time_series_compaction_goal_size_mbytes": 1024, "time_series_compaction_file_count_threshold": 2000, "time_series_compaction_time_threshold_seconds": 3600 } ``` * fix
5 participants
…0 and return
In some scenarios, the partition id in the table meta is 0, but the rowset meta partition is not 0, (#28055) PR check partition id will caused be failed to start when upgrade
meta like this
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...