We found the issue during autocreation of iceberg tables using HIVE catalog.
In the config we are passing the warehouse location as s3://bucket/table but in the table metastore we can see that the location is being stored as s3://bucket//table/metadata (example : s3://[bucket_name]//iceberg_sink_test_11/ where as it should be just as s3://[bucket_name]/iceberg_sink_test_11/ ).
Hence when we checked, we were able to find all the files in the / folder in s3.
Can you tell us what should we use so that we don't see all the files being populated in the / folder, this causes an issue as we are not able to query the table with the files at the wrong location.
This is the current connector config we are using.
We found the issue during autocreation of iceberg tables using HIVE catalog.
In the config we are passing the warehouse location as
s3://bucket/table
but in the table metastore we can see that the location is being stored ass3://bucket//table/metadata
(example :s3://[bucket_name]//iceberg_sink_test_11/
where as it should be just ass3://[bucket_name]/iceberg_sink_test_11/
).Hence when we checked, we were able to find all the files in the
/
folder in s3.Can you tell us what should we use so that we don't see all the files being populated in the
/
folder, this causes an issue as we are not able to query the table with the files at the wrong location.This is the current connector config we are using.