Dear solr users
I am new to solr. I am using Gitlab CI to deploy a decision tree model to
solr. However, I have been provided some other models to be deployed to
solr.
I am not sure how to deploy multiple models to solr. Is there a way? Is
there any architecture for multi-module deployment pipeli
Hi Team
We have created a new sitecore environment with the Azure market
place solution "Azure Experience Cloud" (PaaS). Sitecore version 9.3 XM scaled
topology with SOLR search. Since Solr App doesn't come by default with the
market place solution we created a new Web App for Solr
Hi,
I'm by no means expert on this so if anyone sees a mistake please correct me.
I think you need to index this field, since boost functions are added to the
query as optional clauses
(https://lucene.apache.org/solr/guide/6_6/the-dismax-query-parser.html#TheDisMaxQueryParser-Thebf_BoostFunctio
Hi,
I heavily use streaming expressions and facets, or export large amounts of data
from Solr to Spark to make analyses.
Please correct me if I know wrong:
+ requesting a non-docValues field in a response causes whole document to be
decompressed and read from disk
+ streaming expressions and e
> On Nov 4, 2020, at 6:43 AM, uyilmaz wrote:
>
> Hi,
>
> I heavily use streaming expressions and facets, or export large amounts of
> data from Solr to Spark to make analyses.
>
> Please correct me if I know wrong:
>
> + requesting a non-docValues field in a response causes whole document t
You don’t need to index the field for function queries, see:
https://lucene.apache.org/solr/guide/8_6/docvalues.html.
Function queries, as opposed to sorting, faceting and grouping are evaluated at
search time where the
search process is already parked on the document anyway, so answering the
I completely agree with Shawn. I’d emphasize that your heap is that large
probably to accommodate badly mis-configured caches.
Why it’s different in 5.4 I don’t quite know, but 10-12
minutes is unacceptable anyway.
My guess is that you made your heaps that large as a consequence of
having low hit
inline
> On Nov 4, 2020, at 2:17 AM, Modassar Ather wrote:
>
> Thanks Erick and Ilan.
>
> I am using APIs to create core and collection and have removed all the
> entries from core.properties. Currently I am facing init failure and
> debugging it.
> Will write back if I am facing any issues.
>
3/11/2020, Apache Solr™ 8.7 available
The Lucene PMC is pleased to announce the release of Apache Solr 8.7
Solr is the popular, blazing fast, open source NoSQL search platform
from the Apache Lucene project. Its major features include powerful
full-text search, hit highlighting, faceted search an
I am new to solr. I have solr installed in my home directory
(/home/jar/solr).
But when I start the tutorial, I get an open files limit error.
$ ./bin/solr start -e cloud
*** [WARN] *** Your open file limit is currently 1024.
It should be set to 65000 to avoid operational disruption.
If you
Hi,
You must have to change the ulimit -a parameters on your SO config.
I believe the problem that you have is in:
max user processes (-u) 4096
Kind regards.
David Martín Nieto
Analista Funcional
Calle Cabeza Mesada 5
28031, Madrid
T: +34 667 414 432
And too this:
open files (-n) 1024
At least.
David Martín Nieto
Analista Funcional
Calle Cabeza Mesada 5
28031, Madrid
T: +34 667 414 432
T: +34 91 779 56 98| Ext. 3198
E-mail: dmart...@viewnext.com | Web: www.viewnext.com
Thanks Erick. As indexed is not necessary, and docValues is more efficient
than stored fields for function queries, so we shall go with the
following:
3) indexed=false, stored=false, docValues=true.
Is my understanding correct?
Best,
Wei
On Wed, Nov 4, 2020 at 5:24 AM Erick Erickson
wrot
And in the case of both stored=true and docValues=true, Solr 8.x shall be
choosing the optimal approach by itself?
On Wed, Nov 4, 2020 at 9:15 AM Wei wrote:
> Thanks Erick. As indexed is not necessary, and docValues is more
> efficient than stored fields for function queries, so we shall go w
I am seeing the same error as in this thread:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/202004.mbox/
[1]
with Solr 8.5.0
2020-11-04 16:58:00.998 WARN (qtp335107734-3042730) [c:dovecot
s:shard1 r:core_node44 x:dovecot_shard1_replica_n43]
o.a.s.u.SolrCmdDistributor Unable to fi
Hi Erick,
I have put solr configs in Zookeeper. I have created a collection using the
following API.
admin/collections?action=CREATE&name=mycore&numShards=2&replicationFactor=1&collection.configName=mycore&
property.name=mycore
The collection got created and I can see *mycore**_shard1_replica_n1*
On 11/4/2020 9:32 PM, Modassar Ather wrote:
Another thing: how can I control the core naming? I want the core name to
be *mycore* instead of *mycore**_shard1_replica_n1*/*mycore*
*_shard2_replica_n2*.
I tried setting it using property.name=*mycore* but it did not work.
What can I do to achieve th
On 11/3/2020 11:49 PM, Narayanan, Bhagyasree wrote:
Steps we followed for creating Solr App service:
1. Created a blank sitecore 9.3 solution from Azure market place and
created a Web app for Solr.
2. Unzipped the Solr 8.1.1 package and copied all the contents to
wwwroot folder of the
18 matches
Mail list logo
