Re: Query Elevation Component as a Managed Resource
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 Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query Elevation Component as a Managed Resource
Hi Jeffery, I was looking whether an issue is raised for it or not. Thanks for pointing it, I'm planning to create a patch. Kind Regards, Furkan KAMACI On Mon, Jan 9, 2017 at 6:44 AM, Jeffery Yuan <yuanyun...@gmail.com> wrote: > 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-tp4312089p4313034.html > Sent from the Solr - User mailing list archive at Nabble.com. >
Re: Query Elevation Component as a Managed Resource
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-tp4312089p4313034.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: [Query Elevation Component] Elevate on collapsed field
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 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 the possibility of having the elevate > idField parametric. > By default will be the unique key. > > What do you think? > > https://issues.apache.org/jira/browse/SOLR-9531 > > Cheers > > -- > -- > > Benedetti Alessandro > Visiting card : http://about.me/alessandro_benedetti > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England > -- -- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
Re: The Query Elevation Component
Hi Alessandro, My mistake, I thought for a second there that the elevation component needed to actually searches through documents, which isn't the case. Thanks, Ryan On Wed, 27 Jul 2016 at 19:15 Alessandro Benedetti <abenede...@apache.org> wrote: > Hi Ryan, > can you explain this ? > " I'd like the search request to search multiple > fields, but only elevate if the query is found in one of the fields." > > You mean, that you want to apply the elevation component only if the user > selected a particular field in the query ? > If i remember well, you have the possibility of associate a list of > documents to each query you prefer in the elevation file. > > But maybe I misunderstood your question, are you actually thinking to boost > the results only if they have a certain match in a particular field ? > Because maybe you are 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 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 the elevate component to look > at > > one field, is this possible? I'd like the search request to search > multiple > > fields, but only elevate if the query is found in one of the fields. > > > > Also, is there a recommended way to analyze the query? For example, when > > using the queryFieldType parameter, I'd think I'd only want to use the > > KeywordTokenizer and maybe lowercasing. > > > > Thanks, > > Ryan > > > > > > -- > -- > > Benedetti Alessandro > Visiting card : http://about.me/alessandro_benedetti > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England >
Re: The Query Elevation Component
Hi Ryan, can you explain this ? " I'd like the search request to search multiple fields, but only elevate if the query is found in one of the fields." You mean, that you want to apply the elevation component only if the user selected a particular field in the query ? If i remember well, you have the possibility of associate a list of documents to each query you prefer in the elevation file. But maybe I misunderstood your question, are you actually thinking to boost the results only if they have a certain match in a particular field ? Because maybe you are 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 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 the elevate component to look at > one field, is this possible? I'd like the search request to search multiple > fields, but only elevate if the query is found in one of the fields. > > Also, is there a recommended way to analyze the query? For example, when > using the queryFieldType parameter, I'd think I'd only want to use the > KeywordTokenizer and maybe lowercasing. > > Thanks, > Ryan > -- -- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
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 the elevate component to look at one field, is this possible? I'd like the search request to search multiple fields, but only elevate if the query is found in one of the fields. Also, is there a recommended way to analyze the query? For example, when using the queryFieldType parameter, I'd think I'd only want to use the KeywordTokenizer and maybe lowercasing. Thanks, Ryan
Re: Query Elevation Component only elevates one document in elevateIds list
Ah that did it. I was adding them as an array of strings. Actually setting it
in SolrJ.
params.set(QueryElevationParams.IDS, sa);
Where sa is a String[]. Don't do that. :)
Much thanks Joel.
- Original Message -
From: Joel Bernstein joels...@gmail.com
To: solr-user@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...@redhat.com wrote:
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 as elevated. The other two are not in the results.
I've read the documentation here:
https://archive.apache.org/dist/lucene/solr/ref-guide/apache-solr-ref-guide-4.8.pdf
and here:
https://cwiki.apache.org/confluence/display/solr/The+Query+Elevation+Component
Based on the documentation, I think I have done this correctly, but the
results are not as expected. Any thoughts?
-Charles
Query **
$HOST/solr/collection1/select?enableElevation=truefl=uri,allTitlefl=%5Belevated%5Dstart=0q=oracleqf=allTitleqf=allTextelevateIds=https%3A%2F%
2Fapi.access.devgssci.devlab.phx1.redhat.com
%2Frs%2Farticles%2F216093elevateIds=https%3A%2F%
2Fapi.access.devgssci.devlab.phx1.redhat.com
%2Frs%2Farticles%2F395013elevateIds=https%3A%2F%
2Fapi.access.devgssci.devlab.phx1.redhat.com
%2Frs%2Farticles%2F725843wt=jsondefType=edismaxrows=10indent=trueforceElevation=true
** Query - decode so its easier to read *
$HOST/solr/collection1/select?enableElevation=truefl=uri,allTitlefl=[elevated]start=0q=oracleqf=allTitleqf=allTextelevateIds=
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/216093elevateIds=https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/395013elevateIds=https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/725843wt=jsondefType=edismaxrows=10indent=trueforceElevation=true
** Results **
{
responseHeader:{
status:0,
QTime:274,
params:{
enableElevation:true,
fl:[uri,allTitle,
[elevated]],
indent:true,
start:0,
q:oracle,
forceElevation:true,
qf:[allTitle,
allText],
wt:json,
elevateIds:[
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/216093;,
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/395013;,
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/725843;],
rows:10,
defType:edismax}},
response:{numFound:95055,start:0,maxScore:5.220278,docs:[
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/216093;,
allTitle:Storage Management for the Oracle Database on Red Hat
Enterprise Linux 6: Using ASM With or Without ASMLib,
[elevated]:true},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/838843
,
allTitle:Oracle Salt,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/838413
,
allTitle:Oracle iProcurement,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/839063
,
allTitle:Oracle TSAM,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/839073
,
allTitle:Oracle Tuxedo,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/838953
,
allTitle:Oracle Sourcing,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/837383
,
allTitle:Oracle Coherence,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/837363
,
allTitle:Oracle Clinical,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/837443
,
allTitle:Oracle Database,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/820373
,
allTitle:Oracle RAC,
[elevated]:false}]
},
spellcheck:{
suggestions:[]}}
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...@redhat.com wrote:
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 as elevated. The other two are not in the results.
I've read the documentation here:
https://archive.apache.org/dist/lucene/solr/ref-guide/apache-solr-ref-guide-4.8.pdf
and here:
https://cwiki.apache.org/confluence/display/solr/The+Query+Elevation+Component
Based on the documentation, I think I have done this correctly, but the
results are not as expected. Any thoughts?
-Charles
Query **
$HOST/solr/collection1/select?enableElevation=truefl=uri,allTitlefl=%5Belevated%5Dstart=0q=oracleqf=allTitleqf=allTextelevateIds=https%3A%2F%
2Fapi.access.devgssci.devlab.phx1.redhat.com
%2Frs%2Farticles%2F216093elevateIds=https%3A%2F%
2Fapi.access.devgssci.devlab.phx1.redhat.com
%2Frs%2Farticles%2F395013elevateIds=https%3A%2F%
2Fapi.access.devgssci.devlab.phx1.redhat.com
%2Frs%2Farticles%2F725843wt=jsondefType=edismaxrows=10indent=trueforceElevation=true
** Query - decode so its easier to read *
$HOST/solr/collection1/select?enableElevation=truefl=uri,allTitlefl=[elevated]start=0q=oracleqf=allTitleqf=allTextelevateIds=
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/216093elevateIds=https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/395013elevateIds=https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/725843wt=jsondefType=edismaxrows=10indent=trueforceElevation=true
** Results **
{
responseHeader:{
status:0,
QTime:274,
params:{
enableElevation:true,
fl:[uri,allTitle,
[elevated]],
indent:true,
start:0,
q:oracle,
forceElevation:true,
qf:[allTitle,
allText],
wt:json,
elevateIds:[
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/216093;,
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/395013;,
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/725843;],
rows:10,
defType:edismax}},
response:{numFound:95055,start:0,maxScore:5.220278,docs:[
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/articles/216093;,
allTitle:Storage Management for the Oracle Database on Red Hat
Enterprise Linux 6: Using ASM With or Without ASMLib,
[elevated]:true},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/838843
,
allTitle:Oracle Salt,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/838413
,
allTitle:Oracle iProcurement,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/839063
,
allTitle:Oracle TSAM,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/839073
,
allTitle:Oracle Tuxedo,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/838953
,
allTitle:Oracle Sourcing,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/837383
,
allTitle:Oracle Coherence,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/837363
,
allTitle:Oracle Clinical,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/837443
,
allTitle:Oracle Database,
[elevated]:false},
{
uri:
https://api.access.devgssci.devlab.phx1.redhat.com/rs/ecosystem/software/820373
,
allTitle:Oracle RAC,
[elevated]:false}]
},
spellcheck:{
suggestions:[]}}
Solr Query Elevation Component
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 results will be within that filter even if elevate.xml adds other documents to the result set. Now when I read this it made me think that only documents that are contained in the result set could be filtered. So when I apply a filter using the fq param that removes a document from the result set it should no longer be elevated. I have tested the elevator component using the elevateId's and elevate.xml and both still elevate documents that have been filtered from the result set using the fq parameter IF they exist in the result set before filtering. I would like to have the elevate component have an optional flag. Something like showFiltered=false where any results that have been filtered from the result set with the fq parameter will no longer be elevated. I have created the following ticket if anybody wants to take a stab at it: https://issues.apache.org/jira/browse/SOLR-6308 -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Query-Elevation-Component-tp4150531.html Sent from the Solr - User mailing list archive at Nabble.com.
Removal of unique key - Query Elevation Component
I want to index pdf files in solr 4.3.0 using the data import handler.
I have done the following:
My request handler -
requestHandler name=/dataimport
class=org.apache.solr.handler.dataimport.DataImportHandler
lst name=defaults
str name=configdata-config.xml/str
/lst
/requestHandler
My data-config.xml
dataConfig
dataSource type=BinFileDataSource /
document
entity name=f dataSource=null rootEntity=false
processor=FileListEntityProcessor
baseDir=C:\Users\aroraarc\Desktop\Impdo fileName=.*pdf
recursive=true
entity name=tika-test processor=TikaEntityProcessor
url=${f.fileAbsolutePath} format=text
field column=Author name=author meta=true/
field column=title name=title meta=true/
field column=text name=text/
/entity
/entity
/document
/dataConfig
Now when i tried to index the documents i got the following error
org.apache.solr.common.SolrException: Document is missing mandatory
uniqueKey field: id
Because i dont want any uniquekey in my case i disabled it as follows :
In solrconfig.xml i commented out -
searchComponent name=elevator class=solr.QueryElevationComponent
pick a fieldType to analyze queries
str name=queryFieldTypestring/str
str name=config-fileelevate.xml/str
/searchComponent
In schema.xml i commented out uniquekeyid/uniquekey
and added
fieldType name=uuid class=solr.UUIDField indexed=true /
field name=id type=uuid indexed=true stored=true default=NEW /
and in elevate.xml i made the following changes
elevate
query text=foo bar
doc id=4602376f-9741-407b-896e-645ec3ead457 /
/query
/elevate
When i do this the indexing takes place but the indexed docs contain an
author,s_author and id field. The document should contain author,text,title
and id field (as defined in my data-config.xml). Please help me out. Am i
doing anything wrong? and from where did this s_author field come?
doc
str name=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 archive at Nabble.com.
Re: Removal of unique key - Query Elevation Component
My guess is that you have a copyField element which copies the
author into an author_s field.
On Tue, Jul 2, 2013 at 2:14 PM, archit2112 archit2...@gmail.com wrote:
I want to index pdf files in solr 4.3.0 using the data import handler.
I have done the following:
My request handler -
requestHandler name=/dataimport
class=org.apache.solr.handler.dataimport.DataImportHandler
lst name=defaults
str name=configdata-config.xml/str
/lst
/requestHandler
My data-config.xml
dataConfig
dataSource type=BinFileDataSource /
document
entity name=f dataSource=null rootEntity=false
processor=FileListEntityProcessor
baseDir=C:\Users\aroraarc\Desktop\Impdo fileName=.*pdf
recursive=true
entity name=tika-test processor=TikaEntityProcessor
url=${f.fileAbsolutePath} format=text
field column=Author name=author meta=true/
field column=title name=title meta=true/
field column=text name=text/
/entity
/entity
/document
/dataConfig
Now when i tried to index the documents i got the following error
org.apache.solr.common.SolrException: Document is missing mandatory
uniqueKey field: id
Because i dont want any uniquekey in my case i disabled it as follows :
In solrconfig.xml i commented out -
searchComponent name=elevator class=solr.QueryElevationComponent
pick a fieldType to analyze queries
str name=queryFieldTypestring/str
str name=config-fileelevate.xml/str
/searchComponent
In schema.xml i commented out uniquekeyid/uniquekey
and added
fieldType name=uuid class=solr.UUIDField indexed=true /
field name=id type=uuid indexed=true stored=true default=NEW /
and in elevate.xml i made the following changes
elevate
query text=foo bar
doc id=4602376f-9741-407b-896e-645ec3ead457 /
/query
/elevate
When i do this the indexing takes place but the indexed docs contain an
author,s_author and id field. The document should contain author,text,title
and id field (as defined in my data-config.xml). Please help me out. Am i
doing anything wrong? and from where did this s_author field come?
doc
str name=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 archive at Nabble.com.
--
Regards,
Shalin Shekhar Mangar.
Re: Removal of unique key - Query Elevation Component
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.
Re: Query Elevation Component
davers wrote I want to elevate certain documents differently depending a a certain fq parameter in the request. I've read of somebody coding solr to do this but no code was shared. Where would I start looking to implement this feature myself? Davers, I am also looking into this feature. 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 at Nabble.com.
Re: Query Elevation Component
I have not implemented it yet. And I forget the exact webpage I found. But there was a person on that page discussing the same problem and said it was easy to implement a solution for it but he did not share his solution. If you figure it out let me know. -- View this message in context: http://lucene.472066.n3.nabble.com/Query-Elevation-Component-tp4056856p4068394.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query Elevation Component
I want to elevate certain documents differently depending a a certain fq parameter in the request. I've read of somebody coding solr to do this but no code was shared. Where would I start looking to implement this feature myself? -- View this message in context: http://lucene.472066.n3.nabble.com/Query-Elevation-Component-tp4056856p4057065.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Query Elevation Component
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 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 already? If not where would I start looking to code this feature myself? Any help is appreciated. -- View this message in context: http://lucene.472066.n3.nabble.com/Query-Elevation-Component-tp4056856.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Do we need index analyzer for query elevation component
: 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 usage, if you declare only one analyzer, it will be used as both the 'query' analyzer and the 'index' analyzer (even if it says 'type=query') -Hoss
Do we need index analyzer for query elevation component
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. in that case why would we need index time analyzers, unless i am missing something. Please let me know fieldType name=elevateKeywordsType class=solr.TextField positionIncrementGap=100 analyzer type=query tokenizer class=solr.WhitespaceTokenizerFactory/ 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 at Nabble.com.
