Hello,
I group search result by a field (with high cardinality)
I paginate search page using num of groups using param group.ngroups=true.
But that cause high CPU issue. So i turn off it.
Without ngroups=true, i can't get the num of groups so pagination is not
correct because i must use numFound,
I was able to resolve the issue.I was passing the extracted text content of
each document to Solr for indexing after converting to lowercase(did this
for a different usage).When the original content(without converting
lowercase) was indexed annotated entities were enriched to respective fields
to
Thanks Erick, that summary is very helpful.
Nawab
On Mon, May 29, 2017 at 1:39 PM, Erick Erickson
wrote:
> Yeah, it's a bit confusing. I made Yonik and Mark take me through the
> process in detail in order to write that blog, misunderstandings my
> fault of course ;)
>
> bq: This makes me thi
Yeah, it's a bit confusing. I made Yonik and Mark take me through the
process in detail in order to write that blog, misunderstandings my
fault of course ;)
bq: This makes me think that at the time of soft-commit,
the documents in preceding update requests are already flushed (might not
be on the
> I believe that my solution isolates manual change to two ZK nodes in DC2,
> while your requires config change to 1 in DC2 and manual start/stop of 1 in
> DC1.
Answering my own statement here. Turns out that in order to flip the observer
bit for one ZK node, you need to touch the config of all
Thanks Erick,
I have read different documents in this area and I am getting confused due
to overloaded/"reused" terms.
E.g., in that lucidworks page, the flow for an indexing request is
explained as follows. This makes me think that at the time of soft-commit,
the documents in preceding update re
If you are not using NRT readers then the applyAllDeletes/writeAllDeletes
boolean values are completely unused (and should have no impact on your
performance).
Mike McCandless
http://blog.mikemccandless.com
On Sun, May 28, 2017 at 8:34 PM, Nawab Zada Asad Iqbal
wrote:
> After reading some more
> In my setup once DC1 comes back up make sure you start only two nodes.
And if you start all three in DC1, you have 3+3 voting, what would then happen?
Any chance of state corruption?
I believe that my solution isolates manual change to two ZK nodes in DC2, while
your requires config change to
There's a long post here on this that might help:
https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Short form: soft commit doesn't flush tlogs, does not start a new
tlog, does not close segments, does not open new segments.
Hard commit does all
Hi,
Any updates on this issue? I am using Solr 6.3 and I have hit this same
bug...
Thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/java-lang-NullPointerException-in-json-facet-hll-function-tp4265378p4337877.html
Sent from the Solr - User mailing list archive at Nabb
Michael,
I assume you were trying his out in the SolrAdmin Query tab? With the
debug=true flag set? What do you see in the debug output about scoring?
You might end up using a Boost Function to get the desired ranking.
Google "solr multiple boost functions".
cheers -- Rick
On 2017-05-29 0
Hello,
I'm new to this list and having a question regarding nested documents with
scoring through eDisMax.
We do have an index of e-books that contains the metadata of the e-book and
each page as a single document:
- Book 1
- Page 1
- Page 2
- Page 3
- ...
- Pag
12 matches
Mail list logo