Prisma views (for MongoDB) with composite types causes Engine Panic

view ZohoUser {
  id              String    @map("_id") @db.ObjectId
  zohoId          String
  sub             String?
  email           String
  emailVerified   DateTime?
  isEmailVerified Boolean   @default(false)
  name            String
  firstName       String?
  lastName        String?
  createdAt       DateTime @default(now())
  updatedAt       DateTime @updatedAt

  @@map("zoho-users")
}

view DealPhoto {
  id          String           @map("_id") @db.ObjectId
  blobName    String
  dealId      String
  createdById String?
  createdAt   DateTime
  updatedAt   DateTime
  revision    Int
  config      PhotoConfig
  drawing     DealPhotoDrawing
  rank        Int?
  source      PhotoSource?

  @@map("deal-photos")
}

enum PhotoSource {
  PARTNER
  MANUAL
  ZOHO
}

type DealPhotoDrawing {
  version String
  objects Json[]
}

type PhotoConfig {
  labels PhotoLabel[] @default([])
  note   String       @default("")
}

enum PhotoLabel {
  LABEL_ONE
  ...
}

thread 'tokio-runtime-worker' panicked at query-engine/query-structure/src/field/scalar.rs:96:17:
internal error: entered unreachable code: This shouldn't be reached; composite types are not supported in compound unique indices.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
PrismaClientRustPanicError: 
Invalid `prisma.dealPhoto.findMany()` invocation:


internal error: entered unreachable code: This shouldn't be reached; composite types are not supported in compound unique indices.

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.