Hi Hive team, I'm encountering an issue where Hive Metastore (HMS), running as a Spark sidecar container, is attempting to read/write to S3 even though it's only being used as a metastore. Since HMS is solely functioning as a metadata service in this setup, these S3 operations seem unnecessary.
Can someone help explain: 1. How to completely disable S3 access for HMS? 2. Are there specific configuration parameters I should modify? 3. Is there any potential impact on functionality if S3 access is disabled? Current setup: - HMS running as a Spark sidecar container - Only using HMS for metadata storage - No direct data storage requirements for HMS Thanks in advance for your help. Best regards, Andor Markus
