Hi Alessandro,
Thank you for your detailed answer.
As I understand it, nested documents speed up searches on hierarchical
documents compared to Query Time Joins andc onsume fewer resources but
could create problems during reindexing.
Are there any studies to understand if there are limits to the n
Hi Ishan,
I have looked into that doc, and it looks like the solr version has to
be >8.8 and the config needed is to add the query parameter "&minExactCount=k"
where k is 10 or 100 depending on the accuracy of the first k docs.
I ran a query performance test using an internal tool, with k set t
On 1/31/24 21:59, Anuj Bhargava wrote:
Why does *Optimize* in the *dataimport* section of solr Admin UI duplicate
the records. A new copy is created of each record. "*id*" and "_*version*_"
are different, everything else is the exact copy. Each time I run Optimize,
the initial number of records g
We are running org.apache.solr_solr-solrj-8.4.1
We are occasionally seeing the following error message:
org.apache.solr.common.SolrException: Invalid UUID String: 'static'
at org.apache.solr.schema.UUIDField.toInternal(UUIDField.java:88)
at
org.apache.solr.schema.FieldType.read
On 2/1/24 08:09, Shawn Heisey wrote:
To verify that what I say is true, manually kick an optimize off when
you're NOT doing an import. If your index is named XXX, this command
would do it:
curl "http://hostname:port/solr/XXX/update?optimize=true";
That command is not working for me on SolrC
Update. I am also seeing this message:
[test] webapp=null path=null
params={q=static+firstSearcher+warming+in+solrconfig.xml&distrib=false&event=firstSearcher}
hits=0 status=0 QTime=41
And in our solrconfig.xml, we have this
static firstSearcher warming in solrc
Hi Mark,
Reading the first stack trace. Right, it's triggered by the listener, but
df (default field) is configured for UUIDField, the it fails to parse
"static" as UUID. So, remove the listener or fix default query field.
The second isn't so certain, but sounds like realtime get is requested when
Thanks, I am removing the listener.
you said the *translation *did you mean the *transaction* log? We do
configure that:
${solr.ulog.dir:}
45000
true
1000
Also, we do use a real-time get. Is there a possibility that something else
tu
Thanks Shawn,
This works -
http://localhost:8983/solr/XXX/update?optimize=true&maxSegments=1
Regards,
Anuj
On Thu, 1 Feb 2024 at 21:04, Shawn Heisey
wrote:
> On 2/1/24 08:09, Shawn Heisey wrote:
> > To verify that what I say is true, manually kick an optimize off when
> > you're NOT doing an
Since you got it "seeing (at about the same time):" may it be a temporary
issue during commit, which may go on retry?
On Fri, Feb 2, 2024 at 1:28 AM Mark Hieber wrote:
> Thanks, I am removing the listener.
>
> you said the *translation *did you mean the *transaction* log? We do
> configure that:
10 matches
Mail list logo