what are the tree modes of hive metastore

Hive Metastore has three modes of operation:

1. Embedded Metastore: In this mode, the metastore service runs in the same JVM where the Hive service is running and it uses Derby Database in the backend to store metadata.

2. Local Metastore: In this mode, the metastore service runs in the same JVM where the Hive service is running but it connects to a standalone database such as MySQL or Oracle to store metadata.

3. Remote Metastore: In this mode, the metastore service runs on its own separate JVM and not in the Hive service JVM. Other applications can also make use of metastore service in this mode. It also connects to a standalone database to store metadata.

Hive Metastore has three modes of operation:

1. Embedded Metastore: In this mode, the metastore service runs in the same JVM where the Hive service is running and it uses Derby Database in the backend to store metadata.

2. Local Metastore: In this mode, the metastore service runs in the same JVM where the Hive service is running but it connects to a standalone database such as MySQL, Oracle, etc. running in a separate JVM, possibly in a separate machine.

3. Remote Metastore: In this mode, the metastore service runs on its own separate JVM and not in the Hive service JVM. Other applications including Hive communicate with it over Thrift Network APIs. This mode is typically used in production environments where multiple users are accessing the Hive service.