Hi,
I want to use the Solr query elevation component. Let's say I want to
elevate "doc_id" when a user inputs the query "qwerty". I am able to get a
prototype to work by filling these values in elevate.xml and hitting the
Solr API with q="qwerty".
However, in our
Hi,
I would not use ID (uniqueKey) as signature field, query elevation would never
work properly with such a set up, change a document's content, and it 'll get a
new ID.
If i remember correctly this factory still deletes duplicates if signatureField
is not uniqueKey.
Regarding SOLR-3473
Hello,
I am running Solr Cloud 6.6.2 and trying to get query elevation and
deduplication (with SignatureUpdateProcessor) working at the same time.
The documentation for deduplication
(https://lucene.apache.org/solr/guide/6_6/de-duplication.html) does not
specify if the signatureField needs
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
Hi,
Can we access to Query Elevation Component as a Managed Resource? If not, I
would like to add that functionality.
Kind Regards,
Furkan KAMACI
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
Hi gents,
I was thinking to use the query elevation component sequentially to the
field collapsing.
This means I want to collapse over a field and then elevate docs for that
field.
Correct me if I am wrong, but we don't have this flexibility right now.
I think it is an easy change to give
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
with
the QueryElevationComponent, and to be invoked from the
DataImportHandler (DIH) Event Listeners, onImportStart or onImportEnd.
Github: https://github.com/kaismh/solr-elevate-creator
Blog Post:
https://medium.com/@kaismh/automated-solution-for-query-elevation-using-solr-a15ce88b2762
Please have a look at it, I
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
Hello,
I'm curious, why do you want the particular document to place second, not top,
of the result for a particular query?
Sorry this isn't the answer for your question, but I think you can implement it
rather easy
if you study the existing query elevation.
Koji
On 2016/07/08 19:59
A new requirement to get particular document as second result in result page.
For example, If the query is “coal”, this document(id: 222) should come as
second result.
Please let me know if you have any solution.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query
Hey guys, I just logged this bug and I wanted to raise awareness. If you
use the QueryElevationComponent, and ask for fl=[elevated], you'll get only
false if solr is using LazyDocuments. This looks even stranger when you
request exclusive=true and you only get back elevated documents, and they
@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
Using the Query Elevation Component in solr 4.8 and the elevateIds parameter to
force 3 documents to the top of the query results. Query and results included
below. In the results, you will see only one document of the three is in the
query results. It is the first document and it is marked
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
this message in context:
http://lucene.472066.n3.nabble.com/REST-API-for-Query-Elevation-in-Solr-tp4106596.html
Sent from the Solr - User mailing list archive at Nabble.com.
.
Does Solr provide REST API for elevate.xml file. Does Solr allow us to
change the elevate.xml file through java API other than manually editing
this file.
--
View this message in context:
http://lucene.472066.n3.nabble.com/REST-API-for-Query-Elevation-in-Solr-tp4106596.html
Sent from the Solr
.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.
outside of solr into our java code. As long as both
cores had some results to return for a given query elevation would work.
Thanks,
Ravi
On Sat, May 4, 2013 at 1:54 PM, varun srivastava varunmail...@gmail.com
wrote:
Hi Ravi,
I am getting same probelm . You got any solution ?
Thanks
Varun,
Since our cores were totally disjoint i.e. they pertain to two
different applications which may or may not have results for a given query,
we moved the elavation outside of solr into our java code. As long as both
cores had some results to return for a given query elevation would
of solr into our java code. As long as both
cores had some results to return for a given query elevation would work.
Thanks,
Ravi
On Sat, May 4, 2013 at 1:54 PM, varun srivastava varunmail...@gmail.com
wrote:
Hi Ravi,
I am getting same probelm . You got any solution ?
Thanks
Hi Ravi,
I am getting same probelm . You got any solution ?
Thanks
Varun
On Fri, Mar 29, 2013 at 11:48 AM, Ravi Solr ravis...@gmail.com wrote:
Hello,
We have a Solr 3.6.2 multicore setup, where each core is a complete
index for one application. In our site search we use sharded query
Hi ,
I am getting same exception as Ravi when using shard query containing
elevated terms. I am using solr 4.0.0 stable version which is suppose to
contain fix for this.
https://issues.apache.org/jira/browse/SOLR-2949
ava.lang.IndexOutOfBoundsException: Index: 1, Size: 0\n\tat
.nabble.com/Query-Elevation-Component-tp4056856p4057065.html
Sent from the Solr - User mailing list archive at Nabble.com.
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 the list of fq
parameters. Well really just one fq parameter. ex (fq=siteid:4) since I used
the same solr index for many sites. Is something like this available
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
Hello,
We have a Solr 3.6.2 multicore setup, where each core is a complete
index for one application. In our site search we use sharded query to query
two cores at a time. The issue is, If one core has docs but other core
doesn't for an elevated query solr is throwing a 500 error. I woudl
.472066.n3.nabble.com/Query-elevation-component-fails-tp4015793.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi Wenca,
I'm a bit late. but maybe you're still interested.
There's no such functionality in standard Solr. With sorting, this is
not possible, because sort functions only rank each single document,
they know nothing about the position of the others. And query elevation
is similar, you'll
.
It seems to me that the Query elevation component is not the right thing
for me. I don't know the query in advance (or the set of filter
criteria) and I don't know concrete product that will be the best for
the criteria within the order.
And also I don't think that I can construct a function
: 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
Hello,
In order for query elevation we define a type. do we really need index time
analyzer for query elevation type.
Let say we have some document already indexed and i added only the query
time analyzer, looks like solr reads the words in elevate.xml and map words
to the respective document
On Feb 10, 2010, at 8:46 PM, Jason Chaffee wrote:
Is it possible to do query elevation based on field?
Basically, I would like to search the same term on three different
fields:
q=field1:term OR field2:term OR field3:term
and I would like to sort the results by fourth
Is it possible to do query elevation based on field?
Basically, I would like to search the same term on three different
fields:
q=field1:term OR field2:term OR field3:term
and I would like to sort the results by fourth field
sort=field4+asc
However, I would like to elevate
43 matches
Mail list logo
