kevinjqliu commented on issue #1019: URL: https://github.com/apache/iceberg-python/issues/1019#issuecomment-2274369979
>Ah I see, thanks! Using the standlone-metastore container did indeed work with pyiceberg. Awesome! > When I start the standalone metastore, I'm able to connect via pyiceberg. But I'm unable to docker exec -it metastore-standalone beeline -u 'jdbc:hive2://localhost:9083' - is that expected behavior? Yes, this is expected. Because beeline is used to connect to HiveServer2 > Is that a documentation error, or perhaps I'm misunderstanding what embedded Metastore means in this context? There's a couple of different ways to launch a "Hive setup" 1. "Launch the HiveServer2 with an embedded Metastore." This launches HiveServer2 and exposes its port. It also launches "an embedded Metastore" which as the name suggests, is not exposed. The "embedded metastore" is an instance of Hive Metastore. 2. "Launch Standalone Metastore". This launch Hive Metastore as a standalone service and exposes its port. But no the query engine part of Hive (HiveServer2) is not started. 3. "Using HS2 with Standalone/Remote Metastore". This is a hybrid. It launches both HiveServer2 and Hive Metastore and exposes both of its ports. Depending on what you're doing, option 3 should give you both a HiveServer2 which you can connect to using beeline, and a Hive Metastore which you can connect to with PyIceberg. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
