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
Regarding "many search definitions can I have in a Vespa cluster":
Each search definition correspond to a separate instance of all the machinery and files needed to store and query a data type. 10k is definitely too many.
It sounds like you need a different solution. Either
create a generic search definition and maintain a mapping to its generic fields for each of your use-defined type.
create a generic search definition and mangle terms with the customer id to avoid cross-customer matches, or
Hi all,
First of all thank you for this amazing platform. I have 2 questions about Search definition.
Search definition creation in runtime
Is there any API which I can use to create a search definition (sd) in runtime.
This is a requirement, because the documents that I will index are depending on the user input in my front end application.
If it is not possible, what is the best way for me to implement/workaround this feature.
How many search definitions can I have in a Vespa cluster?
Lets say that I am creating 100000 search definitions. Is this possible? What is the impact in terms of performance?
The text was updated successfully, but these errors were encountered: