: print c.search(q='a_dt:["2005-08-01T00:00:00Z" TO "2005-08-01T23:59:59Z"]')
:
: Note that without the quotes around the date in the range query, I get
: an exception because the ':' causes the value to be truncated by the
: queryparser.
uhh... i'm not sure what you're talking about dude ... it
: However, when I run the following search
: foobar date:[2005-08-01T00:00:00Z TO 2005-08-01T23:59:59Z]
: I get values back that do not have a date value in the 08/01/2005 range.
unless you changed somethine else to mkae queries default to "all clauses
mandatroy" (aka: and "AND" query) that's se
> Does anyone know how to make string fields (solr.StrField) case
> insensitive for searching?
Yep. Switch it to a solr.TextField and use
solr.LowerCaseAnalyzerFactory. StrField will not work for anything
other than exact matching.
LowerCaseAnalyzer does some tokenization (on whitespace i thin
On Feb 2, 2007, at 4:29 PM, Yonik Seeley wrote:
One downside of doing joins is that it makes it pretty hard to
distribute/federate in the future because a document doesn't stand
alone.
The connection between objects is key in our library domain though.
A flat structure for tagging could be t
On Feb 2, 2007, at 11:36 PM, Erik Hatcher wrote:
It also provides a specific scope for a connection, rather than it
being possible for it to leak out (as an instance variable could).
It hides the details of the Connection constructor also (maybe to
cache instanced keyed by Solr URL?).
Yea
On Feb 2, 2007, at 11:22 PM, Edward Summers wrote:
On Feb 2, 2007, at 10:51 PM, Erik Hatcher wrote:
Ruby experts - know how I can code Solr::Connection to work like
this without an explicit method? (I'm still a Ruby newbie)
What purpose does this block passing serve?
Well, first and forem
On Feb 2, 2007, at 10:51 PM, Erik Hatcher wrote:
Ruby experts - know how I can code Solr::Connection to work like
this without an explicit method? (I'm still a Ruby newbie)
What purpose does this block passing serve?
//Ed
On Feb 2, 2007, at 5:29 PM, Yonik Seeley wrote:
On 2/2/07, Michael Kimsal <[EMAIL PROTECTED]> wrote:
I'm having a devil of a time getting date seaching to work
properly. I've
created a 'date' field in my schema, and I put values like
"2005-08-01T23:59:59Z" in it.
However, when I run the fol
Hmmm, Solr tries to be smart about splitting the query from the sort
specification.
If it sees a semicolon inside quotes (single or double), or backslash
escaped, then it will treat it as part of the query.
An immediate workaround would be to query for "jam's" or jam\'s
It would be helpful if yo
Search for the word jam's -- including the single quote. (%27 is a single
quote encoded for URL)
Here's the examples
http://10.0.101.11:8080/forsale/select/?q=jam%27s-- this works (i get
~20 hits back)
http://10.0.101.11:8080/forsale/select/?q=jam%27s;score%20desc --- this
doesn't (get 0
On 2/2/07, Michael Kimsal <[EMAIL PROTECTED]> wrote:
I'm having a devil of a time getting date seaching to work properly. I've
created a 'date' field in my schema, and I put values like
"2005-08-01T23:59:59Z" in it.
However, when I run the following search
foobar date:[2005-08-01T00:00:00Z TO 2
The index has a "type" field: "A" for archived objects and "C" for
collectibles. All the original objects are indexed in batch fashion
as type "A". Users collect objects and tags/annotates them. When a
user collects an object, a document of type "C" is indexed with the
original objects unique
One downside of doing joins is that it makes it pretty hard to
distribute/federate in the future because a document doesn't stand
alone.
A flat structure for tagging could be to add a
taguser and tag field to the actual document each time a user tagged a document.
- all collected objects
fa
I'm having a devil of a time getting date seaching to work properly. I've
created a 'date' field in my schema, and I put values like
"2005-08-01T23:59:59Z" in it.
However, when I run the following search
foobar date:[2005-08-01T00:00:00Z TO 2005-08-01T23:59:59Z]
I get values back that do not h
Before Solr had facets, I built my own implementation in a much
cruder and less performant way into Collex as custom request handlers.
Now the performance issue of warming up the cache needs to be
addressed. I'm going to upgrade Solr and adjust the application to
work with the built-in fac
On 2/2/07, Przemysław Brzozowski <[EMAIL PROTECTED]> wrote:
Does anyone know how to make string fields (solr.StrField) case
insensitive for searching?
Yep. Switch it to a solr.TextField and use
solr.LowerCaseAnalyzerFactory. StrField will not work for anything
other than exact matching.
-Mi
Hi,
I'm trying to get a custom tokenizer working, but I'm having some
problems. Per the instructions on various pages [1][2], I've been able
to develop and build the factory and tokenizer. However, when I start
solr up, I get a stack trace, that says "java.lang.NoClassDefFoundError:
org/apache/sol
On 2/2/07, rubdabadub <[EMAIL PROTECTED]> wrote:
Hi:
The following link seems to be broken from home page..
http://lucene.apache.org/solr/api/index.html
Yes, the nightly build failed, but the build script deleted the old
api docs, but didn't have new ones to replace it with.
I wonder if $? i
Hi
Does anyone know how to make string fields (solr.StrField) case
insensitive for searching?
Przemek Brzozowski
--
Jak to robi Rasiak - zobacz >> http://link.interia.pl/f19ee
Hi:
The following link seems to be broken from home page..
http://lucene.apache.org/solr/api/index.html
I have also found several other broken links that leads to trunk as
well as to api docs.
Regards
Hi:
Lets say you typed a wrong query i.e
http://localhost:8983/solr/select/?indent=on&q=video;inStock+asc+price+desc
or
http://localhost:8983/solr/select/?indent=on&q=name:
First one throws - Unknown sort order: asc price desc
Second one throws - Error parsing Lucene query
Above is correct beh
21 matches
Mail list logo
