: I'm not sure if you can do prefix queries with the fq parameter. You will
: need to use the 'q' parameter for that.
fq supports anything q supports ... with the QParser and local params
options it can be any syntax you want (as long as there is a QParser for
it)
-Hoss
Ben wrote:
The exception SOLR raises is :
org.apache.lucene.queryParser.ParseException: Cannot parse
'vector:_*[^_]*_[^_]*_[^_]*': Encountered ] at line 1, column 12.
Was expecting one of:
TO ...
RANGEIN_QUOTED ...
RANGEIN_GOOP ...
Ben wrote:
Passing in a RegularExpression like
You have to escape all special characters. Even [ to \[
Have a look here http://lucene.apache.org/java/2_4_0/queryparsersyntax.html
Uwe
2009/7/1 Ben b...@autonomic.net
I only just noticed that this is an exception being thrown by the
lucene.queryParser. Should I be mailing on the lucene
Yes, I had done that... however, I'm beginning to see now that what I am
doing is called a wildcard query which is going via Lucene's queryparser.
Lucene's query parser doesn't not support the regexp idea of character
exclusion ... i.e. I'm not trying to match [ I'm trying to express
Match as
You should split the strings at the comma yourself and store the values in a
multivalued field? Then wildcard search like A1_* are not a problem. I don't
know so much about facets. But if they work on multivalued fields that
should be then no problem at all.
Uwe
2009/7/1 Ben b...@autonomic.net
Is there a way in the Schema to specify that the comma should be used to
split the values up?
e.g. Can I specify my vector field as multivalue and also specify some
sort of tokeniser to automatically split on commas?
Ben
Uwe Klosa wrote:
You should split the strings at the comma yourself
To get the desired efffect I described you have to do the split before you
send the document to solr. I'm not aware of an analyzer that can split one
field value into several field values. The analyzers and tokenizers do
create tokens from field values in many different ways.
As I see it you have
I'm not quite sure I understand exactly what you mean.
The string I'm processing could have many tens of thousands of values...
I hope you aren't implying I'd need to split it into many tens of
thousands of columns.
If you're saying what I think you're saying, you're saying that I should
2009/7/1 Ben b...@autonomic.net
I'm not quite sure I understand exactly what you mean.
The string I'm processing could have many tens of thousands of values... I
hope you aren't implying I'd need to split it into many tens of thousands of
columns.
No, that is not what I meant. It will be
my brain was switched off. I'm using SOLRJ, which means I'll need to
specify multiple :
addMultipleFields(solrDoc, vector, vectorvalue, 1.0f);
for each value to be added to the multiValuedField.
Then, with luck, the simple wildcard query will be executed over each
individual value when
On Wed, Jul 1, 2009 at 5:07 PM, Ben b...@autonomic.net wrote:
my brain was switched off. I'm using SOLRJ, which means I'll need to
specify multiple :
addMultipleFields(solrDoc, vector, vectorvalue, 1.0f);
for each value to be added to the multiValuedField.
Then, with luck, the simple
Passing in a RegularExpression like [^_]*_[^_]* (e.g. matching
anything with an underscore in the string) using some code like :
...
parameters.add(fq, vector:[^_]*_[^_]*);
...
seems to cause problems for SOLR, I assume because of the [ or ^ character.
Can somebody please advise how to handle
The exception SOLR raises is :
org.apache.lucene.queryParser.ParseException: Cannot parse
'vector:_*[^_]*_[^_]*_[^_]*': Encountered ] at line 1, column 12.
Was expecting one of:
TO ...
RANGEIN_QUOTED ...
RANGEIN_GOOP ...
Ben wrote:
Passing in a RegularExpression like [^_]*_[^_]*
13 matches
Mail list logo
