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
Is your feature request related to a problem? Please describe.
Yes, currently the index names (more precisely HNSW_INDEX_NAME and KEYWORD_INDEX_NAME) are not configurable, this means that you cannot create two or more document_stores tables on the same postgres schema, since you cannot have two indexes with the same name.
Describe the solution you'd like
I'd like for the index name to be configurable and to the index creation to be optional, just as the recreation of the table is also optional under the flag 'recreate_table'.
Describe alternatives you've considered
I've considered changing the index names on the tables manually, but because the index is always checked to exist by name it's impossible to workaround this.
Additional context
I'd be happy to make a PR for this myself, just want to make sure that I'm not missing anything before working on this.
The text was updated successfully, but these errors were encountered:
Awesome @anakin87.
I think it would be good to be optional to give more freedom for people that want to tinker with creating and managing indexes themselves, without the constant fear that haystack will always check for indexes to exist and create them if they don't.
However, I understand that might be different than how the other integrations are implemented, so I'm fine with only making the index name customisable if you think it's better.
Is your feature request related to a problem? Please describe.
Yes, currently the index names (more precisely HNSW_INDEX_NAME and KEYWORD_INDEX_NAME) are not configurable, this means that you cannot create two or more document_stores tables on the same postgres schema, since you cannot have two indexes with the same name.
Describe the solution you'd like
I'd like for the index name to be configurable and to the index creation to be optional, just as the recreation of the table is also optional under the flag 'recreate_table'.
Describe alternatives you've considered
I've considered changing the index names on the tables manually, but because the index is always checked to exist by name it's impossible to workaround this.
Additional context
I'd be happy to make a PR for this myself, just want to make sure that I'm not missing anything before working on this.
The text was updated successfully, but these errors were encountered: