nce. (Also,
unfortunately, we do not have the luxury of using super big
machines/storage -- so it's always a balancing act for us.)
Best,
Edd
--------
Edward Turner
On Tue, 10 Nov 2020 at 16:22, Walter Underwood
wrote:
> By far the simplest solution is to leave stopwords in th
WordsFrom("This is pretend index or query
data")
// wordsForSolr = "pretend index query data"
Off the top of my head, this will by-pass position issues.
I will give this a go, but was wondering whether this is something others
have done?
Best wishes,
Edd
Ed
ur analysis setup?
Any help would be much appreciated -- getting phrase queries to work is an
important use-case of ours.
Kind regards and thank you in advance,
Edd
Edward Turner
That's really good and helpful info, thank you. Perfect.
Best wishes,
Edd
On Mon, 28 Sep 2020, 5:53 pm Shawn Heisey, wrote:
> On 9/28/2020 8:56 AM, Edward Turner wrote:
> > By removing the copyfields, we've found that our index sizes have reduced
> > by ~40% in s
Hi all,
We have recently switched to using edismax + qf fields, and no longer use
copyfields to allow us to easily search over values in multiple fields (by
copying multiple fields' values to the copyfield destinations, and then
performing queries over the destination field).
By removing the copy
ication, before sending it to Solr, which I suppose isn't the way to do
it.
Many thanks,
Edd
--------
Edward Turner
On Mon, 17 Aug 2020 at 21:23, Markus Jelsma
wrote:
> Hello Edward,
>
> You asked for the 'Lucene Query representation of the client's query'
erver
side in Solr?)
Kind regards,
Edd
--------
Edward Turner
On Mon, 17 Aug 2020 at 15:06, Markus Jelsma
wrote:
> Hello Edward,
>
> Yes you can by extending ExtendedDismaxQParser [1] and override its
> parse() method. You get the main Query object through super.parse()
Hi all,
Thanks for all your help recently. We're now using the edismax query parser
and are happy with its behaviour. We have another question which maybe
someone can help with.
We have one use case where we optimise our query before sending it to Solr,
and we do this by manipulating the client's
Goodness me, woops, yes, it was a typo -- sorry fo the confusion. We're
indeed exploring qf, rather than pf! :). So far it's looking promising!
Thanks for your eagle-eye spotting!
Best,
Edd
--------
Edward Turner
On Wed, 12 Aug 2020 at 13:15, Erick Erickson
wrote:
&g
e pf field (thanks to Alexandre R. for
this) to automatically search on multiple fields, rather than relying on df.
Kind regards,
Edd
--------
Edward Turner
On Tue, 11 Aug 2020 at 15:44, Erick Erickson
wrote:
> Have you explored edismax?
>
> > On Aug 11, 2020,
e".
e.g.,
q=id:value1 // hits id field, which uses the "simple" type
q=value1 // hits content field, which uses the "complex" type
... so results might differ between the two queries
I hope this clarifies our question?
Best,
Edd
Edward Turner
On T
Hi all,
Is it possible to have multiple "df" fields? (We think the answer is no
because our experiments did not work when adding multiple "df" values to
solrconfig.xml -- but we just wanted to double check with those who know
better.) The reason we would like to do this is that we have two main fi
Hi Chris,
Good info, thank you for that!
> What's your UI & middle layer like for this application and
> eventual "download" ?
I'm working in a team on the back-end side of things, where we providing a
REST API that can be used by clients, which include our UI, which is a
React JS based app with
= 150M. A key challenge for us is that
in the life sciences, when more sequencing data comes in, it's possible for
our data-sets to grow extremely quickly. Currently it doubles every 18
months or so (and today we have about 200M records, so not super big right
now).
Best,
Edd
--
ring docs evict lower scoring docs.
>
> So I think CursorMark is your best bet.
>
> Best,
> Erick
>
> > On Oct 1, 2019, at 3:59 AM, Edward Turner wrote:
> >
> > Hi all,
> >
> > As far as I understand, SolrCloud currently does not allow the us
Hi all,
As far as I understand, SolrCloud currently does not allow the use of
sorting by the pseudofield, score in the /export request handler (i.e., get
the results in relevancy order). If we do attempt this, we get an
exception, "org.apache.solr.search.SyntaxError: Scoring is not currently
suppo
16 matches
Mail list logo