Hi, kamaci:
That's great :) It's so nice of you to create the path and implement the
feature which are wanted for a long time :)
Best,
Jeffery Yuan
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-Elevation-Component-as-a-Managed-Resource-tp4312089p4313380.html
doesn't support this.
>
> Maybe you can vote for https://issues.apache.org/jira/browse/SOLR-6092, so
> add a patch for it :)
>
>
>
> --
> View this message in context: http://lucene.472066.n3.
> nabble.com/Query-Elevation-Component-as-a-Managed-
> Resource-tp4312089p431
I am looking for same things.
Seems Solr doesn't support this.
Maybe you can vote for https://issues.apache.org/jira/browse/SOLR-6092, so
add a patch for it :)
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-Elevation-Component-as-a-Managed-Resource
More I investigate the code more I grow sceptical it is feasible at all
with the current architecture
I will investifgate a bit more.
Cheers
On Mon, Sep 19, 2016 at 10:17 AM, Alessandro Benedetti <
abenede...@apache.org> wrote:
> Hi gents,
> I was thinking to use the que
re looking for the classic edismax with different field
> boosting instead than the query elevation component.
> Let us know and we can help you better!
>
> Cheers
>
> On Wed, Jul 27, 2016 at 4:49 AM, Ryan Yacyshyn <ryan.yacys...@gmail.com>
> wrote:
>
> > Hi
ic edismax with different field
boosting instead than the query elevation component.
Let us know and we can help you better!
Cheers
On Wed, Jul 27, 2016 at 4:49 AM, Ryan Yacyshyn <ryan.yacys...@gmail.com>
wrote:
> Hi everyone,
>
> I'm reading the docs on the query elevation component
Hi everyone,
I'm reading the docs on the query elevation component and some questions
came up:
Can I specify a field that the elevate component will look at, such as only
looking at the title field? My search handler (using eDisMax) is searching
across multiple fields, but if I only want
@lucene.apache.org
Sent: Friday, February 6, 2015 2:54:20 PM
Subject: Re: Query Elevation Component only elevates one document in elevateIds
list
Try sending the elevateIds as a comma delimited list.
Joel Bernstein
Search Engineer at Heliosearch
On Fri, Feb 6, 2015 at 2:17 PM, Charles Sanders csand
Try sending the elevateIds as a comma delimited list.
Joel Bernstein
Search Engineer at Heliosearch
On Fri, Feb 6, 2015 at 2:17 PM, Charles Sanders csand...@redhat.com wrote:
Using the Query Elevation Component in solr 4.8 and the elevateIds
parameter to force 3 documents to the top
The documentation is very unclear (at least to me) around Query Elevation
Component and filter queries (fq param)
The documentation for Solr 4.9 states:
The fq Parameter
Query elevation respects the standard filter query (fq) parameter. That is,
if the query contains the fq parameter, all
.nabble.com/Removal-of-unique-key-Query-Elevation-Component-tp4074624.html
Sent from the Solr - User mailing list archive at Nabble.com.
=authorarora arc/str
str name=author_sarora arc/str
str name=id4f65332d-49d9-497a-b88b-881da618f571/str/doc
--
View this message in context:
http://lucene.472066.n3.nabble.com/Removal-of-unique-key-Query-Elevation-Component-tp4074624.html
Sent from the Solr - User mailing list
Thanks! The author_s issue has been resolved.
Why are the other fields not getting indexed ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Removal-of-unique-key-Query-Elevation-Component-tp4074624p4074636.html
Sent from the Solr - User mailing list archive at Nabble.com.
. Care to tell where did you see this
discussed? I could not find anything. Also, did you manage to implement this
somehow?
thanks
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-Elevation-Component-tp4056856p4068308.html
Sent from the Solr - User mailing list archive
://lucene.472066.n3.nabble.com/Query-Elevation-Component-tp4056856p4068394.html
Sent from the Solr - User mailing list archive at Nabble.com.
.nabble.com/Query-Elevation-Component-tp4056856p4057065.html
Sent from the Solr - User mailing list archive at Nabble.com.
Perhaps you should describe the problem you are tryin to solve. There
may be other ways to solve it.
Upayavira
On Thu, Apr 18, 2013, at 01:08 AM, davers wrote:
I would like to use the Query Elevation Component. As I understand it
only
elevates based on term. I would also like it to consider
: In order for query elevation we define a type. do we really need index time
: analyzer for query elevation type.
If you declared an index analyzer, it would probably never be used in this
context (i don't remember the details of QEC off the top of my head)
but to be clear: regardless of
/
filter class=solr.LowerCaseFilterFactory/
/analyzer
/fieldType
darniz
--
View this message in context:
http://lucene.472066.n3.nabble.com/Do-we-need-index-analyzer-for-query-elevation-component-tp1077130p1077130.html
Sent from the Solr - User mailing list archive
19 matches
Mail list logo
