Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
From: "Beach, Daniel" <Daniel.Beach@spglobal.com>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Subject: Querying fields that don't exist in every collection
Thread-Topic: Querying fields that don't exist in every collection
Thread-Index: AdNIRUHEGD5Aqj9ZRIW5J7NnwAvgdw==
Date: Wed, 18 Oct 2017 19:15:18 +0000
Message-ID: <DM5PR10MB204345E511ACAB8851A72438F54D0@DM5PR10MB2043.namprd10.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_DM5PR10MB204345E511ACAB8851A72438F54D0DM5PR10MB2043namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Oct 2017 19:15:18.8960
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8f3e36ea-8039-4b40-81a7-7dc0599e8645
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR10MB2044
X-OriginatorOrg: spglobal.com
archived-at: Wed, 18 Oct 2017 19:15:36 -0000

--_000_DM5PR10MB204345E511ACAB8851A72438F54D0DM5PR10MB2043namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello all,

I'm running into an issue where adding a field to the qf changes the parsed=
 query if that field doesn't exist in the Solr index. Our use case for doin=
g this is that we have multiple collections and many of our queries leverag=
e aliases to search across several of them simultaneously. While we have a =
common group of fields that is shared across schemas, it is often the case =
that we need to use collection-specific fields to boost one content type ov=
er another.

Here is the query debug output from a query that only searches on existing =
fields. This is the intended outcome.

    q=3Dcompanies%20NOT%20brands*&qf=3DText&wt=3Djson&debug=3Dquery&defType=
=3Dedismax

    "rawquerystring":"companies NOT brands*",
    "querystring":"companies NOT brands*",
    "parsedquery":"(+(DisjunctionMaxQuery((Text:company)) -DisjunctionMaxQu=
ery((Text:brands*))))/no_coord",
    "parsedquery_toString":"+((Text:company) -(Text:brands*))",
    "QParser":"ExtendedDismaxQParser",


When a "BOGUS" field name is added to the second query suddenly the query o=
perators aren't interpreted correctly, and wildcards get dropped.

    q=3Dcompanies%20NOT%20brands*&qf=3DText%20BOGUS&wt=3Djson&debug=3Dquery=
&defType=3Dedismax

    "rawquerystring":"companies NOT brands*",
    "querystring":"companies NOT brands*",
    "parsedquery":"(+(DisjunctionMaxQuery((Text:company)) DisjunctionMaxQue=
ry((Text:not)) DisjunctionMaxQuery((Text:brand))))/no_coord",
    "parsedquery_toString":"+((Text:company) (Text:not) (Text:brand))",
    "QParser":"ExtendedDismaxQParser"


These results are from Solr 6.5.0 and 5.5, querying against a single collec=
tion endpoint. Is this Solr's expected functionality? Hopefully I'm just bl=
anking on something simple here.

Thanks,
Daniel Beach

________________________________

The information contained in this message is intended only for the recipien=
t, and may be a confidential attorney-client communication or may otherwise=
 be privileged and confidential and protected from disclosure. If the reade=
r of this message is not the intended recipient, or an employee or agent re=
sponsible for delivering this message to the intended recipient, please be =
aware that any dissemination or copying of this communication is strictly p=
rohibited. If you have received this communication in error, please immedia=
tely notify us by replying to the message and deleting it from your compute=
r. S&P Global Inc. reserves the right, subject to applicable local law, to =
monitor, review and process the content of any electronic message or inform=
ation sent to or from S&P Global Inc. e-mail addresses without informing th=
e sender or recipient of the message. By sending electronic message or info=
rmation to S&P Global Inc. e-mail addresses you, as the sender, are consent=
ing to S&P Global Inc. processing any of your personal data therein.

--_000_DM5PR10MB204345E511ACAB8851A72438F54D0DM5PR10MB2043namp_--