Hi,
I am running into a conflict between two constraints.
Atomic updates require copy-field destinations to be stored=false. However,
if we want to use these copy-field destination fields in highlighting then
they need to be stored=true.
How to resolve this conflict?
I resolved this issue by extending the class to SearchComponent instead of
QueryComponent. It seems that SearchComponent sits at a higher level of
abstraction than QueryComponent and is useful when you want to work on a
layer above shards.
On Wed, Mar 10, 2021 at 8:05 PM gnandre wrote:
> I have
I am getting exception trying to remove a zookeeper node. The node is old
solr’s chrot (condatining data of one node).
Exception in thread "main" java.lang.StackOverflowError
at org.apache.zookeeper.ClientCnxn$Packet.(ClientCnxn.java:280)
at org.apache.zookeeper.ClientCnxn.queueP
And to add to your confusion:
* the solr repo was just split from the lucene-solr repo
* the "master" branch was renamed "main" ...
https://gitbox.apache.org/repos/asf#solr
https://github.com/apache/solr/tree/main
: Date: Tue, 2 Mar 2021 15:54:10 -0500
: From: Houston Putman
: Reply-To: solr
Hi:
Distributed group query, if rename the unique key field name, will be
java.lang.NullPointerException.
Because of without StoredFieldsShardResponseProcessor processing rename.
Can I create an issue to fix it?
query("q", "*:*", "rows", 100, "fl", “aliasName:id," + i1,
