I would start with the sample 8.x schema and port your fields into that.
I’m doing a bunch of migrations from 4.10.4 and 6.6.2 and doing that
for both schema.xml and solrconfig.xml.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Apr 23, 2021, at 3:0
Use stemming for regular text, like news articles or product descriptions.
You want to match “job” to both “jobs report” and “job numbers”.
Use unstemmed for proper names—people, places, products. You do not
want “job” to match “Steve Jobs” but you do want it to match “Book of Job”.
You don’t want
Seeing a zookeeper_data? (directory name with ?ending) along
with zookeeper_data
and zookeeper_server.pid is only file in that directory ending with ? where
as all other files are under zookeeper_data directory.
Not really sure why this new folder with ? created , is that a known issue
with zookee
Hi,
There are two ways to query multiple collections as far as I know:
1) If your set of collections are fixed, you can use an alias pointing to
multiple collections and query the alias as if it was a regular collection,
replacing the name of the collection in URL with the alias
2) If your set
Thanks, but as far as I understand this is "just" a different, Json-based
syntax for the same underlying feature (join queries, no support for
parent/child block joins). So alas! my questions remain open. I have been
unable so far to find any comprehensive example I could relate to, and I have
Hi Everyone,
We generally query a solr store (collection) in the solr UI by
selecting each collection.
I would like to query multiple collections at a time, do we have any
backend command line scripts/commands. Could you please share it really
helps.
Please let me know if more information is req
Thanks, Tim. Alas, this is nothing more than a join query in Json syntax, so
does not really explain how the sort of query I am looking for could be
expressed. Any takers ?
A.
On 2021/04/22 20:45:37, Timothy Potter wrote:
> Might take a look at the domain join stuff in JSON facets too:
> http
Hallo,
I would use both at the same time. You do not always want to find all
stemmed forms of a term, but the unstemmed form instead, or at least have
the latter being scored higher. Out of the box, the scoring will already
take care of it.
Although i actually prefer both in one field, using the
If you focus on this part of the exception message, you should find your
answer:
... and retrievable(stored or docValues)...
(_version_ not retrievable
You need the _version_ field to be stored or docValues.
Cheers
--
Alessandro Benedetti
Apache Lucene/Solr Committer
Direc
Hi, what is your configuration for the “long” field type?
Also error says “_version_ not retrievable”
A field can be retrievable in 2 ways:
1) Marking it with stored=”true” (yours is not)
2) Marking it with docValues=”true” and having useDocValuesAsStored flag set to
true in schema too
My config
Hi,
Did you try with _version_ field stored (stored=true)?
Gaël
De : shacky
Envoyé : vendredi 23 avril 2021 12:09
À : solr-user
Objet : Unable to create core: _version_ field must exist in schema and be
searchable and retrievable and not multiValued
Hi,
I'm creating a new core on a newly
Hi,
I'm creating a new core on a newly installed Solr 8.8.2 and I'm trying to
porting my very old schema which I was using on my previous Solr 1.4
installation.
On my old schema I removed some deprecated field types and the deprecated
parameter "enablePositionIncrements" plus the "defaultSearchFie
Hello
I have aschema with two fields
One is stemmed and one isn't.
When I would use the stemmed field in my search. ( or when I shouldn't do it )
Regards
S
Hi,
Almost same reply as for new releases. There's a separate security section in
the website, also with an ATOM feed.
You could probably also setup an email rule on this list, looking for CVE in
the subject, and route those to a different folder.
Jan
> 23. apr. 2021 kl. 06:59 skrev Basheer K
Hi,
There are several ways to monitor new Solr releases.
* Periodically visit https://solr.apache.org/ or subscribe to the ATOM feed at
https://solr.apache.org/feeds/solr/news.atom.xml
* Look for [ANNOUNCE] messages here or in main ANNOUNCE list
https://lists.apache.org/list.html?annou...@apache
Thank you David. That helps , thanks for your reply.
On Fri, Apr 23, 2021 at 12:55 PM DAVID MARTIN NIETO
wrote:
> Hi,
>
> For my experience is not a good idea to have two instances in the same
> server, due to high consume of disk that solr have if can cause cpu
> increase or process thread of s
Not sure about reordered DBQs, but DBQs do not play well with concurrent
updates because it needs to block all updates in order to make sure all
replicas delete the same set of documents. That can result in queueing updates,
recovery and even OOM. Here is and older blogpost explaining that
http
Il giorno gio 22 apr 2021 alle ore 18:07 Mark H. Wood ha
scritto:
> It is possible that you will need to update your schema. Some of the
> field type implementations were replaced and the old ones are no
> longer available since v5.
>
Thanks Mark.
I think I will be able to modify the field typ
Hi Rekha,
Do you also have query load while indexing? Have you tried the TLOG + PULL
replica types?
https://solr.apache.org/guide/8_4/shards-and-indexing-data-in-solrcloud.html#types-of-replicas
Thanks,
Wei
On Thu, Apr 22, 2021 at 11:27 PM Rekha Sekhar
wrote:
> Hi,
>
> Gentle reminder...it's
Hi,
For my experience is not a good idea to have two instances in the same server,
due to high consume of disk that solr have if can cause cpu increase or process
thread of solr increase and bad performance of the solr cluster.
I believe if you try with only one instance per machine, reducing fr
20 matches
Mail list logo
