You are right of course, Shawn.
I added useDocValuesAsStored="false" to the IDX_ExpirationDate field
definition, and it no longer shows up
Thanks,
Rick
-Original Message-----
From: Hodder, Rick
Sent: Monday, August 05, 2019 2:02 PM
To: solr-user@lucene.apache.org
Subject: RE:
Hi Shawn,
>The DatePointField class defaults to docValues="true" and
>useDocValuesAsStored="true". Unless those parameters are changed,
>if the field is defined for a document, it will typically be in search results.
Just checking, I'm fine with ExpirationDate appearing in the results, it's th
I am migrating from SOLR 4.10.2 to 8.1.1. For some reason, in the 8.1.1 core, a
pdate index named IDX_ExpirationDate is appearing as a field in the search
results documents.
I have several other indexes that are defined and (correctly) do not appear in
the results. But the index I am having trou
have a SOLR 4.10.2 core, and I am upgrading to 8.1.1.
When I compare parsedQuery for a search 4.10 vs 8.1.1 I am seeing the query
wrapped with SynonymQuery(Synonym( in 8.1.1.
I think it may be because I replaced the deprecated SynonymFilterFactory with
SynonymGraphFilterFactory.
Is this a new fe
I have a SOLR 4.10.2 core, and I am upgrading to 8.1.1.
I created an 8.1.1 core manually using the default_config set , and then
brought over settings into the 8.1.1 schema
I have adjusted the schema.xml and solrconfig.xml, and I have the core
queryable in 8.1.1.
I have a field named Company:
I am using SOLR 7.1
ClassicSimilarityFactory
I have data in my core with field called CompanyName in an indexed field
IDX_CompanyName
Here are a few of the 900,000 rows in the core
Cityview
Citadel
CivicVentures
Clutch City Sports
Clutch City Sports & Entertainment
Clutch City Sports & Enter
I am using SOLR 7.1
ClassicSimilarityFactory
I have data in my core with field called CompanyName in an indexed field
IDX_CompanyName
Here are a few of the 900,000 rows in the core
Cityview
Citadel
CivicVentures
Clutch City Sports
Clutch City Sports & Entertainment
Clutch City Sports & Ente
I'm using SOLR 7.1 and I'm trying to set the similarity factory back to
ClassicSimilarityFactory so that it will behave like SOLR 6 or before.
In the document
https://lucene.apache.org/solr/guide/7_1/other-schema-elements.html#similarity
It says
This default behavior can be overridden by decla
I upgraded from SOLR 4.10 to SOLR 7.1
In the core, I have a string field called "company" and string field "year",
and I have an index on company called IDX_Company.
Here is the definition of the company field, and the definition of text_general
in my schema in 4.10
I'm converting SOLR 4.10.2 to SOLR 7.1
I have the following three strings in both SOLR cores
Action Technical Temporaries t/a CTR Corporation
Action Technical Temporaries
Action Technical Temporar
If I search
IDX_CompanyName: (Action AND Technical AND Temporaries AND t/a AND CTR AND
Corporatio
Classic Similarity helped, but the ranges of values don’t have a min near 0
like back in 4's version
Are there other attributes/elements to this factory that could get me back the
old functionality?
-Original Message-
From: Joël Trigalo [mailto:jtrig...@gmail.com]
Sent: Friday, Febru
Hi Shawn,
Thanks for your help - I'm still finding my way in the weeds of SOLR.
Combining everything into one query is what I'd prefer because as you said, one
would think that with everything in the same query, the score would organize
everything nicely.
>>Assuming you're using the default re
I am migrating from SOLR 4.10.2 to SOLR 7.1.
All seems to be going well, except for one thing: the score that is coming back
for the resulting documents is giving different scores.
The core uses a schema. Here's the schema info for the field that i am
searching on:
When searching maxrows=75
Hi Chris,
:Are you still using the same solrconfig.xml you had in 4.10, or did you switch
to using a newer sample/default set (or in some other way
modified) solrconfig.xml?
:I ask because even if you are using the ClassicIndexSchemaFactory, your update
processor chain might be using TrimFieldU
I am converting a SOLR 4.10 db to SOLR 7.1
It is NOT schemaless - so it uses a ClassicIndexSchemaFactory.
In 4.10, I have a field that is a phone number (here's the schema information
for the field):
When inserting documents into SOLR, there are some documents where the value of
Phone is an
15 matches
Mail list logo