On 10/22/07, Vadim Gritsenko <[EMAIL PROTECTED]> wrote: > > Text query syntax is the same as Lucene query syntax, > > except it does not use fields (using fields does not cause errors when > > parsing the query, but function will return false). > > Will it log this situation? Possibly, a WARNing?
No, currently it won't be logged. I agree it would be a good idea to inform user somehow about this situation, except I'm not sure if it is possible to do without going in depth of Lucene query parser. > > For XPath queries that use ftcontains function Xindice will attempt to > > optimize the query by using LuceneIndexer, if it is available and has > > a suitable pattern. If LuceneIndexer exists for the collection being > > queried, even if there is no suitable pattern, > > Does it also log this condition? I'd think at INFO level, say that indexer > available but this particular pattern is missing, so that user can check logs > and correct the situation. This behavior is consistent with queries that may be using other types of indexers. If query uses starts-with function and there is no value indexer for that pattern, it will not be reported. Is there any reason to treat new function differently? Natalia
