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
Requests to 3rd party integrations: #2#69
Lack of guidance for new users: #61
After starting the quest for not using OpenAI embedded, that use a "magic number" of 1536 for their resulting vectors, we see that most on-premises (or competitors) use any other vector length for their reasons.
This creates one of the most known headaches for developers. So, this issue is here to:
Remind the users that the embedding process differs from the "chat" process, and there is no standard yet. And to get worse, most Vector DBs still need to be ready for these non-standards.
Remind the developers that this information shall be shown everywhere. Metadata, popups, labels, whatever.
my 2 cents
The text was updated successfully, but these errors were encountered:
Requests to 3rd party integrations: #2 #69
Lack of guidance for new users: #61
After starting the quest for not using OpenAI embedded, that use a "magic number" of 1536 for their resulting vectors, we see that most on-premises (or competitors) use any other vector length for their reasons.
This creates one of the most known headaches for developers. So, this issue is here to:
my 2 cents
The text was updated successfully, but these errors were encountered: