Declarative API for managing connectors and schemas
AssigneeConfluent, Inc.
InventorsRajesh Rc, Pei Yang, Andrew Ding, Rohit Bakhshi, Lokesh Shekar, Steven Costa
Life of this patent
Estimating the term…
Abstract
A request to configure a connect cluster including one or more connectors for a cloud computing system is received. The request include a desired connector state. A connector specification file is automatically generated based on the desired connector state for the connect cluster via a declarative application programming interface (API). Application resources associated with the connect cluster are automatically configured based on the specification file.
Claims20
A method comprising:
- receiving, at a declarative application programming interface (API), a request to configure a connect cluster comprising one or more connectors for a cloud computing system, the request including a particular state and a schema defined by a user for the connect cluster;
- in response to receiving the request, automatically generating a connector specification file based on the particular state and schema defined by the user that triggers installation of one or more connector plugins, the connector specification file including a list of the one or more connector plugins;
- automatically configuring application resources associated with the connect cluster based on the connector specification file, the automatically configuring including causing download and installation of the one or more connector plugins;
- detecting a connector in the connect cluster being in a failed state;
- and
- in response to detecting the connector being in the failed state, attempting to restart the connector via the declarative API.
A system, comprising:
- at least one processor;
- and
- memory storing instructions that, when executed by the at least one processor cause the system to perform operations comprising:
- receiving, at a declarative application programming interface (API), a request to configure a connect cluster comprising one or more connectors for a cloud computing system, the request including a particular state and a schema defined by a user for the connect cluster;
- in response to receiving the request, automatically generating a connector specification file based on the particular state and schema defined by the user that triggers installation of one or more connector plugins, the connector specification file including a list of the one or more connector plugins;
- automatically configuring application resources associated with the connect cluster based on the connector specification file, the automatically configuring including causing download and installation of the one or more connector plugins;
- detecting a connector in the connect cluster being in a failed state;
- and
- in response to detecting the connector being in the failed state, attempting to restart the connector via the declarative API.
A non-transitory machine-readable medium having instructions embodied thereon, the instructions executable by a processor of a machine to perform operations comprising:
- receiving, at a declarative application programming interface (API), a request to configure a connect cluster comprising one or more connectors for a cloud computing system, the request including a particular state and a schema defined by a user for the connect cluster;
- in response to receiving the request, automatically generating a connector specification file based on the particular state and schema defined by the user that triggers installation of one or more connector plugins, the connector specification file including a list of the one or more connector plugins;
- automatically configuring application resources associated with the connect cluster based on the specification file, the automatically configuring including causing download and installation of the one or more connector plugins;
- detecting a connector in the connect cluster being in a failed state;
- and
- in response to detecting the connector being in the failed state, attempting to restart the connector via the declarative API.
Dependencies are inferred from the claim text.