@@ -370,7 +370,7 @@ void SchemaBuilder<Getter, NameMapper>::applyDiff(const SchemaDiff & diff)
370370 {
371371 // >= SchemaActionType::MaxRecognizedType
372372 // log down the Int8 value directly
373- LOG_ERROR (log, " Unsupported change type: {}, diff_version={}" , fmt::underlying (diff.type ), diff.version );
373+ LOG_WARNING (log, " Unsupported change type: {}, diff_version={}" , fmt::underlying (diff.type ), diff.version );
374374 }
375375
376376 break ;
@@ -1138,7 +1138,7 @@ void SchemaBuilder<Getter, NameMapper>::applyCreateStorageInstance(
11381138 // Else the storage instance does not exist, create it.
11391139
11401140 // We need to create a Storage instance to handle its raft log and snapshot when it
1141- // is "dropped" but not physically removed in TiDB. To handle it porperly , we get a
1141+ // is "dropped" but not physically removed in TiDB. To handle it properly , we get a
11421142 // tso from PD to create the table. The tso must be newer than what "DROP TABLE" DDL
11431143 // is executed. So when the gc-safepoint is larger than tombstone_ts, the table can
11441144 // be safe to physically drop on TiFlash.
@@ -1434,7 +1434,7 @@ void SchemaBuilder<Getter, NameMapper>::syncAllSchema()
14341434 }
14351435 sync_all_schema_wait_group->wait ();
14361436
1437- // `applyRenameLogicalTable` is not atmoic when renaming a partitioned table
1437+ // `applyRenameLogicalTable` is not atomic when renaming a partitioned table
14381438 // to new database. There could be a chance that the logical table .sql have
14391439 // been moved to the new database while some partitions' sql are not moved.
14401440 // Try to detect such situation and fix it.
@@ -1526,7 +1526,7 @@ void SchemaBuilder<Getter, NameMapper>::tryFixPartitionsBelongingDatabase()
15261526 auto it = part_to_db_id.find (*opt_tbl_id);
15271527 if (it == part_to_db_id.end ())
15281528 {
1529- // this is not a physical_table_id of a partition, ignore sliently
1529+ // this is not a physical_table_id of a partition, ignore silently
15301530 continue ;
15311531 }
15321532 // Get the `new_database_id` from `table_id_map`
@@ -1769,8 +1769,8 @@ String SchemaBuilder<Getter, NameMapper>::tryGetDatabaseDisplayNameFromLocal(Dat
17691769{
17701770 // This method is called in the `applyDiff` loop. The `applyDiff` loop should apply the all the DDL operations before
17711771 // the database get dropped, so the database info should be cached in `databases`.
1772- // But for corner cases that the database is dropped on some unkonwn cases, we just return a display database name
1773- // according to the keyspace_id and database_id because display name ususally is not critical.
1772+ // But for corner cases that the database is dropped on some unknown cases, we just return a display database name
1773+ // according to the keyspace_id and database_id because display name usually is not critical.
17741774 if (auto new_db_info = databases.getDBInfo (database_id); likely (new_db_info != nullptr ))
17751775 {
17761776 return name_mapper.displayDatabaseName (*new_db_info);
0 commit comments