You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/feature-servers/registry-server.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,15 @@
4
4
5
5
The Registry server supports both gRPC and REST interfaces for interacting with feature metadata. While gRPC remains the default protocol—enabling clients in any language with gRPC support—the REST API allows users to interact with the registry over standard HTTP using any REST-capable tool or language.
6
6
7
+
Feast supports running the Registry Server in three distinct modes:
| REST only |`feast serve_registry --rest-api --no-grpc`| Used for REST-only clients like the UI |
14
+
15
+
7
16
## How to configure the server
8
17
9
18
## CLI
@@ -12,10 +21,16 @@ There is a CLI command that starts the Registry server: `feast serve_registry`.
12
21
To start the Registry Server in TLS mode, you need to provide the private and public keys using the `--key` and `--cert` arguments.
13
22
More info about TLS mode can be found in [feast-client-connecting-to-remote-registry-sever-started-in-tls-mode](../../how-to-guides/starting-feast-servers-tls-mode.md#starting-feast-registry-server-in-tls-mode)
14
23
15
-
To enable REST API support, start the registry server with REST mode enabled :
24
+
To enable REST API support along with gRPC, start the registry server with REST mode enabled :
16
25
17
26
`feast serve_registry --rest-api`
18
27
28
+
This launches both the gRPC and REST servers concurrently. The REST server listens on port 6572 by default.
0 commit comments