* Restructure NamespaceInfo Protos
* System namespace registration is moved to the immutableClusterMetadata path, rather than registering in schema
* Add NewUUID(), Fix Namespace test
* Remove unused import
* Serialization moved to Manager
Rename generated binaries:
- cadence -> temporal
- cadence-server -> temporal-server
- cadence-canary -> temporal-canary
- cadence-sql-tool -> temporal-sql-tool
- cadecne-cassandra-tool -> temporal-cassandra-tool
Moved core schema files for all database implementation to be under temporal folder.
Also used 'temporal' as keyspace or database name for core schema.
Renamed all environment variable to use TEMPORAL instead of CADENCE.
Renamed all docker scripts to references to point to new executables and mention
temporal.
Change reference to buildkite pipelines for temporal.
- ProtoWorkflowExecutionInfo definition - Moves SQL from Thrift and Cassandra from frozen
- WorkflowExecutionInfo split into two objects (added WorkflowExecutionState) to support UpdateCurrentExecution workflows where the store layer wont want to fetch and manipulate an existing monolith proto.
- Checksum proto introduced, Cassandra moves from frozen Checksum to proto
- This does not move any protos into the request layer and leaves InternalWorkflowMutableState, so common field mapping functions exist
- The go defined ReplicationInfo struct is consolidated to the proto replication package ReplicationInfo
* ClusterMembership Pagination Needs Monotonic SQL Id
* ClusterMembership Pagination Fields on GetClusterMembers
* Expanded ClusterMembership tests to include pagination
This change adds three new apis to the ClusterMetadataManager persistence client across Mysql, Postgresql and Cassandra implementations:
- GetActiveClusterMembers
- UpsertClusterMembership
- PruneClusterMembership
This paves the way for a subsequent change to persist and coordinate cluster membership through this layer.
This builds upon https://github.com/temporalio/temporal/pull/65 and implements the logic on top of the provided schemas to make the number of history shards and the cluster name read-only configuration.
See PR commits for step by step vertical implementation of a configuration value to the persistence layer.
* Add ack level to source cluster and source cluster can clean up replication task based on min ack level from all other clusters
* Add sync shard info from get replication messages API
Samar Abbas