Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display Async Replication with appropriate icon #781

Closed
antonkovalenko opened this issue Mar 29, 2024 · 4 comments · Fixed by #856
Closed

Display Async Replication with appropriate icon #781

antonkovalenko opened this issue Mar 29, 2024 · 4 comments · Fixed by #856
Assignees

Comments

@antonkovalenko
Copy link
Member

antonkovalenko commented Mar 29, 2024

Designers have icon, please ask them.
One of the objects in a directory listing might have async replication type.

This issue is for displaying it with appropriate icon

@artemmufazalov
Copy link
Member

artemmufazalov commented Mar 29, 2024

Icon should be added also here: https://github.com/ydb-platform/ydb-ui-components

@antonkovalenko
Copy link
Member Author

@antonkovalenko
Copy link
Member Author

icon attached

Image

@antonkovalenko
Copy link
Member Author

How to create async replication

with login auth

CREATE ASYNC REPLICATION `my_replication`
FOR `/mydb/table` AS `replicated_table`
WITH (
  ENDPOINT = "db.ydb.tech:2135",
  DATABASE = "/mydb",
  USER = "user",
  PASSWORD = "password"
);
  
CREATE ASYNC REPLICATION `my_replication`
FOR `/mydb/table1` AS `replicated_table1`,
    `/mydb/table2` AS `replicated_table2`
WITH (
  ENDPOINT = "db2.ydb.tech:2135",
  DATABASE = "/mydb2",
  USER = "user",
  PASSWORD = "password"
);

with OAuth token

CREATE ASYNC REPLICATION `replication` FOR
  `orders` AS `orders`,
  `orderLines` AS `orderLines`,
  `stock` AS `stock`
WITH (
  CONNECTION_STRING = 'grpc://balancer.ydb.tech:2135/?database=/mydb',
  TOKEN = 'VERY-SECRET-TOKEN'
);"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants