# Error during nearText call: panic occurred: ValidateParam was called without any known params present **URL:** \ **Category:** Support\ **Created:** [April 22, 2024, 1:19pm UTC](https://forum.weaviate.io/t/error-during-neartext-call-panic-occurred-validateparam-was-called-without-any-known-params-present/2083 "2024-04-22T13:19:36Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![Robert\_Oschler](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/robert_oschler/32/1308_2.png) [@Robert\_Oschler](https://forum.weaviate.io/u/Robert_Oschler)\ **Post date:** [April 23, 2024, 10:13pm UTC](https://forum.weaviate.io/t/error-during-neartext-call-panic-occurred-validateparam-was-called-without-any-known-params-present/2083/11 "2024-04-23T22:13:15Z")
I’ll give that a try. I did not want to do per-property vectorization. That is the schema that was given to me here: > [@Is nearText() completely a Weaviate cloud operation, no outbound LLM call?](https://forum.weaviate.io/t/is-neartext-completely-a-weaviate-cloud-operation-no-outbound-llm-call/2048/6): > > Hi! The downside of using object data type, for now, is that they are not indexable nor filterable: from docs: As of 1.22, object and object[] datatype properties are not indexed and not vectorized. Future plans include the ability to index nested properties, for example to allow for filtering on nested properties and vectorization options. for the url, you can also use a text, however, as you don’t want it added as part of the vectorization, you mark it to skip, like so: const schema … Collection level vectorization is fine. --- _[View the full topic](https://forum.weaviate.io/t/error-during-neartext-call-panic-occurred-validateparam-was-called-without-any-known-params-present/2083)._