AddMigration doesn't create all indexes when using different filters or names

[cornem]

When you define multiple indexes for an entity over the same columns but with a different filter expression and/or name, EF will only create a migration statement for the last one.

Steps to reproduce

Create a project with this model:

public class State
{
    public Guid Id { get; set; }

    public DateTime LastModified { get; set; } = DateTime.UtcNow;

    public int? CustomerId { get; set; }

    public int? ItemId { get; set; }

    public int? ItemGroupId { get; set; }

    [Required, StringLength(450)]
    public string RemoteId { get; set; }
}

public class StateDbContext : DbContext
{
    public DbSet<State> State { get; set; }

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<State>(s =>
        {
            s.HasIndex("RemoteId")
                .HasFilter("CustomerId IS NOT NULL")
                .HasName("IX_State_RemoteId_CustomerId")
                .IsUnique();

            s.HasIndex("RemoteId")
                .HasFilter("ItemId IS NOT NULL")
                .HasName("IX_State_RemoteId_ItemId")
                .IsUnique();

            s.HasIndex("RemoteId")
                .HasFilter("ItemGroupId IS NOT NULL")
                .HasName("IX_State_RemoteId_ItemGroupId")
                .IsUnique();
        });
    }
}

• Notice that even though the index uses the same property RemoteId, the name and filter for each index is different (I can create such indexes on SQL server with T-SQL)
• Add a migration: dotnet ef migrations add CreateInitialSchema
• Notice that the generated migration only contains the index IX_State_RemoteId_ItemGroupId.

Further technical details

EF Core version: both 2.* and 3.0.0
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: netcoreapp2.2 / netcoreapp3.0
Operating system: Windows 10
IDE: N/A

[bricelam]

This is a limitation in our Fluent API. s.HasIndex("RemoteId") will get or add the single index covering that property. Subsequent calls to HasFilter and HasName are overriding the configuration for that index.

@AndriySvyryd Can you work around this by dropping down to Metadata? Do we have an issue on our backlog about addressing indexes by name in the fluent API?

[AndriySvyryd]

There is no way of doing this in Metadata.
Duplicate of #4150

[bricelam]

Note, you can manually add the indexes by adding calls to migrationBuilder.CreateIndex() inside a migration.