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 

ContextPtr query_context, const StorageMetadataPtr & metadata_snapshot, SelectQueryInfo & query_info) const
{
    const auto & settings = query_context->getSettingsRef();
    if (!settings.allow_experimental_projection_optimization || query_info.ignore_projections || query_info.is_projection_query)
        return std::nullopt;
    const auto & query_ptr = query_info.original_query;
    if (auto * select = query_ptr->as<ASTSelectQuery>(); select)
    {
        /
        if (select->final())
            return std::nullopt;
        /
        if (select->arrayJoinExpressionList().first)
            return std::nullopt;
    }
    /
    if (settings.parallel_replicas_count > 1)
        return std::nullopt;
    InterpreterSelectQuery select(
        query_ptr,
        query_context,
        SelectQueryOptions{QueryProcessingStage::WithMergeableState}.ignoreProjections().ignoreAlias(),
        query_info.sets /;
    const auto & analysis_result = select.getAnalysisResult();
    query_info.sets = std::move(select.getQueryAnalyzer()->getPreparedSets());
    bool can_use_aggregate_projection = true;