I think the intent was for this to happen through API integration. What is the user interaction that you're trying to achieve? Do you want each `CREATE VIEW` call to automatically append a new representation?
On Fri, Sep 4, 2026 at 2:32 PM Alex Stephen via dev <[email protected]> wrote: > Hello, > > The view spec allows creating a single view with multiple engine-specific > representations. This allows a single view to be queried by multiple > engines, each using its own specific SQL dialect. > > In practice, this is difficult to achieve. Users can use the > `replace.drop-dialect.allowed` view property to allow the replacing of an > existing representation. However, there's no way to append a representation > (by creating a new ViewVersion with the existing representations and a new > one). This means that a direct REST API call is the only way to create a > View with multiple representations. > > I'd like to propose the creation of a new view property called > `replace.append-dialect.allowed` that allows users to append a new > representation to an existing view. > > PR: https://github.com/apache/iceberg/pull/17930 > > Please take a look. I'd love to hear from the community whether there is > value in this use case. > > Thanks! > > -- Alex Stephen >
