[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-27。"],[[["\u003cp\u003eDataproc Metastore services require choosing between the Apache Thrift or gRPC protocol, which dictates how Hive Metastore clients access metadata.\u003c/p\u003e\n"],["\u003cp\u003eThe Apache Thrift protocol is the legacy default, necessary for Kerberos implementation, and allows for choosing a custom port number, defaulting to \u003ccode\u003e9083\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe gRPC protocol is a modern, high-performance option that must be explicitly selected, automatically uses port \u003ccode\u003e443\u003c/code\u003e, and can't be switched to Thrift after creation.\u003c/p\u003e\n"],["\u003cp\u003eThe gRPC protocol offers enhanced security via IAM and supports federation with other Google Cloud products, making it the recommended choice.\u003c/p\u003e\n"],["\u003cp\u003eAfter selecting either protocol, the Dataproc Metastore can be connected to from a Dataproc cluster, which will then utilize the metastore for its operations.\u003c/p\u003e\n"]]],[],null,["# About Dataproc Metastore endpoint protocols\n\nWhen you create a Dataproc Metastore service, you must choose to use\none of the following endpoint protocols:\n\n- The Apache Thrift protocol\n- The gRPC protocol\n\nThis protocol defines how your Hive Metastore clients access metadata stored in\nyour Dataproc Metastore service. This choice can also affect the\nfeatures that you can integrate and use with your service.\n\nThis page explains the conceptual differences between each of the endpoint\nprotocols.\n\n### Apache Thrift\n\nThe [Apache Thrift](https://thrift.apache.org/) protocol is the\nlegacy default option that is preselected when you create a\nDataproc Metastore service.\n\nIf you require Kerberos in your implementation, you should use this option. If\nyou don't require Kerberos, consider using the gRPC protocol, which provides\naccess to additional features.\n\nIf you use a Thrift endpoint, you can choose the port number that the Thrift\ninterface connects to. By default, port number `9083` is used.\n\n#### After choosing the Thrift protocol\n\nAfter you create a Dataproc Metastore using Thrift, you can connect to\nit from a [Dataproc cluster or self-managed\ncluster](/dataproc-metastore/docs/attach-dataproc). Your cluster then uses\nDataproc Metastore as its Hive metastore.\n\n### gRPC\n\nThe [gRPC protocol](https://grpc.io/) is the modern, portable, high\nperformance option that you must explicitly select when you create a\nDataproc Metastore service.\n\nIf you choose the gRPC protocol, you can't update it to Thrift at a later date.\nIf you want to move from gRPC to Thrift, you must create a new\nDataproc Metastore.\n\nIf you use a gRPC endpoint, you can't choose the port number that the gRPC\ninterface uses. Instead, port number `443` is automatically assigned to your\ninterface.\n| **Tip:** We recommend that you use the gRPC protocol because it provides additional security through Identity and Access Management (IAM). It also supports federation integrations with other Google Cloud products.\n\n#### After choosing the gRPC protocol\n\nAfter you create a Dataproc Metastore using the gRPC endpoint protocol,\nyou must grant [additional IAM roles](/dataproc-metastore/docs/grpc-endpoints).\nAfter, you can connect to it from a [Dataproc\ncluster](/dataproc-metastore/docs/attach-dataproc). Your cluster then uses\nDataproc Metastore as its Hive metastore.\n\nWhat's next\n-----------\n\n- [Choose an endpoint protocol](/dataproc-metastore/docs/endpoint-protocol)\n- [Access gRPC endpoints](/dataproc-metastore/docs/grpc-endpoints)"]]