i try to create Iceberg Destination using with hive meta store, but connection create fail with error

Could not connect to the Iceberg catalog with the provided configuration

Failed to create file: hdfs:xxxxx.. root cause: RemoteException(Permission denied:

i can define user connect with hive thrift urrl

Based on the information provided, it seems like the issue might be related to permissions. The error message

Could not connect to the Iceberg catalog with the provided configuration

and

Failed to create file: hdfs:xxxxx.. root cause: RemoteException(Permission denied:

indicates that the user or role you're using might not have the necessary permissions to access the Hive metastore or the HDFS file system. When setting up the Iceberg destination, you need to ensure that the

HiveCatalog

has the necessary permissions to connect to the Hive metastore and manage Iceberg tables. Similarly, for

HadoopCatalog

, it should have permissions to access HDFS or similar file systems that support atomic rename. Please check the permissions of the user or role you're using to connect to the Hive metastore and the HDFS file system. If necessary, grant the required permissions. For more information, you can refer to the [Iceberg documentation](https://docs.airbyte.com/integrations/destinations/iceberg) on Airbyte's website.

@kapa.ai can i define user via thrift url ?

Hmm, I don't know enough to give you a confident answer yet. The information extracts provided do not mention anything about defining a user via a Thrift URL in the context of Airbyte. However, you can define users in various ways depending on the source or destination you are working with. For example, for databases like [Postgres](https://docs.airbyte.com/integrations/destinations/postgres), [ClickHouse](https://docs.airbyte.com/integrations/sources/clickhouse), [Snowflake](https://docs.airbyte.com/integrations/sources/snowflake), and [Teradata](https://docs.airbyte.com/integrations/destinations/teradata), you can create a dedicated user with specific permissions. For more specific information, I would recommend checking the [Airbyte documentation](https://docs.airbyte.com/) or asking in the [Airbyte community](https://discuss.airbyte.io/).