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
I searched existing ideas and did not find a similar one
I added a very descriptive title
I've clearly described the feature request and motivation for it
Feature request
Currently, Weaviate lib args is limitating:
exportinterfaceWeaviateLibArgs{client: WeaviateClient;/** * The name of the class in Weaviate. Must start with a capital letter. */indexName: string;textKey?: string;metadataKeys?: string[];tenant?: string;}
the textKey is a single string and same for Document.
the idea would be to support multi pageContent for Document (a Record/Dictionary) and have not just textKey but rather textKeys as string[]
Motivation
I'm building a similarity categorizer, and I'd like to keep datastructure as lean as possible. Weaviate allows to create a vector on a field basis.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Checked
Feature request
Currently, Weaviate lib args is limitating:
the
textKey
is a single string and same forDocument
.the idea would be to support multi
pageContent
forDocument
(a Record/Dictionary) and have not justtextKey
but rathertextKeys
asstring[]
Motivation
I'm building a similarity categorizer, and I'd like to keep datastructure as lean as possible. Weaviate allows to create a
vector
on a field basis.Meaning I could have:
and yet create a vector for each of these fields
Proposal (If applicable)
No response
Beta Was this translation helpful? Give feedback.
All reactions