I think that it is fairly intuitive depending on what functionality people are trying to use.
For just a standard set of terms the big question is what should the default boolean operator be OR or AND. For the rest, it seems fairly "standard" when looking at other search engine syntax. Also, when a user wants the added functionality it's available just by reading some documentation. Searching by field, phrase queries, sub queries, fuzzy searches, boosting terms, proximity operators. >From my perspective selling a product that depends on the search engine, people ask about the complex search features, but often don't use them (although they would down grade the product unless it had them). It's very nice to be able to say we have the functionality, and it's one of the reasons why we choose Lucene because it was so full featured from the get go. --Peter On 6/2/02 9:40 PM, "Eric D. Friedman" <[EMAIL PROTECTED]> wrote: > I agree with Alex -- the QueryParser's syntax has become > at least as obfuscated as SQL, probably more so. It may > have started out simple, but it's not simple anymore. > > Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
