This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
[Question] Regarding Hard-coded Elastic index vector dimension size #492
Labels
You can continue the conversation there. Go to discussion →
Context / Scenario
In trying to setup a custom LLM and also use the Elasticsearch integration, it's constantly complaining about the dimension size being different than the index mapping when ingesting documents.
Question
Is there a roadmap item or timeline on when this will be implemented?
kernel-memory/extensions/Elasticsearch/Elasticsearch/ElasticsearchMemory.cs
Line 78 in a1f280c
Took me at least a whole day to figure out that this was hard-coded while trying to setup a custom LLM.
The text was updated successfully, but these errors were encountered: