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
[This issue has been generalised based on Alex's message below]
The protocol spec includes definitions specific to Core and Cluster in one place. However, this exposes Cluster APIs on the Core server that could accidentally be implemented and additionally represents a domain leak. The Cluster protocol should be separate and extend the Core protocol in a separately released package.
The text was updated successfully, but these errors were encountered:
lolski
changed the title
Do not allow sending read replica request to Grakn Core server
Split read replica definition into its own definition only visible to Grakn Cluster
Jan 25, 2021
lolski
changed the title
Split read replica definition into its own definition only visible to Grakn Cluster
Make read replica definition part of Grakn Cluster specific definitions
Jan 25, 2021
lolski
changed the title
Make read replica definition part of Grakn Cluster specific definitions
Make read secondary replica type part of Grakn Cluster specific definitions
Jan 25, 2021
flyingsilverfin
changed the title
Make read secondary replica type part of Grakn Cluster specific definitions
Read secondary replica option should be part of cluster-specific protocol
Jan 10, 2023
flyingsilverfin
changed the title
Read secondary replica option should be part of cluster-specific protocol
Cluster-specific protocol should not be included in Core's protocol
Jan 10, 2023
Problem to Solve
[This issue has been generalised based on Alex's message below]
The protocol spec includes definitions specific to Core and Cluster in one place. However, this exposes Cluster APIs on the Core server that could accidentally be implemented and additionally represents a domain leak. The Cluster protocol should be separate and extend the Core protocol in a separately released package.
The text was updated successfully, but these errors were encountered: