> PostCutOffZones:${zone}))"
>
>
> (Function query documentation here:
> https://cwiki.apache.org/confluence/display/solr/Function+Queries)
>
> Let me know if it works.
>
> Cheers,
> Diego
>
>
>
>
>
>
>
> On Tue, Aug 29, 2017 at 5:47 PM, B
I have one solr collection used for auto-suggestions. If I submit a query with
q="coffe", I will get a responses back with documents that have a field
suggestion="coffee", "coffee table", "coffee maker", etc. I want to know if
those suggestions would have results if I used them to query a
t;fq" : [
"{!frange l=NOW}CutOffDate",
"{!term f=PreCutOffZones}${zone}"
]
OR
"fq" : [
"{!frange u=NOW}CutOffDate",
"{!term f=PostCutOffZones}${zone}"
]
}
},
Thank you!
Brian Yee
t;fq" : [
"{!frange l=NOW}CutOffDate",
"{!term f=PreCutOffZones}${zone}"
]
OR
"fq" : [
"{!frange u=NOW}CutOffDate",
"{!term f=PostCutOffZones}${zone}"
]
}
},
Thank you!
Brian Yee
I have a similar question. I performing my feature extraction with the
following:
fl= [features+efi.query=bakeware 3-piece set]
I'm pretty sure the dash is causing my query to error. But I'm also not sure
how the spaces impacts the efi param. I tried putting the term in quotes, but
that does
Has anyone had experience tuning feature caches? Do any of the values below
look unreasonable?
--Brian
-Original Message-
From: Brian Yee [mailto:b...@wayfair.com]
Sent: Friday, October 20, 2017 1:41 PM
To: solr-user@lucene.apache.org
Subject: LTR feature extraction performance
When I upload, I can see my model when I hit
"solr/collection_name/schema/model-store/" but when I reload the collection,
it's gone.
Is there a size limit for LTR models? I have a 1.6mb / 49,000 line long
lambdamart model (that's what ranklib spit out for me) which I didn't think
would be a
Thanks Christine, that makes sense. I am currently working around the issue by
limiting how many trees Ranklib produces which reduces the file size.
--Brian
-Original Message-
From: Christine Poerschke (BLOOMBERG/ QUEEN VIC)
[mailto:cpoersc...@bloomberg.net]
Sent: Friday, December 01,
Hi Alessandro,
Unfortunately some of my most important features are query dependent. I think I
found an issue though. I don't think my features are being inserted into the
cache. Notice "cumulative_inserts:0". There are a lot of lookups, but since
there appear to be no values in the cache, the
/hits?
--Brian
-Original Message-
From: Brian Yee [mailto:b...@wayfair.com]
Sent: Tuesday, October 24, 2017 12:14 PM
To: solr-user@lucene.apache.org
Subject: RE: LTR feature extraction performance issues
Hi Alessandro,
Unfortunately some of my most important features are query dependent. I
I'm still having this issue. Does anyone have LTR feature extraction
successfully running and have cache inserts/hits?
--Brian
-Original Message-
From: Brian Yee [mailto:b...@wayfair.com]
Sent: Tuesday, October 24, 2017 12:14 PM
To: solr-user@lucene.apache.org
Subject: RE: LTR feature
So I've read a bunch of stuff on hard/soft commits and tlogs. As I understand,
after a hard commit, solr is supposed to delete old tlogs depending on the
numRecordsToKeep and maxNumLogsToKeep values in the autocommit settings in
solrconfig.xml. I am occasionally seeing solr fail to do this and
ur
target cluster and not lose any updates.
Later versions can do the full sync of the index and buffering is being removed.
Best,
Erick
On Tue, Jun 19, 2018 at 7:31 AM, Brian Yee wrote:
> Thanks for the suggestion. Can you please elaborate a little bit about what
> DISABLEBUFFER does? T
8 11:55 AM
To: solr-user
Subject: Re: tlogs not deleting
bq. Do you recommend disabling the buffer on the source SolrCloud as well?
Disable them all on both source and target IMO.
On Tue, Jun 19, 2018 at 8:50 AM, Brian Yee wrote:
> Thank you Erick. I am running Solr 6.6. From the
?
-Original Message-
From: Susheel Kumar [mailto:susheel2...@gmail.com]
Sent: Monday, June 18, 2018 9:12 PM
To: solr-user@lucene.apache.org
Subject: Re: tlogs not deleting
You may have to DISABLEBUFFER in source to get rid of tlogs.
On Mon, Jun 18, 2018 at 6:13 PM, Brian Yee wrote:
> So I've r
I enabled LTR feature extraction and response times spiked. I suppose that was
to be expected, but are there any tips regarding performance? I have the
feature values cache set up as described in the docs:
Do I simply have to wait for the cache to fill up and hope that response times
go
Thanks for the reply Alessandro. I'm starting to agree with you but I wanted to
see if others agree. It seems to me that the original score feature is not
useful because it is not normalized across all queries and therefore cannot be
used to compare relevance in different queries.
I wanted to get some opinions on using the original score feature. The original
score produced by Solr is intuitively a very important feature. In my data set
I'm seeing that the original score varies wildly between different queries.
This makes sense since the score generated by Solr is not
ick
On Thu, Feb 1, 2018 at 10:55 AM, Brian Yee <b...@wayfair.com> wrote:
> Hello,
>
> I want to use external file field to store frequently changing inventory and
> price data. I got a proof of concept working with a mock text file and this
> will suit my needs.
>
> Wha
Interesting. I will definitely explore this. Just so I'm clear, we can sort on
docValues, but not filter? Is there any situation where external file fields
would work better than docValues?
-Original Message-
From: Chris Hostetter [mailto:hossman_luc...@fucit.org]
Sent: Friday,
Hello,
I want to use external file field to store frequently changing inventory and
price data. I got a proof of concept working with a mock text file and this
will suit my needs.
What is the best way to keep this file updated in a fast way. Ideally I would
like to read changes from a Kafka
Hello,
I am trying to use Payload fields to store per-zone delivery dates for
products. I have an index where my documents are products and for each product
we want to store a date by when we can deliver that product for 1-100 different
zones. Since the payload() function only supports int and
I asked a question here about fast inventory updates last week and I was
recommended to use docValues with partial in-place updates. I think this will
work well, but there is a problem I can't think of a good solution for.
Consider this scenario:
InStock = 1 for a product.
InStock changes to 0
have to re-index the whole document And the only way to do that effectively
would be if all the fields are stored, which is not a requirement for in-place
updates.
Best,
Erick
On Mon, Feb 12, 2018 at 8:02 AM, Brian Yee <b...@wayfair.com> wrote:
> I asked a question here about fast inventor
"Zone06": 20180216,
"Zone07": 20180216,
"Zone08": 20180216,
"Zone09": 20180218,
"Zone10": 20180220,
"Zone11": 20180220,
"
I'm not sure if this will solve your problem, but you are using a very old
version of Ranklib. The most recent version is 2.9.
https://sourceforge.net/projects/lemur/files/lemur/RankLib-2.9/
-Original Message-
From: kusha.pande [mailto:kusha.pa...@gmail.com]
Sent: Thursday, February
26 matches
Mail list logo
