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

[Question] Regarding Hard-coded Elastic index vector dimension size #492

Open
xdave opened this issue May 15, 2024 · 1 comment
Open

[Question] Regarding Hard-coded Elastic index vector dimension size #492

xdave opened this issue May 15, 2024 · 1 comment
Labels
question Further information is requested

Comments

@xdave
Copy link

xdave commented May 15, 2024

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?

const int Dimensions = 1536; // TODO: make not hardcoded

Took me at least a whole day to figure out that this was hard-coded while trying to setup a custom LLM.

@xdave xdave added the question Further information is requested label May 15, 2024
@xdave xdave changed the title [Question] [Question] Regarding Hard-coded Elastic index vector dimension size May 15, 2024
@dluc
Copy link
Collaborator

dluc commented May 15, 2024

/cc @afederici75 FYI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants