Actions6
Overview
This node integrates with Apache Solr, a powerful search platform, allowing users to perform various document management and search operations. Specifically, the "Delete by ID" operation deletes a single document from a Solr core using its unique document ID. This is useful when you want to remove outdated or irrelevant documents from your search index.
Common scenarios include:
- Removing a specific record that is no longer valid.
- Cleaning up entries after data deletion in an external system.
- Managing indexed content dynamically based on user actions.
Example: If you have a product catalog indexed in Solr and a product is discontinued, you can use this node to delete that product's document by its ID to keep the search results accurate.
Properties
| Name | Meaning |
|---|---|
| Commit | Whether to make the changes immediately visible in Solr (true/false). |
| Document ID | The unique identifier of the document to delete from the Solr index. |
Output
The node outputs JSON data representing the response from Solr after attempting the deletion. Typically, this includes success confirmation or details about the operation result. The output is structured as:
{
"json": {
// Response object from Solr indicating success or failure of the delete operation
},
"pairedItem": {
"item": <index_of_input_item>
}
}
No binary data is produced by this operation.
Dependencies
- Requires connection credentials to an Apache Solr instance, including host, port, core name, and optionally username/password for basic authentication.
- Needs an API key credential or equivalent authentication configured in n8n to connect securely to Solr.
- Uses the
@magierin-schnee/solr-clientlibrary internally to communicate with Solr.
Troubleshooting
Common issues:
- Incorrect or missing document ID will cause the delete operation to fail or have no effect.
- Authentication failures if credentials are incorrect or missing.
- Network connectivity problems to the Solr server.
- Trying to delete a document from a non-existent core or collection.
Error messages:
- Errors returned from Solr typically include HTTP status codes and messages such as "Document not found" or "Unauthorized".
- If the node throws an error related to authentication, verify the API key or username/password credentials.
- For network errors, check the Solr host, port, and firewall settings.
Resolution tips:
- Double-check the document ID value.
- Ensure the Solr core specified in credentials exists and is accessible.
- Confirm commit option is set appropriately to reflect changes immediately if needed.
- Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.