Hi,
Here's our example of exact match fields:
https://github.com/NatLibFi/finna-solr/blob/master/vufind/biblio/conf/schema.xml#L48
textProper_l requires a partial match from the beginning. textProper_lr
requires a full match. I'm not sure if this works for you, but at least
we have this
Hi Omer,
If you mean exact match with same number of words (Emir's), you can also
add an identifier in the beginning and end of the some other field like
title_exact. This can be done in your indexing script or using Pattern
Replace. During query side, you can use this identifier. For example,
There are two different interpretations of “exact match” going on here, don’t
be confused!
Emir’s version is “the text has to match the _entire_ input. So a field with “a
b c d” will NOT match “a b” or “a b c” or “b c", but only “a b c d”.
David’s version is “The text has to contain some
Hi Omer,
From performance perspective, it is the best if you index title as a single
token: KeywordTokenizer + LowerCaseFilter
If you need to query that field in some other way, you can index it differently
as some other field using copyField.
HTH,
Emir
--
Monitoring - Log Management -
if the query is in quotes it will work. also, not sure if youve been
following, but get rid of:
StopFilterFactory and all stopwords, or just make your stop word file empty
if you need it to work in non quotes, add them to the query post
submission ?
On Mon, Dec 2, 2019 at 3:44 PM OTH wrote:
>
First, attachments are aggressively stripped by the mail server, none of
your images came through.
Second, try adding =query to the URL and look at the parsed query
returned, that should provide some good hints.
Best,
Erick
On Thu, Jul 5, 2018 at 7:18 AM, Rushikesh Garadade <
Hello Gintas,
>From the first letter I've got that you use colon to separate fieldname and
text.
But here it's =, which is never advised in lucence syntax.
On Fri, Mar 17, 2017 at 2:37 PM, Gintautas Sulskus <
gintautas.suls...@gmail.com> wrote:
> Hi,
>
> Thank you for your replies.
> Sorry,
Hi,
Thank you for your replies.
Sorry, forgot to specify, I am using Solr 4.10.3 (from Cloudera CDH 5.9.0).
When I search for name:Guardian I can see both "Guardian EU-referendum"
and "Guardian US" in the result set.
The debugQuery results for both queries are identical
Hello,
I've tested on an old solr 4.3 instance and the schema and the field
definition are fine. I've also checked that only the
query nameExact:"Guardian EU-referendum" gives the result, the other one
you have commented (nameExact:"Guardian US") gives 0 hits. Maybe, you
forgot to re-index after
You can try to check debugQuery to understand how this query is parsed:
double quotes hardly compatible with KeywordTokenizer. Also you can check
which terms are indexed in SchemaBrowser. Also, there is Analysis page at
Solr Admin.
On Thu, Mar 16, 2017 at 8:55 PM, Gintautas Sulskus <
I may have provided too much background story for my question. What I am
trying to do at the core here, is an exact match on a single field. I do
this programmatically by reading the field value from the facet query and
setting it equal to the field name for a subsequent search.
if this is a
Shoot I just noticed the error in my original post which would certainly
cause confusion.
Instead of
query.addFacetField(fq);
I meant to write
query.setParam(fq, fg);
Sorry.
--
View this message in context:
: Exact match on string field with special characters
I may have provided too much background story for my question. What I am trying
to do at the core here, is an exact match on a single field. I do this
programmatically by reading the field value from the facet query and setting it
equal
When you call addFacetField, the parameter you pass it should just be the
fieldName. The fieldValue shouldn't come into play at all (unless I'm
misunderstanding what you're trying to do).
If you ever do need to escape a value for a query, you can use
Hi,
raw query parser or term query parser would be handy.
https://cwiki.apache.org/confluence/display/solr/Other+Parsers#OtherParsers-TermQueryParser
Ahmet
On Thursday, October 2, 2014 12:32 AM, tedsolr tsm...@sciquest.com wrote:
I am trying to do SQL like aggregation (GROUP BY) with solr
Maybe use dismax for this? Something like q={!dismax qf=field_name
mm=90%}query_string, or more verbosely and separately,
q=query_stringdefType=dismaxmm=90%
Erik
On Aug 19, 2014, at 2:43 AM, William Bell billnb...@gmail.com wrote:
If I have a long string, how do I match on 90% of
take the exact match ..?
Let me know if I am missing something.
Thanks
-Original Message-
From: Shawn Heisey [mailto:s...@elyograg.org]
Sent: Monday, July 07, 2014 8:22 PM
To: solr-user@lucene.apache.org
Subject: Re: Exact Match first in the list.
HI, I HAVE A situation where applying
HI, I HAVE A situation where applying below search rules.
When I search columns for the full text search. Product Variant Name,
the exact match has to be in the first list and other match like , product
or variant or name or any combination will be next in the results.
Any thoughts, why
Hi Chris, thanks for your reply and sorry for my poor explained question.
Here are some examples of indexed data (fieldname:propertyType):
Apartamento Padrão
Casa Padrão
Loft
Terreno
And some examples of the queries
propertyType:Apartamento Padrão
propertyType:apartamento-padrao
Can you show us examples of the types of data you are indexing, and the
types of queries you want to match? (as well as examples of queries you
*don't* want to match)
https://wiki.apache.org/solr/UsingMailingLists#Information_useful_for_searching_problems
Best guess, based on your problem
admin/analysis is your friend here. It'll tell you exactly what gets into
your
index and the transformations defined by each step along the way.
As Developer pointed out, you're using the ngram filter, that's almost
surely
what's causing the matches you're seeing.
FWIW,
Erick
On Tue, Oct 22,
Kumar
You might want to look into the 'pf' parameter:
https://cwiki.apache.org/confluence/display/solr/The+Extended+DisMax+Query+Parser
François
On Oct 21, 2013, at 9:24 AM, kumar pavan2...@gmail.com wrote:
I am querying solr for exact match results. But it is showing some other
You need to provide us with the fieldtype information..
If you just want to match the phrase entered by user, you can use
KeywordTokenizerFactory..
Reference:
http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters
Creates org.apache.lucene.analysis.core.KeywordTokenizer.
Treats the entire
Hi i am using field type configuration in the following way.
field name=fsw_title type=text_full_startwith_match indexed=true
stored=false multiValued=true omitNorms=true
omitTermFreqAndPositions=true /
fieldType name=text_full_startwith_match class=solr.TextField
analyzer type=index
For exact phrase match you can wrap the query inside quotes but this will
perform the exact match and it wont match other results.
The below query will match only : Okkadu telugu movie stills
http://localhost:8983/solr/core1/select?q=%22okkadu%20telugu%20movie%20stills%22
Since you are using
Hi,
use debugQuery=true and you'll probably immediately see how that
url:... stuff was interpreted. Maybe that : throws it off...
Otis
--
Solr ElasticSearch Support -- http://sematext.com/
Performance Monitoring -- http://sematext.com/spm
On Fri, Jul 26, 2013 at 4:31 PM, Furkan KAMACI
Is url a string field or is it text (and hence analyzed, which
typically removes all punctuation)?
A URL typically needs to be stored as both string and text so that the user
can do both exact match and keyword match.
-- Jack Krupansky
-Original Message-
From: Furkan KAMACI
Sent:
Try using the Solr's Analysis tool(http://localhost:8983/solr/analysis) to
check all the tokenizers/filters chain that modifies your query.
What's probably happening is that the field url uses a tokenizer or filter
that removes the *special* chars ://.
--
View this message in context:
Hi Bill.
So it seems you want an exact match to be first even if it is outside the
spatial region, right? Your suggested implementation suggests this. And
apparently you want to sort by distance, notwithstanding the exact match
being first. Although you don't have to do this as two queries, I
Thanks David !
On Sun, May 26, 2013 at 8:02 AM, David Smiley (@MITRE.org)
dsmi...@mitre.org wrote:
Hi Bill.
So it seems you want an exact match to be first even if it is outside the
spatial region, right? Your suggested implementation suggests this. And
apparently you want to sort
Try edismax with the PF2 option, which will automatically boost documents
that contains occurrences of adjacent terms as you have suggested.
See:
http://wiki.apache.org/solr/ExtendedDisMax
-- Jack Krupansky
-Original Message-
From: Pranav Prakash
Sent: Wednesday, August 01, 2012
Hello Roberto,
Exact match needs extra " (double-quotes) surrounding the exact
thing you want to query in the id field.
Give a try to a query like this :
id:"http://127.0.0.1:/my/personal/testuser/Personal
Documents/cal9.pdf"
See this wiki page :
Hi, are you sure you're using dismax query parser? Make sure you have the
parameter defType=dismax in your request.
*Juan*
On Thu, Aug 18, 2011 at 11:22 AM, jyn7 jyotsna.namb...@gmail.com wrote:
Hi,
I am trying to achieve an exact match search on a text field. I am using a
copy field and
I implemented both solutions Hoss suggested and was able to achieve the
desired results. I would like to go with
defType=dismax qf=myname pf=myname_str^100 q=Frank
but that doesn't seem to work if I have a query like myname:Frank
otherfield:something. So I think I will go with
That's a clever idea. I'll put something together and see how it turns out.
Thanks for the tip.
On Wed, Jul 27, 2011 at 10:55 PM, Chris Hostetter
hossman_luc...@fucit.orgwrote:
: With your solution, RECORD 1 does appear at the top but I think thats
just
: blind luck more than anything else
Keep in mind that if you use a field type that includes spaces (eg
StrField, or KeywordTokenizer), then if you're using dismax or lucene
query parsers, the only way to find matches in this field on queries
that include spaces will be to do explicit phrase searches with double
quotes.
These
Thanks Emmanuel for that explanation. I implemented your solution but I'm
not quite there yet. Suppose I also have a record:
RECORD 3
arr name=myname
strFred G. Anderson/str
strFred Anderson/str
/arr
With your solution, RECORD 1 does appear at the top but I think thats just
blind luck more
: With your solution, RECORD 1 does appear at the top but I think thats just
: blind luck more than anything else because RECORD 3 shows as having the same
: score. So what more can I do to push RECORD 1 up to the top. Ideally, I'd
: like all three records returned with RECORD 1 being the first
That is caused by the size of the documents. The principle is pretty
intuitive if one of your documents is the entire three volumes of The Lord
of the Rings, and you search for tree I know that The Lord of the Rings
will be in the results, and I haven't memorized the entire text of that book
:p
It
There's a JIRA issue assigned to this feature:
https://issues.apache.org/jira/browse/SOLR-1980
However, it's not yet implemented. Anyone?
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
On 17. mai 2011, at 15.51, Alex Grilo wrote:
Hi,
Can I make a query that
Hi Alex,
You need to define that field of type String in the schema and then search
for it. That will give you an exact match.
Regards,
Anuj
On Tue, May 17, 2011 at 7:21 PM, Alex Grilo a...@umamao.com wrote:
Hi,
Can I make a query that returns only exact match or do I have to change the
Try this: search term
--
View this message in context:
http://lucene.472066.n3.nabble.com/Exact-match-tp2952591p2952699.html
Sent from the Solr - User mailing list archive at Nabble.com.
You've got to change the fields to do it.
If you use a String field, then only exact matches will match, but
they'll be REALLY exact matches -- spacing, punctuation, etc.
Also, if you are using the lucene or dismax query parsers, you'll need
to phrase quote your query if it has any spaces in
Hi,
Using quoted means use this as a phrase, not use this as a literal. :)
I think copying to unstemmed field is the only/common work-around.
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
@lucene.apache.org
Subject: Re: Exact match on a field with stemming
Hi,
Using quoted means use this as a phrase, not use this as a literal. :) I
think copying to unstemmed field is the only/common work-around.
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem
search :: http
@lucene.apache.org
Subject: Re: Exact match on a field with stemming
Hi,
Using quoted means use this as a phrase, not use this as a literal. :) I
think copying to unstemmed field is the only/common work-around.
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem
search :: http
use a copyField and index the copy as type string, exact matches on
that field should then work as the text wont be tokenized
On Thu, Jun 17, 2010 at 3:13 PM, Pete Chudykowski
pchudykow...@shopzilla.com wrote:
Hi,
I'm trying with no luck to filter on the exact-match value of a field.
And when you do that, a best practice for fq'ing on a string field is:
fq={!raw f=field_name}value
That avoids query parsing and the hassles associated with escaping
special characters.
Erik
On Jun 17, 2010, at 6:22 PM, Joe Calderon wrote:
use a copyField and index the copy
Wonderful,
Thank you both.
Pete.
-Original Message-
From: Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Thursday, June 17, 2010 3:33 PM
To: solr-user@lucene.apache.org
Subject: Re: Exact match on a filter
And when you do that, a best practice for fq'ing on a string field
What do you get back when you specify debugQuery=on?
Best
Erick
On Mon, Apr 5, 2010 at 7:31 PM, Mark Fletcher
mark.fletcher2...@gmail.comwrote:
Hi,
I am using the dismax handler.
I have a field named *myfield* which has a value say XXX.YYY.ZZZ. I have
boosted myfield^20.0.
Even with such
Hi Eric,
Thanks many for your mail!
Please find attached the debugQuery results.
Thanks!
Mark
On Mon, Apr 5, 2010 at 7:38 PM, Erick Erickson erickerick...@gmail.comwrote:
What do you get back when you specify debugQuery=on?
Best
Erick
On Mon, Apr 5, 2010 at 7:31 PM, Mark Fletcher
Hi,
you need to quote your phrase when you search for 'Social News':
feedClass:Social News (URI encoded of course).
otherwise your request will become (I assume you're using a standard
query parser) feedClass:Social defaultField:News . Well that's the
idea.
It should then work using the type
thank worked for me, changed to:
http://localhost:8983/solr/select?q=feedClass:%22social%20news%22
and the matches are correct, I changed the feedClass field back to
type text.
A followup question has to do with sorting these results.
I have a field called title that I want the results
If feedClass acts as an identifier, better use string :)
use sort=title asc,score desc (not sort:)
J.
2009/11/4 Joel Nylund jnyl...@yahoo.com:
thank worked for me, changed to:
http://localhost:8983/solr/select?q=feedClass:%22social%20news%22
and the matches are correct, I changed the
How did you index your title field? It sholdn't be tokenized, see:
http://wiki.apache.org/solr/FAQ#Why_Isn.27t_Sorting_Working_on_my_Text_Fields.3F
http://wiki.apache.org/solr/FAQ#Why_Isn.27t_Sorting_Working_on_my_Text_Fields.3F
Best
Erick
On Wed, Nov 4, 2009 at 1:47 PM, Joel Nylund
that worked, thanks!
had to negate the score.
thanks
Joel
On Nov 4, 2009, at 1:57 PM, Jérôme Etévé wrote:
If feedClass acts as an identifier, better use string :)
use sort=title asc,score desc (not sort:)
J.
2009/11/4 Joel Nylund jnyl...@yahoo.com:
thank worked for me, changed to:
if you want to have exactly the same effect as the SQL equality, you
need more.
The phrase query matches anything with words Social followed by news.
It would also match feedClass:... finished. Social News In Our
Bulletin.
As noted elsewhere on the thread you need to query this on a field
Hi,
I am doing exact search in Solr .In Solr admin page I am
giving the search input string for search.
For ex: I am giving “channeL12” as search input string
in solr home page it displays search results as
doc
str name=urlhttp://rediff/field
str name=titlefirst/field
str
: Depending on your needs, you might want to do some sort of minimal
: analysis on the field (ignore punctuation, lowercase,...) Here's the
: text_exact field that I use:
Deans reply is a great example of what exact is a vague term.
with a TextField you can get an exact match using a simple
Hi Laurent,
I use the copy field approach and copy the text fields to a custom type
text_exact that I define in my schema.xml. This allows searching for
exact matches anywhere within the text field, which doesn't use tokens
injected by stemming, synonyms or other index-time filters.
In my
: I have indexed my data as custom123, customer, custom for the
: UserName field. I need to search the records for exact match, when I
: am trying to search with UserName:customer I am finding the records
: where UserName is custom123 and custom.
:
: As per my understanding solr splits the
Try using fieldtype string instead of text for the UserName
field. Then it will not be tokenized so it should only give exact
matches.
--
Steve
On Feb 2, 2009, at 2:27 AM, mahendra mahendra wrote:
Hi,
I have indexed my data as custom123, customer, custom for the
UserName field.
I
Look at what Solr returns when adding debugQuery=true for the parsed
query, and also consider how your fields are analyzed (their
associated type, etc).
Erik
On Jul 28, 2008, at 4:56 AM, Sunil wrote:
Hi,
I am sending a request to solr for exact match.
Example: (title:(Web 2.0
Hatcher [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2008 2:33 PM
To: solr-user@lucene.apache.org
Subject: Re: Exact match
Look at what Solr returns when adding debugQuery=true for the parsed
query, and also consider how your fields are analyzed (their
associated type, etc).
Erik
you're querying on.
Erik
Thanks,
Sunil
-Original Message-
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2008 2:33 PM
To: solr-user@lucene.apache.org
Subject: Re: Exact match
Look at what Solr returns when adding debugQuery=true for the parsed
query
65 matches
Mail list logo
