lucene-solr | Apache Lucene and Solr open-source search software | Search Engine library

I have a flow that starts with a poller and hands off the message to several async flows downstream using task-executors to execute in parallel for a given dataset. A downstream aggregator completes the flow and notifies the poller that the flow is complete.

I would like to track every execution of the poller by using MDC so that the logs can be mapped to a particular execution of the flow.

I started by adding MDC to the poller thread (using Advice), however with this approach there could be a couple of issues:

1. How do I stamp the MDC on the executor thread when the async hand off happens?
2. Since executor uses a a thread pool, do I need to clear the MDC before the thread returns to the pool? Will there be any side effects?

Another approach would be to add MDC to the Message header and set it manually on the new thread during the async handoff. How to do that? For example, if I turn on the debug logs, the MDC should be stamped right from the beginning of the new thread execution and not from the point where my logic starts in the service activator. How to set this on the task-executor thread (and probably also remove before returning to the pool) using XML configuration? Something like an MdcAwareThreadPoolExecutor seen here. Also, I would not want the MDC logic to be spread across all the async handoff endpoints, may be there is some generic way to configure it?

Is there a better way to achieve this? Any known solutions?

I need to move a solr core running on 5.5.3 to new server, where I installed solr 8.1.1. Unfortunately the exixsting schema.xml uses several instances of

I'm using SolrCLoud is to search documents with multiple attributes. In my application, I would like to search over all the fields if the query does not specify any specific field such term1 AND term2 query should search for that combination in all the fields.

Reading the documentation looks like you can define a default fields for your search.

I have found examples of changing the default facets for search handler, but not for the default search fields but not for the default search fields on query handler.

Does anyone know how to use the Solr API to change the default fields in the QueryHandler?

I am using straight up Lucene (no Solr or ElasticSearch) to index a set of documents of which follow a parent-child hierarchy.

I am using 'blocks' to accomplish this by adding all children followed by the parent to the same block calling:

I'm trying to automatically bootstrap a SolrCloud cluster. I've figured out how to upload my configuration files and my solr.xml file to zookeeper using

I am setting up a new Solr server and I'm running into an issue I haven't experienced in previous Solr installations. When I navigate to a core's "Dataimport" tab (without even triggering an import request), several of the HTTP requests made by the admin UI fail. Checking the Solr logs, I see this stacktrace:

I am running official Docker Hub Apache Solr 7.4 image inside GCP Kubernetes Engine.

I need to upload JSON documents to the index. In the past I've only had experience uploading documents stored on the same machine that hosts Solr instance using bin/post command or the Admin UI.

Now I need to upload quite a few JSON documents from my machine to the Solr instance in the Docker container (86 documents ~30MB each to be exact). Adding so much extra data to the image doesn't make sense. And JSON Formatted Index Updates docs page only provides two options:

• Uploading JSON docs located on the same machine as Solr instance or
• Specifying JSON document directly in the curl command

I tired adding the documents using commands that I would expect to work (note that I use localhost here since I test the Docker image locally first, but the idea is the same):

I'm trying to run solr as a SystemD service. When I start the service I get this warning then the solr server stops.

I just started to learn Solr, when I create the index on the "films" example, I got only 5 documents in Solr Admin which is of course wrong. Here are the steps from Steve Rowe that I followed: