Windows, x64

@wlad this may be actually expected.

The testsuite specifies --ignore-db-dirs=.rocksdb option:
https://github.com/MariaDB/server/blob/bb-10.2-mariarocks/storage/rocksdb/mysql-test/rocksdb/suite.opt

I recall discussing it with serg: there is no way a storage engine can tell the SQL layer that "I am creating this directory in the datadir, please ignore it". So --ignore-db-dirs is the only currently available solution.

I imagine, when rocksdb engine is starting up, it may update ignore-db-dirs list (opt_ignore_db_dirs variable) itself. Function push_ignored_db_dir(char *path) might be useful for that, as there is a hash, and array and what not made of opt_ignore_db_dirs

How do I drop this database? Please someone tell me.

p4karthikeyan, it is not really a database.
The best way to solve this is to add ignore-db-dirs=.rocksdb into your my.cnf file.

If you are certain you do not have any MyRocks tables on your system, there is another way: Go to the data directory and manually delete the .rocksdb subdirectory there.

Thank you Sergei, I deleted the directories manually.

I thought thats where the data is stored in disk - so if I have RocksDB tables, I cant really delete this directory - Am I correct?

psergey,

Please find a proper solution before MDEV-9658 happens. It's not just a cosmetic issue, there are some obscure problems with using information_schema due to this garbage; and the workaround is viable for a proof of concept, but not for a stable version, we cannot tell every user to populate the option.

I encounter the same problem after activating RocksDB. One of the nasty consequence is that a mysqldump --all-databases fails with the message:

mysqldump: Got error: 1102: "Incorrect database name '#mysql50#.rocksdb'" when selecting the database

Fixed as part of fix for MDEV-14123. it is #rocksdb now, and it is not shown in SHOW DATABASES.

This is claimed to be 'fixed' but I'm still hitting it with MariaDB 10.3.12:

[root@www duply]# mysqldump -u root --all-databases
...
mysqldump: Got error: 1102: "Incorrect database name '#mysql50#.rocksdb'" when selecting the database

I guess my dir was created while the bad old name was still in use and there is no automatic migration? Is there a manual way I can fix this up? Thanks.