weaviate/weaviate · error

wrong parameters

Error message

wrong parameters

What it means

The sum-transformers module's AdditionalPropertyFn expects the params argument to be the module's *Params type; if the dynamic type doesn't match the assertion, it throws 'wrong parameters'. This indicates the additional property was dispatched with unexpected parameter data — typically a marshalling or module wiring mismatch between what the GraphQL layer produced and what the module expects.

Source

Thrown at modules/sum-transformers/additional/summary/summary.go:58

	return &Params{}
}

func (p *SummaryProvider) ExtractAdditionalFn(param []*ast.Argument, class *models.Class) interface{} {
	return p.parseSummaryArguments(param)
}

func (p *SummaryProvider) AdditionalFieldFn(classname string) *graphql.Field {
	return p.additionalSummaryField(classname)
}

func (p *SummaryProvider) AdditionalPropertyFn(ctx context.Context,
	in []search.Result, params interface{}, limit *int,
	argumentModuleParams map[string]interface{}, cfg moduletools.ClassConfig,
) ([]search.Result, error) {
	if parameters, ok := params.(*Params); ok {
		return p.findSummary(ctx, in, parameters)
	}
	return nil, errors.New("wrong parameters")
}

View on GitHub (pinned to 75aa4b6d11)

Solutions

1. Ensure the GraphQL query passes valid summary arguments matching the module schema (e.g. summary: { properties: [...] })
2. Align client and Weaviate/module versions so the params schema matches
3. Verify only one sum-transformers module version is deployed across the cluster

Example fix

// before
_additional { summary } // no valid params shape
// after
_additional { summary(properties: ["description"], radius: 3) { ... } }

// ensure summary arguments match the module schema before querying
args := map[string]interface{}{"properties": []string{"content"}}
if len(args["properties"].([]string)) == 0 { return errors.New("summary requires properties") }

if p, ok := params.(*summary.Params); !ok { return fmt.Errorf("unexpected params type %T", params) }

catch (e) { if (e.message === 'wrong parameters') { // fix GraphQL summary argument shape / align module versions } }

When it happens

Trigger: Requesting the _additional { summary } property when the params cannot be asserted to *summary.Params — e.g. malformed/incorrectly shaped summary arguments in the GraphQL query, or a mismatch between module version and client schema.

Common situations: Out-of-date clients sending legacy argument shapes; mixing module versions in a cluster; issuing the additional property through a path that doesn't deserialize params into the expected struct.

Related errors

• no properties provided
• wrong parameters
• cannot get texts
• wrong parameters
• unknown params

AI-assisted analysis of weaviate/weaviate@75aa4b6d11 (2026-09-04). Data as JSON: /api/errors/2b768f82886a5fad. Report an issue: GitHub.