Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Qdrant location.
qdrant_api.png

Qdrant API

Create a Qdrant Destination​

  1. Click the + icon on the Nexset that will be sent to the Qdrant destination, and select the Send to Destination option from the menu.

  2. Select the Qdrant connector from the list of available destination connectors. Then, select the credential that will be used to connect to your Qdrant account, and click Next; or, create a new Qdrant credential for use in this flow.

  3. In Nexla, Qdrant destinations can be created using pre-built endpoint templates, which expedite destination setup for common Qdrant endpoints. Each template is designed specifically for the corresponding Qdrant endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Qdrant destinations can also be configured manually, allowing you to send data to Qdrant endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Qdrant endpoints. Each template is designed specifically for the corresponding Qdrant endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Upsert Points (Vectors)

    This endpoint template performs the insert + update action on specified points in your Qdrant collection using records from a Nexset. Any point with an existing ID will be overwritten. Use this template when you need to insert or update vectors in your Qdrant collection for similarity search, recommendation systems, or other AI-powered applications.

    • Enter the collection name in the Collection Name field. This should be the name of the Qdrant collection where you want to upsert points (vectors). The collection name determines which collection will receive the points.

    This endpoint sends data as JSON in the request body to upsert points (vectors) into your Qdrant collection. The endpoint uses batch mode to efficiently send multiple points in a single request. Each record from your Nexset will be included in the batch, and points will be upserted in batches of up to 20 points per request.

    The point structure must match the Qdrant API's expected format. Each point should include an ID, vector values, and optional payload. For detailed information about point upsert, request body formats, batch processing, and available point properties, see the Qdrant API documentation.

    Used to upserting batches of points(vectors)

    This endpoint template batch updates points, including their respective vectors and payloads, in your Qdrant collection using records from a Nexset. Use this template when you need to efficiently upsert multiple points in a single batch operation.

    • Enter the collection name in the Collection Name field. This should be the name of the Qdrant collection where you want to batch update points (vectors). The collection name determines which collection will receive the batch updates.

    This endpoint sends data as JSON in the request body to batch update points (vectors) in your Qdrant collection. The endpoint uses batch mode to efficiently send multiple points in a single request. Each record from your Nexset will be included in the batch operation, and points will be batch updated in batches of up to 20 points per request.

    The batch update structure must match the Qdrant API's expected format. Each batch operation should include an upsert operation with points. For detailed information about batch updates, request body formats, batch processing, and available point properties, see the Qdrant API documentation.

Configure Manually​

Qdrant destinations can be manually configured to send data to any valid Qdrant API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Qdrant API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Qdrant API from the Method pulldown menu. Qdrant API typically uses PUT method for upserting points and POST method for batch operations.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Qdrant API from the Content Format pulldown menu. Qdrant API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Qdrant API endpoint to which data will be sent in the URL field. This should be the complete URL including your cluster host URL (from your credential), the API path (e.g., /collections/{collection_name}/points, /collections/{collection_name}/points/batch), and any required query parameters. Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Qdrant API endpoint URL should point to the endpoint where you want to upsert points. The endpoint URL should include your cluster host URL and the appropriate API path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Qdrant API. The request body should contain the point data formatted as JSON, with field names matching the Qdrant API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings. For batch operations, you may need to format the request body to include an operations array containing upsert operations with points.

The request body must be valid JSON and must match the Qdrant API's expected format for the specific endpoint you're using. Qdrant API uses specific structures for different endpoints (upsert, batch update, etc.). Each point should include an ID, vector values, and optional payload. For detailed information about request body formats, available endpoints, and point structures, see the Qdrant API documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.