: > 4) now it's easy to subclass StandardRequestHandler as
: > XmlQuerySyntaxRequestHandler or SurroundSyntaxRequestHandler
: > just by overriding getQUeryParser.
: Blech. All the other ideas are good, and rather orthogonal to
: declaring the syntax in the query itself.
yeah ... i didn't say i
On Jan 20, 2007, at 9:23 PM, Chris Hostetter wrote:
: > In the back of my mind, I've been thinking about *how* to support
: > multiple query syntaxes.
: > trying to add new parameters everywhere specifying the type
doesn't
: > seem like a great idea (way too many places).
: Good point. Yeah
Is there any easy way to split a string into a multi-field on the server:
given:
subject1; subject2; subject- 3
I would like:
subject1
subject2
subject- 3
Thanks for any pointers
ryan
On 1/21/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Is there any easy way to split a string into a multi-field on the server:
From an indexing perspective, yes... just assign a tokenizer that splits on ';'
I don't think we currently have such as configurable Tokenizer though.
The (hypothetic
Are you suggesting something like this:
...
On 1/21/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 1/21/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> Is there any easy way to split a string into a multi-field on the server:
From an ind
On 1/21/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Are you suggesting something like this:
...
Exactly, except for that bit... what's that?
-Yonik
On 1/21/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 1/21/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> Are you suggesting something like this:
>
>
> sortMissingLast="true" omitNorms="true">
>
>
>
>
>
> ...
>
>
Exactly, except fo
On 1/21/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Maybe the name is wrong, but it is something to tell the updateHandler
to use the tokenizer and filters (normally used for analysis) to
convert the single field into many fields.
I want something that is equivalent to splitting the string on t
>
> I want something that is equivalent to splitting the string on the
> client side and filling multiple *fields* not just tokens.
Oh, I was talking about indexing only.
aaah.
Why is it that multiple fields are needed? Multiple tokens are
indistinguishable from multiple fields during searc
On 1/21/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> >
> > I want something that is equivalent to splitting the string on the
> > client side and filling multiple *fields* not just tokens.
>
> Oh, I was talking about indexing only.
>
aaah.
> Why is it that multiple fields are needed? Multipl
>
> In the case I'm looking at, it would be cleaner and more safe to have
> it on the server side...
Safer? It precludes adding a subject with a ';' in it...
well, in *this* case it is :)
An aside: your need sounds like it's part of that much bigger issue of
processing documents and splitti
On 1/21/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
On Jan 20, 2007, at 9:23 PM, Chris Hostetter wrote:
> : > In the back of my mind, I've been thinking about *how* to support
> : > multiple query syntaxes.
> : > trying to add new parameters everywhere specifying the type
> doesn't
> : > seem lik
On 1/21/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
Another syntax option... something like
!term:myfield:my unescaped value all as a singe term
#term:
%term:
@term:
(basically, find a prefix that would be unlikely to appear as an
actual term or wildcard in lucene queryparser syntax)
More bra
On 1/21/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Deep within the "Update Plugin" discussion, Hoss and I agreed that
adding an interface and registry for DocumentParsers is a good idea:
interface SolrDocumentParser
{
Document parse(ContentStream content);
}
SolrDocumentParser parser = cor
14 matches
Mail list logo
