I am reading clickhouse mutation code. In StorageMergeTree->selectPartsToMutate() function, there is a check 
`if (current_ast_elements + commands_size >= max_ast_elements)
                break;`

I think if there are many mutations then the check result will be true, so that it will skip the remaining mutations.
But the new part's mutation is set to the last one in mutation map, and it does not apply the remaining mutations actually.
`new_part_info.mutation = current_mutations_by_version.rbegin()->first;`

Then the new part will miss the remaining mutations in future mutation job.

I think it's wrong here. Am I right?

If it is right, I will submit a PR 

size_t clearOldTemporaryDirectories(const MergeTreeDataMergerMutator & merger_mutator, size_t custom_directories_lifetime_seconds);
    size_t clearEmptyParts();
    
    
    void dropAllData();
    
    void dropIfEmpty();
    
    
    
    void rename(const String & new_table_path, const StorageID & new_table_id) override;
    
    
    
    
    
    void checkAlterIsPossible(const AlterCommands & commands, ContextPtr context) const override;
    
    
    void checkMutationIsPossible(const MutationCommands & commands, const Settings & settings) const override;
    
    void checkAlterPartitionIsPossible(const PartitionCommands & commands, const StorageMetadataPtr & metadata_snapshot, const Settings & settings) const override;
    
    void changeSettings(
        const ASTPtr & new_settings,
        AlterLockHolder & table_lock_holder);
    
    void reportBrokenPart(const String & name) const