Hi All,
I use Solr 8.4.1 and the latest solrj client.
There is a field let's which can have 3 different values. If I use the
admin UI, I write to the fq the following: filterName:"value1"
filterName:"value2" and it is working as expected.
If I use solrJ SolrQuery.addFilterQuery method and call it
You can do something like that if we are talking on the same filter query name.
addFilterQuery(String.format("%s:(%s %s)", filterName, value1, value2));
-Original Message-
From: Szűcs Roland
Sent: Tuesday, March 24, 2020 11:35 AM
To: solr-user@lucene.apache.org
Subject: how to add multi
Thanks Avi, it worked.
Raboah, Avi ezt írta (időpont: 2020. márc. 24., K,
11:08):
> You can do something like that if we are talking on the same filter query
> name.
>
> addFilterQuery(String.format("%s:(%s %s)", filterName, value1, value2));
>
>
> -Original Message-
> From: Szűcs Roland
I have added an edge ngram field to my index and get decent results
with partial words but the results appear randomly sorted and all
contain the same score. Ideally I would like to sort by shortest
ngram match within my other qualifiers.
Is there a canonical solution to this?
Thanks,
Matt
p.s.
Sort by the full field. You’ll need to copy to a field with keywordTokenizer
and lowercaseFilter (string_ci? assuming it’s not really a :”string”) type.
Best,
Erick
> On Mar 24, 2020, at 7:10 AM, matthew sporleder wrote:
>
> I have added an edge ngram field to my index and get decent results
>
Your original formation of the filter query has two problems:
1> you included a “+” in the value. My guess is that you misinterpreted the
URL you got back from the browser in the admin UI where a “+” is a
URL-encoded space. You’ll also see a bunch of %XX in the URL which are
other
## 24 March 2020, Apache Solr™ 8.5.0 available
The Lucene PMC is pleased to announce the release of Apache Solr 8.5.0.
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, fac
Congrats! -- H
On Tue, 24 Mar 2020 at 05:32, Alan Woodward wrote:
> ## 24 March 2020, Apache Solr™ 8.5.0 available
>
> The Lucene PMC is pleased to announce the release of Apache Solr 8.5.0.
>
> Solr is the popular, blazing fast, open source NoSQL search platform from
> the Apache Lucene project
Oh maybe a schema bug!
my string_ci:
going to try this instead:
Then I can probably kill the lowercasefilter on edgeytext:
On Tue, Mar 24, 2020 at 7:44 AM Erick Erickson wrote:
>
> Sort by the full field. You’ll n
Won’t work. String types are totally unanalyzed. Your string_ci fieldType is
what I was looking for.
No, you shouldn’t kill the lowercasefilter unless you want all of your searches
will then be case-sensitive.
So you should try:
q=edgy_text:whatever&sort=string_ci asc
Please use the admin>>pi
Okay I appreciate you responding.
Switching "slug" from "string_ci" class="solr.StrField" accomplished
about the same results, which makes sense to me now :)
The previous definition of string_ci was:
So lowercase + KeywordTokenizerFactory;
I am trying aga
I just updated to SOLR 8.5.0 on one of our test servers and I continue to get
the same issue/bug I described below. Below my description of the problem I
have also included the log message detail from Drupal.
This is the third time I have submitted this item. For the time being we will
contin
Hi!
I'm looking for some guidance on engineering a solution for searching
individual pages of PDF documents. I currently have a SolrCloud setup that uses
an external tika server to extract text data from PDFs. I'd like to be able to
search individual pages for search results and for the overall
Hi Phil,
The error you mention “The website encountered an unexpected error.
Please try again later.” isn't being generated by Solr but by Drupal. We
can't tell from the error text you're providing what the Drupal Solr
plugin is actually sending to Solr as a query I'm afraid: if you could
fig
Well, given the structure of an inverted index, how would you have a clue what
page the hit was on? You could conceivably index enough data with payloads and
the like, but that’d cause a lot more bloat than just indexing each page.
Using grouping would allow you to show, say, the top three pages
I have a use case that I would think is a common one but I cannot find any help
with this use case.
I am wanting to do a query that returns a list of records that I will display
in an html table in an app. This table only displays n records of the complete
data set, but is able to page through
I’m not sure I get the problem.
How do you “filter the records and only display those that match the filter
string”? Do you attach an fq clause to the original query? If so, the return
set _is_ the number of docs that match the filter (and the original query), and
the numFound from the original
Hi,
I think "debug" query parameter or "explain" document transformer will help
you
to know which fields and query conditions are boosted.
https://lucene.apache.org/solr/guide/7_5/common-query-parameters.html
https://lucene.apache.org/solr/guide/7_5/transforming-result-documents.html
Thanks,
Yas
18 matches
Mail list logo
