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

When I try to customize the table prefix, the cache may have problems finding the key value; For example, set table_prefix to xxxx_. The possible cause is that the prefix of the cache value related to "global_xxxx“ is set in the code. #745

Open
shenhuanjie opened this issue Jul 31, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@shenhuanjie
Copy link

Gorse version
Lastest

Describe the bug

# The naming prefix for tables (collections, keys) in databases. The default value is empty.
table_prefix = "custom_"

# The naming prefix for tables (collections, keys) in cache storage databases. The default value is `table_prefix`.
cache_table_prefix = ""

# The naming prefix for tables (collections, keys) in data storage databases. The default value is `table_prefix`.
data_table_prefix = ""

When I try to customize the table prefix, the cache may have problems finding the key value; For example, set table_prefix to xxxx_. The possible cause is that the prefix of the cache value related to "global_xxxx“ is set in the code.

Like this :

redis-cli get global_meta/matching_index_recall
null
@shenhuanjie shenhuanjie added the bug Something isn't working label Jul 31, 2023
@zhenghaoz
Copy link
Collaborator

The right place of this value is:

get xxxx_global_meta/matching_index_recall

@aqlx86
Copy link

aqlx86 commented Jul 25, 2024

is this fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants