Bug: Rerank functionnality in Qdrant

:bug: Bug Report: Qdrant Node “similaritySearch is not a function” Error with Rerank Enabled

Problem Description

When I enable the new rerank functionality in the n8n Qdrant node, I get the following error:

this.vectorstore.similaritySearch is not a function

The workflow runs fine with rerank disabled, but fails immediately when I activate the rerank feature.

Environment Details

  • n8n Version: 1.102.0

Steps to Reproduce

  1. Create a workflow with a Qdrant node
  2. Configure the Qdrant node with valid connection details
  3. Enable the “Rerank” functionality in the node settings
  4. Run the workflow
  5. Error occurs: this.vectorstore.similaritySearch is not a function

Expected Behavior

The Qdrant node should work with rerank functionality enabled, performing similarity search with reranking applied to the results.

Actual Behavior

The workflow fails with a JavaScript error indicating the similaritySearch method doesn’t exist on the vectorstore object.

Workaround

Disabling the rerank functionality allows the node to work normally, but without the reranking benefits.

Additional Context

  • This appears to be a bug in the node’s implementation where the rerank feature changes how the vectorstore object is initialized
  • The error suggests the vectorstore object doesn’t have the expected similaritySearch method when rerank is enabled
  • Other users might be experiencing the same issue but haven’t reported it yet

Request

Could the development team please:

  1. Investigate why enabling rerank breaks the similaritySearch method
  2. Provide a timeline for when this might be fixed
  3. Confirm if this is a known issue or if additional debugging information is needed

Thanks for looking into this! The rerank functionality would be very useful for improving search results quality.


If anyone else is experiencing this issue, please comment below to help the team understand the scope of the problem.

3 Likes

Facing the same issue! I don’t understand it.

1 Like

same issue with Postgres Node

having same issue after adding rerank functionality

1 Like