Requesting a way to detected detect newly created ColumnFamilyHandle in Secondary RocksDB instance

[anantharaman93]

Hi Team,

Use Case

In the POC I am trying I have 2 RocksDB instances one initialized using RocksDB.open (Say instance A) and another initialized using RocksDB.openAsSecondary (Say instance B) using the same data-directory.

Now, when the instances are running a new ColumnFamily is created on the instance A. How can I detect and create/initialize a new ColumnFamilyHandle for the newly created ColumnFamily on instance B where the RocksDB instance is already running?

Expected behavior

Expecting some way to actually detect and open newly created ColumnFamilies on the Secondary RocksDB instance.

Actual behavior

A easy of API to get the ColumnFamilies present in a given RocksDB instance or any technique to solve this issue.

Steps to reproduce the behavior

The issue can be reproduced by following the setups mentioned about.

Note: I have raised this case in rocksdb.dev and based the comment shared only I am posting it here.

Thanks.

[jowlyzhang]

Thanks for the request. This feature is not on our recent roadmap. A workaround would be if your primary instance can communicate with the secondary instance somehow when a new column family, would a secondary instance reopen work?

[anantharaman93]

@jowlyzhang Intimation of new addition of ColumnFamily is possible. But re-open is not-possible in our current flow.

[ameya-deshmukh]

@ajkr is this still up for grabs?

[ajkr]

@ameya-deshmukh Sorry for the delay. Yes it's still up for grabs.

[ameya-deshmukh]

Thanks!