Hi there.
Are there any ideas?
Od: nc-tech-user
Wysłane: 19 lipca 2018 11:09
Do: solr-user@lucene.apache.org
Temat: Problem in QueryElevationComponent with solr 7.4.0
Hello.
We are using solr 6.6.2 and want to upgrade it to version 7.4.0.
But we have a
Hello.
We are using solr 6.6.2 and want to upgrade it to version 7.4.0.
But we have a problem with QueryElevationComponent when adding parameter
"elevateIds=..." and "fl=[elevated]"
Expample of query
/solr/products/select?omitHeader=true&elevateIds=1,2,3,4,5&
hen I try to create a core via the web interface I get:
> >
> > Error CREATEing SolrCore 'new_core': Unable to create core [new_core]
> > Caused by:
> > QueryElevationComponent missing config file: 'elevate.xml either:
> > /var/solr/d
1:53 AM, Leon STRINGER
wrote:
> Hi,
>
> I'm new to Solr and am trying to set up a newly installed Solr instance.
>
> When I try to create a core via the web interface I get:
>
> Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused
> b
Hi,
I'm new to Solr and am trying to set up a newly installed Solr instance.
When I try to create a core via the web interface I get:
Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused by:
QueryElevationComponent missing config file: 'elevate.xml ei
uniqueid:"sitecore://master/{450555a7-2cf7-40ec-a4ad-a67926d23c4a}?lang=en&ver=1";
Please suggest as I am struck with this..
Thanks,
G. Naresh Kumar
--
View this message in context:
http://lucene.472066.n3.nabble.com/Error-initializing-QueryElevationComponent-tp4133914p413716
The full details are farther down in the stack...
: null:org.apache.solr.common.SolrException: SolrCore 'master' is not
: available due to init failure: Error initializing QueryElevationComponent.
...
: Caused by: org.apache.solr.common.SolrException: Error in
Hi Team,
I am getting error "null:org.apache.solr.common.SolrException: SolrCore
'master' is not available due to init failure: Error initializing
QueryElevationComponent."
Please check below for configurations
elevate.xml
--
Scema.xml
--
Hello,
I was looking into "QueryElevationComponent" component.
As per the spec (http://wiki.apache.org/solr/QueryElevationComponent), if
config is not found in zookeepr, it should be loaded from data directory.
However, I see the bug. It doesn't seem to be working even in lates
t music ".
As in both the queries it contains "ipod" for which I want my desired doc
id's to be elevated.
I also tried changing in the QueryElevationComponent as:
First with this:
string"
Second time:
text_general
But no success.
Please correct me if I am doing the correc
t;ipod" as well as multi word query "apple
> ipod"?
>
> Thanks in advance!!!
> Niranjan
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/multi-word-search-for-elevator-QueryElevationComponent-not-working-tp4131016.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
/lucene.472066.n3.nabble.com/multi-word-search-for-elevator-QueryElevationComponent-not-working-tp4131016.html
Sent from the Solr - User mailing list archive at Nabble.com.
Thanks Hoss, that makes sense.
Anyway, I like the new paradigm better ... it allows for more
intelligent elevation control.
Cheers,
L
On 25/02/2014 23:26, Chris Hostetter wrote:
: What is seems that is happening is that excludeIds or elevateIds ignores
: what's in elevate.xml. I would hav
: What is seems that is happening is that excludeIds or elevateIds ignores
: what's in elevate.xml. I would have expected (hoped) that it would layer on
: top of that, which makes a bit more sense I think.
That's not how it's implemented -- i believe Joel implemented this way
intentional because
Hit the send button too fast ...
What is seems that is happening is that excludeIds or elevateIds ignores
what's in elevate.xml. I would have expected (hoped) that it would layer
on top of that, which makes a bit more sense I think.
Thanks,
Lajos
On 25/02/2014 22:58, Lajos wrote:
Guys,
I
Guys,
I've been testing out https://issues.apache.org/jira/browse/SOLR-5541 on
4.7RC4.
I previously had an elevate.xml that elevated 3 documents for a specific
query. My understanding is that I could, at runtime, exclude one of
those. So I tried that like this:
http://localhost:8080/solr/e
: Here are the results with the debugQuery=true; with debugging off, there are
: no results.
I don't understand what you mean. According to this response, with
debugQuery=true, there are not results matching your query...
:
: The elevated result appears in the queryBoost section but not i
I can guarantee you that the ID is unique and it exists in that index.
--
View this message in context:
http://lucene.472066.n3.nabble.com/QueryElevationComponent-results-only-show-up-with-debug-true-tp4087531p4087565.html
Sent from the Solr - User mailing list archive at Nabble.com.
0.0
0.0
0.0
--
View this message in context:
http://lucene.472066.n3.nabble.com/QueryElevationComponent-results-only-show-up-with-debug-true-tp4087531p4087554.html
Sent from the Solr - User mailing
, and the query you executed, and
you've said that you see evidence of the QueryElevationComponent working
according to the debug score explanation -- but you haven't shown us the
actaul response of your sample query so we can understand what exactly you
are getting in response.
w/o t
elevate.xml
https://server/profiles/html/profileView.do?key=ec6de388-fb7a-4397-9ed5-51760e4333d3";
/>
--
View this message in context:
http://lucene.472066.n3.nabble.com/QueryElevationComponent-results-only-show-up-with-debug-true-tp4087531.html
Sent from the Solr - User mailing list archive at Nabble.com.
e I saw that:
> >
> > "Distributed searching does not support the QueryElevationComponent,
> which
> > configures the
> > top results for a given query regardless of Lucene's scoring"
> >
> > is that still true for SolrCloud?
>
>
No, I'm fairly sure we added support a year or less back.
- Mark
On Apr 23, 2013, at 5:56 PM, Furkan KAMACI wrote:
> When I read Lucidworks' Solr Guide I saw that:
>
> "Distributed searching does not support the QueryElevationComponent, which
> configures the
>
When I read Lucidworks' Solr Guide I saw that:
"Distributed searching does not support the QueryElevationComponent, which
configures the
top results for a given query regardless of Lucene's scoring"
is that still true for SolrCloud?
In case anyone was wondering, the solution is to html encode the URL.
Solr didn't like the &'s; just convert them to & and it works!
--
View this message in context:
http://lucene.472066.n3.nabble.com/error-initializing-QueryElevationComponent-tp4035194p4036261.html
Sent fr
Hi,
I'm trying to test out the queryelevationcomponent.
elevate.xml is in the solrconfig.xml and it's in the conf directory.
I left the defaults.
I added this to the elevate.xml
https://opentextdev/cs/llisapi.dll?func=ll&objID=577575&objAction=download";
/>
i
: We are currently working on having Solr files read from HDFS. We extended
: some of the classes so as to avoid modifying the original Solr code and
: make it compatible with the future release. So here comes the question, I
: found in QueryElevationComponent, there is a piece of code checking
We want to put all files into a file system(HDFS). It is easy to maintain
if both config and index files are in the same place. You are right, we can
put a dummy one to by pass that. But I have another idea. We subclass the
Directory class to handle all the files access. If QueryElevationComponent
Is the goal to have the elevation data read from somewhere else? In
other words, why don't you want the elevate.xml to exist locally?
If you want to read the data from somewhere else, could you put a
dummy elevate.xml locally and subclass the QueryElevationComponent and
overrid
Hi there
We are currently working on having Solr files read from HDFS. We extended
some of the classes so as to avoid modifying the original Solr code and
make it compatible with the future release. So here comes the question, I
found in QueryElevationComponent, there is a piece of code checking
ing to newer versions.
>
> Thank you,
> Vinoth
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/QueryElevationComponent-not-working-in-Distributed-Search-tp4011785p4012382.html
> Sent from the Solr - User mailing list archive at Nabble.com.
the functionality of elevating to be
working for distributed search.
Can you pleae let me know if there is any mean that I can include this fix
without migrating to newer versions.
Thank you,
Vinoth
--
View this message in context:
http://lucene.472066.n3.nabble.com/QueryElevationComponent-not
the fix for the issue I have mentioned above is present in my
> version.
> 2. Is the problem of elevating in distributed search still exists.
>
> It will be of great help if anyone can share me your ideas with me.
>
> Thank you,
> Vinoth Asokan
>
>
>
> --
>
.nabble.com/QueryElevationComponent-not-working-in-Distributed-Search-tp4011785.html
Sent from the Solr - User mailing list archive at Nabble.com.
.nabble.com/QueryElevationComponent-not-working-in-Distributed-Search-tp4011780.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Apr 26, 2012, at 2:56 PM, srinir wrote:
> Can anyone help me out in understand the fix to QueryElevationComponent (in
> Solr 4.0) to make it work for distributed search.
>
>
https://github.com/apache/lucene-solr/commit/229ed68c31b346611c505ca9766871cec713a850
-
Can anyone help me out in understand the fix to QueryElevationComponent (in
Solr 4.0) to make it work for distributed search.
--
View this message in context:
http://lucene.472066.n3.nabble.com/QueryElevationComponent-and-distributed-search-tp3936998p3942221.html
Sent from the Solr - User
an give me an overview of how its fixed in solr
4.0. Is it with the modifications to the ElevationComparatorSource class ?
Thanks
Srini
--
View this message in context:
http://lucene.472066.n3.nabble.com/QueryElevationComponent-and-distributed-search-tp3936998p3939953.html
Sent from the Solr -
On Apr 25, 2012, at 5:54 PM, srinir wrote:
> Can anyone tell me whether support for distributed search is added to
> QueryElevationComponent in solr 4.0 ?
Yes.
>
> I looked at QueryElevationComponent code in trunk and it doesnt seem to have
> any code to support distribut
Can anyone tell me whether support for distributed search is added to
QueryElevationComponent in solr 4.0 ?
I looked at QueryElevationComponent code in trunk and it doesnt seem to have
any code to support distributed search. Am I missing something here ?
--
View this message in context:
http
Hi,
I am using solr 3.6. I saw in Solr wiki that QueryElevationComponent is not
supported for distributed search.
https://issues.apache.org/jira/browse/SOLR-2949
When I checked the above ticket, it looks like its fixed in Solr 4.0. Does
anyone have any idea when a stable version of solr 4.0
Walter Underwood [mailto:wun...@wunderwood.org] writes:
>On Mar 5, 2012, at 1:16 PM, Welty, Richard wrote:
>> Walter Underwood [mailto:wun...@wunderwood.org] writes:
>>> You may be able to have unique keys. At Netflix, I found that there were
>>> collisions between the movie IDs and the person
On Mar 5, 2012, at 1:16 PM, Welty, Richard wrote:
> Walter Underwood [mailto:wun...@wunderwood.org] writes:
>
>> You may be able to have unique keys. At Netflix, I found that there were
>> collisions between >the movie IDs and the person IDs. So, I put an 'm' at
>> the beginning of each movie I
Walter Underwood [mailto:wun...@wunderwood.org] writes:
>You may be able to have unique keys. At Netflix, I found that there were
>collisions between >the movie IDs and the person IDs. So, I put an 'm' at the
>beginning of each movie ID and a >'p' at the beginning of each person ID. Like
>ma
have a solr 3.5.0 server set up that needs to index several different
> document types, there is no common unique key field. so i can't use the
> uniqueKey declaration and need to disable the QueryElevationComponent.
>
> when i set this up with the uniqueKey, i mapped ids
e the QueryElevationComponent.
when i set this up with the uniqueKey, i mapped ids from the various database
tables to the id key temporarily just to get things working, but the results
from queries are showing me i really have to get rid of that hack. so i
commented out uniqueKey in schema.xm
- Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
> From: Romi
> To: solr-user@lucene.apache.org
> Sent: Fri, May 27, 2011 5:36:22 AM
> Subject: How to disable QueryElevationComponent
>
> Hi, in my indexed document i do not want a uniqueKey fiel
Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.mortbay.start.Main.invokeMain(Main.java:183)
> at org.mortbay.start.Main.start(Main.java:497)
> at org.mortbay.start.Main.
org.mortbay.start.Main.start(Main.java:497)
at org.mortbay.start.Main.main(Main.java:115)
-
Thanks & Regards
Romi
--
View this message in context:
http://lucene.472066.n3.nabble.com/How-to-disable-QueryElevationComponent-tp2992195p2992320.html
Sent from the Solr - User mailing list archive at Nabble.com.
Remove the component configuration from your solrconfig.
> Hi, in my indexed document i do not want a uniqueKey field, but when i do
> not give any uniqueKey in schema.xml then it shows an exception
> org.apache.solr.common.SolrException: QueryElevationComponent requires the
> sche
Hi, in my indexed document i do not want a uniqueKey field, but when i do not
give any uniqueKey in schema.xml then it shows an exception
org.apache.solr.common.SolrException: QueryElevationComponent requires the
schema to have a uniqueKeyField.
it means QueryElevationComponent requires a
what is QueryElevationComponent, why it is used. in my schema.xml if i do not
declare a uniqueKey then it shows the error
org.apache.solr.common.SolrException: QueryElevationComponent requires the
schema to have a uniqueKeyField
why so ??
-
Romi
--
View this message in context:
http
t;>
>>
>>
>> On 26 April 2010 19:13, Grant Ingersoll wrote:
>>
>>>
>>> On Apr 26, 2010, at 7:53 AM, Oliver Beattie wrote:
>>>
>>> > Hi all,
>>> >
>>> > I'm currently writing an application that uses Sol
t; > Hi all,
>> >
>> > I'm currently writing an application that uses Solr, and we'd like to
>> use
>> > something like the QueryElevationComponent, without having to specify
>> which
>> > results appear top. For example, what we reall
gt;
> On Apr 26, 2010, at 7:53 AM, Oliver Beattie wrote:
>
> > Hi all,
> >
> > I'm currently writing an application that uses Solr, and we'd like to use
> > something like the QueryElevationComponent, without having to specify
> which
> > results
On Apr 26, 2010, at 7:53 AM, Oliver Beattie wrote:
> Hi all,
>
> I'm currently writing an application that uses Solr, and we'd like to use
> something like the QueryElevationComponent, without having to specify which
> results appear top. For example, what we really
Hi all,
I'm currently writing an application that uses Solr, and we'd like to use
something like the QueryElevationComponent, without having to specify which
results appear top. For example, what we really need is a way to say "for
this search, include these results as part of the
y field
functionality of qf from dismax.
So we altered the query to boost certain phrases against a given field.
We were using QueryElevationComponent ("elevator" from solrconfig.xml) for one
particular entry we wanted at the top, but because we aren't using a pure q value,
el
field
> functionality of qf from dismax.
> So we altered the query to boost certain phrases against a given field.
> We were using QueryElevationComponent ("elevator" from solrconfig.xml) for
> one particular entry we wanted at the top, but because we aren't using a pure
Using Solr 1.4.
Was using the standard query handler, but needed the boost by field
functionality of qf from dismax.
So we altered the query to boost certain phrases against a given field.
We were using QueryElevationComponent ("elevator" from solrconfig.xml)
for one particular entry
Hi,
On May 12, 2009, at 12:33 , Nicolas Pastorino wrote:
Hi,
On May 7, 2009, at 6:03 , Noble Paul നോബിള്
नोब्ळ् wrote:
going forward the java based replication is going to be the preferred
means replicating index. It does not support replicating files in the
dataDir , it only supports re
at 7:08 PM, Nicolas Pastorino wrote:
On May 6, 2009, at 15:17 , Noble Paul നോബിള്
नोब्ळ् wrote:
Why would you want to write it to the data dir? why can't it be
in the
same place (conf) ?
Well, fact is that the QueryElevationComponent loads the
configuration file
( elevate.xm
15:17 , Noble Paul നോബിള് नोब्ळ् wrote:
>
>> Why would you want to write it to the data dir? why can't it be in the
>> same place (conf) ?
>
> Well, fact is that the QueryElevationComponent loads the configuration file
> ( elevate.xml ) either from the data dir, either fr
On May 6, 2009, at 15:17 , Noble Paul നോബിള്
नोब्ळ् wrote:
Why would you want to write it to the data dir? why can't it be in the
same place (conf) ?
Well, fact is that the QueryElevationComponent loads the
configuration file ( elevate.xml ) either from the data dir, either
fro
e core is reloaded . if
>> you post the new xml you will have to reload the core.
>>
>> A simple solution would be to write a RequestHandler which extends
>> QueryElevationComponent which can be a listener for commit and call an
>> super.inform() on that event
&g
Hello,
On May 6, 2009, at 15:02 , Noble Paul നോബിള്
नोब्ळ् wrote:
The elevate.xml is loaded from conf dir when the core is reloaded . if
you post the new xml you will have to reload the core.
A simple solution would be to write a RequestHandler which extends
QueryElevationComponent which
The elevate.xml is loaded from conf dir when the core is reloaded . if
you post the new xml you will have to reload the core.
A simple solution would be to write a RequestHandler which extends
QueryElevationComponent which can be a listener for commit and call an
super.inform() on that event
On
Hi,
On Apr 10, 2009, at 16:51 , Ryan McKinley wrote:
On Apr 10, 2009, at 7:48 AM, Nicolas Pastorino wrote:
Hello !
Browsing the mailing-list's archives did not help me find the
answer, hence the question asked directly here.
Some context first :
Integrating Solr with a CMS ( eZ Publish
On Apr 10, 2009, at 7:48 AM, Nicolas Pastorino wrote:
Hello !
Browsing the mailing-list's archives did not help me find the
answer, hence the question asked directly here.
Some context first :
Integrating Solr with a CMS ( eZ Publish ), we chose to support
Elevation. The idea is to be a
Hello !
Browsing the mailing-list's archives did not help me find the answer,
hence the question asked directly here.
Some context first :
Integrating Solr with a CMS ( eZ Publish ), we chose to support
Elevation. The idea is to be able to 'elevate' any object from the
CMS. This can be a
eption: Unknown FieldType: 'string' used in
QueryElevationComponent
at
org.apache.solr.handler.component.QueryElevationComponent.inform(QueryElevationComponent.java:151)
at
org.apache.solr.core.SolrResourceLoader.inform(SolrResourceLoader.java:388)
at org.apache.so
7; used in
QueryElevationComponent
at
org.apache.solr.handler.component.QueryElevationComponent.inform(QueryElevationComponent.java:151)
at
org.apache.solr.core.SolrResourceLoader.inform(SolrResourceLoader.java:388)
at org.apache.solr.core.SolrCore.(SolrCor
On Nov 23, 2008, at 3:06 PM, Paolo Ruscitti wrote:
Thanks Ryan for your answer.
The only thing that may be weird is that if you id field is named
"myid",
your elevate.xml file still refers to "id" as the unique key. Is
that what
you are refering to?
yes, my id field is named "myid", but
what may be wrong. If you want solr to
continue after configuration errors, change:
false in solr.xml
-
org.apache.solr.common.SolrException: Error initializing
QueryElevationComponent. at
org.apache.solr.handler.component.QueryElevation
hymm -- that *should* not be the case. The id field in
QueryElevationComponent uses the globally defined field:
SchemaField sf = core.getSchema().getUniqueKeyField();
...
idField = sf.getName().intern();
The only thing that may be weird is that if you id field is named
"
I have a question about QueryElevationComponent.
I'm trying to use it but it seems it works properly if, and only if, the id
field name in definition is '*id*'.
so if I have *myid*, it does not work.
Could you please tell me what I'm doing wrong?
thaks a lot
Paolo
- th
I don't know much about QueryElevationComponent but perusing the wiki docs
and trying it out with teh example configs i noticed that this URL didn't
produce the output i expected...
http://localhost:8983/solr/elevate?q=ipod&fl=id,price&sort=price+asc&forceElevation=tru
77 matches
Mail list logo
