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
There is one yb-admin command to list all the DB stream IDs created. The syntax to use the command is as follows:
./yb-admin list_change_data_streams
By default, the above command would fetch all the streams on the server. But there is an optional flag to specify which namespace (database) the command should return the stream ID of.
Now even if I provide the optional database_name, the command still returns all the stream IDs available on the server.
Steps to reproduce:
Assuming that the yugabyte database exists by default, create one more database i.e. CREATE DATABASE testdb;
Connect to testdb --> \c testdb
Create a table --> create table test (a int primary key, b text); -- this step might not be necessary
Create stream IDs for databases
$ ./yb-admin create_change_data_stream ysql.yugabyte
CDC Stream ID: 7e90548121f84798902657ca5a5aa111 # This is the output
$ ./yb-admin create_change_data_stream ysql.testdb
CDC Stream ID: 5be8202a540a4c89ab464f7a10101c1f # This is the output
Now on executing ./yb-admin list_change_data_streams testdb
Notice that I am getting both the stream IDs now i.e. not the ones specific to testdb
There is one yb-admin command to list all the DB stream IDs created. The syntax to use the command is as follows:
./yb-admin list_change_data_streams
By default, the above command would fetch all the streams on the server. But there is an optional flag to specify which namespace (database) the command should return the stream ID of.
./yb-admin list_change_data_streams [database_name]
Now even if I provide the optional database_name, the command still returns all the stream IDs available on the server.
Steps to reproduce:
yugabyte
database exists by default, create one more database i.e.CREATE DATABASE testdb;
testdb
-->\c testdb
create table test (a int primary key, b text);
-- this step might not be necessary./yb-admin list_change_data_streams testdb
Notice that I am getting both the stream IDs now i.e. not the ones specific to
testdb
The text was updated successfully, but these errors were encountered: