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 

{
    if (force)
    {
        
        auto merge_blocker = stopMergesAndWait();
        auto part = getPartIfExists(part_name, {MergeTreeDataPartState::Committed});
        if (!part)
            throw Exception("Part " + part_name + " not found, won't try to drop it.", ErrorCodes::NO_SUCH_DATA_PART);
        removePartsFromWorkingSet({part}, true);
        return part;
    }
    else
    {
        
        std::unique_lock lock(currently_processing_in_background_mutex);
        auto part = getPartIfExists(part_name, {MergeTreeDataPartState::Committed});
        
        if (!part)
            return nullptr;
        
        
        if (currently_merging_mutating_parts.count(part))
            return nullptr;
        removePartsFromWorkingSet({part}, true);
        return part;
    }
}
void StorageMergeTree::dropPartNoWaitNoThrow(const String & part_name)