Hi Guys
We have faced an issue where tlog size is increasing unnecessarily. We are
using a "heavy indexing, heavy query" approach. We enabled hard commit
also,
solr cloud: 6.6
zk: 3.4.10
shards: 2, replication factor= 2
solrconfig,
${solr.autoCommit.maxTime:15000}
1
Hello,
I am using Solr in a distributed environment where I have split my collection
into parts, which I have running on different nodes. When I create each part
of the collection, I set numShards and replicationFactor to 1. The query speed
is most important to us, and we are not worried abou
This is useful. Thanks, David.
Although in my case, I don't think the solution to the issue you
mentioned resolves the issue.
Here is why -
I don't want to point to other fields for highlighting but use the same
copy fields destination fields for highlighting.
This is because those copy field dest
While performing atomic indexing, I run into an error which says 'unknown
field X' where X is not a field specified in the schema. It is a
discontinued field. After deleting that field from the schema, I have
restarted Solr but I have not re-indexed the content back, so the deleted
field data stil
I'm not 100% clear; perhaps you could use a hypothetical example where you
more clearly state which of f1 or f2 is stored, which way the copyField
goes, which field(s) you are already listing in "qf" for search.
It's been awhile since I last looked at that JIRA issue but I'm imagining a
feature wh
Hey Solr community,
I found myself doing some maintenance inside QueryElevationComponent
related to some much larger refactoring. I'm seeing a fair amount of
complexity around it's support of "elevate.xml" in a Solr *data* directory
(where the index is). I don't know of any other Solr component
