: It was a surprise to discover that
: dateorigin_sort:
: is a syntax error, but
: dateorigin_sort:[ TO *]
: is legit. This says that there's a bug in the Lucene syntax parser?
If it was, it was in the old parser ... using trunk Solr (with Lucene
2.3.1) they both work for me.
Did
: 1. how to attach my own stylesheet to the output?
You can use the XSLTResponseWriter to get Solr to apply an XSLT before
writing hte response to the client...
http://wiki.apache.org/solr/XsltResponseWriter
...alternately there is a stylesheet param that can be used with the
: I read some documentation on the WordDelimterFilter. Just to clarify my
: thinking, I understand that if I use WordDelimiterFilter and search for a
: term like axd100 it will break it into two tokens axd and 100. But then
: when I do my search should Solr match the documents containing both
: Is there a way to specify that a dynamic field cannot have an empty string?
: With static fields, you can enforce this with 'required=true
: default=-1'.
Uh... are you sure about that? required=true just says there must be a
value supplied, the empty string is still a value. (i just verified
: If you go to http://tkb.mydns.jp:8899/exist/rest/db/new/tkb.xq you will see
: what I currently have. Just click search to search for the example, or maybe
: delete the last character so that you get more results (this is not released
I don't read Japanese so i'm really not sure what I'm
Hi,
I am aware of lucene but newbie in solr...
I want to swith my one of the product to solr for,
1. run time index ( the record which is indexed becomes searchable immediately)
2. faceted search
3. master slave architecture
But i have doubt that does solr supports runtime index in master slave
On Mar 17, 2008, at 3:20 AM, Bhavin Pandya wrote:
Hi,
I am aware of lucene but newbie in solr...
I want to swith my one of the product to solr for,
1. run time index ( the record which is indexed becomes searchable
immediately)
Immediately is a bit of a stretch, but say, within 1 minute
Hi,
1. run time index ( the record which is indexed becomes searchable
immediately)
Immediately is a bit of a stretch, but say, within 1 minute or so, that
is doable.
I think its cron job... so it will sync the snapshot of master index to all
slaves
suppose we have four slave
Hi,
I have a problem of returning an list of results which is sorted on a
average of ranks returned from aggregates.
the qury would be something like ?
q=product:p1+product:p2+product:p3; sort score desc
To explain Supose I have documents with fields Product, Manufacturer, Rank
and I want to
Hi,
I have the following use case. I could implement the solution but
performance is affected. I need some smart ways of doing this.
Use Case :
Incoming data has two fields which have values like 'WAL MART STORES INC'
and 'wal-mart-stores-inc'.
Users can search the data either in 'walmart'
: It appears that adding sort functions would be done in Lucene, and not
: in solr. I'm not sure I want to go down that path, so I'm wondering
: if there's a way to accomplish this with solr. From recent
: discussions, it sounds like I might be able to do this with some boost
: magic.
Hi,
I'm working on a custom SearchComponent to display context stored in
payloads. I noticed that both the FacetComponent and the
HighlightComponent are tightly coupled with the ResponseBuilder through
the frequent use of doFacet and doHighlight. If I am building a
component with
I have 30 millions document indexed and tried sort by sequenceid which is
unique over the document.
I am experiencing very slow than sort by pub_date.
sequenceid is not defined as unique key in the schema.xml and there is the
unique key defined in schema.xml - item_id.
Anyone knows why?
Thanks,
The first time sort on a particular field is normally slow.
Subsequent sorts on the same field should be just as fast.
-Yonik
On Mon, Mar 17, 2008 at 4:42 PM, Jae Joo [EMAIL PROTECTED] wrote:
I have 30 millions document indexed and tried sort by sequenceid which is
unique over the document.
Hi,
I'm working on an application where the documents in the solr index
might only be relevant to users within a date range. We are storing a
start_date and an end_date in the index for each document that defines
the range for which the document is relevant. These date ranges in the
document
Nevermind, this is actually easy:
StartDate: [NOW TO NOW+30DAY] AND EndDate: [NOW TO NOW+30DAY]
-Nathan
On 3/17/08, Nathan Woodhull [EMAIL PROTECTED] wrote:
Hi,
I'm working on an application where the documents in the solr index
might only be relevant to users within a date range. We are
Actually, it doesn't. This does not take care of documents that extend
beyond the bounds of the current 30 day window... which are relevant
even though both the start and end are not within the range.
For instance: A document with a start_date of 1/1/08 and an end_date
of 3/1/08 should still
where 'distribution' of queried single-value field is extemely low, such as
fq=country:USA
Standard query q=country:USA is 1 times faster than less intelligent
q=id:[* TO *]fq=country:USA
Does anyone experience similar staff?
It's probably specific to [* TO *] which was stupid in this
Tricia Williams wrote:
Hi,
I'm working on a custom SearchComponent to display context stored in
payloads. I noticed that both the FacetComponent and the
HighlightComponent are tightly coupled with the ResponseBuilder through
the frequent use of doFacet and doHighlight. If I am building
On Mon, Mar 17, 2008 at 5:59 PM, Ryan McKinley [EMAIL PROTECTED] wrote:
[* TO *] iterates over all docs in the index, so that is not a fair
comparison...
It's equivalent to iterating over all docs in the index, but it's
worse since it iterates over all terms in the field and then all docs
for
Hi,
Sorry I could have sworn I read a snippet about this somewhere and
having trouble tracking it back down. Im interested in (possible)
using DataImportHandler to run MultiCore (n+ indexes) ... what Id like
to do is have 2 indexes (/news and /video) and run them in a single
instance
Hi Jon,
For general information related to using multiple cores, see
http://wiki.apache.org/solr/MultiCore
Apart from that, configuration of DataImportHandler does not change in
any way when using it with multiple cores. The only thing that changes
is the URL which has the core name now e.g.
Hi Nathan,
We had a similiar problem but with a numeric field and we had solved
it by keeping both start and end range as one multivalued field. Then
your first query will get you the desired results.
On Tue, Mar 18, 2008 at 2:52 AM, Nathan Woodhull [EMAIL PROTECTED] wrote:
Actually, it
Bhavin - one of the nice things about Solr's index replication is that
*typically* only changed/new index files are sent from master to slave, and
this is typically cheap.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Bhavin Pandya [EMAIL
24 matches
Mail list logo