Hmmm, with 4.x I get much different behavior than you're describing, what version of Solr are you using?
Besides Alex's comments, try adding &debug=query to the url and see what comes out from the query parser. A quick glance at the code shows that DefaultAnalyzer is used, which doesn't do any analysis, here's the javadoc... /** * Default analyzer for types that only produces 1 verbatim token... * A maximum size of chars to be read must be specified */ so it's much like the "string" type. Which means I'm totally perplexed by your statement that 300 and letters return a hit. Have you perhaps changed the field definition and not re-indexed? The behavior you're seeing really looks like somehow WordDelimiterFilterFactory is getting into your analysis chain with settings that don't mash the parts back together, i.e. you can set up WDDF to split on letter/number transitions, index each and NOT index the original, but I have no explanation for how that could happen with the field definition you indicated.... FWIW, Erick On Tue, May 28, 2013 at 7:47 AM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > What does analyzer screen say in the Web AdminUI when you try to do that? > Also, what are the tokens stored in the field (also in Web AdminUI). > > I think it is very strange to have TextField without a tokenizer chain. > Maybe you get a standard one assigned by default, but I don't know what the > standard chain would be. > > Regards, > > Alex. > On 28 May 2013 04:44, "Michał Matulka" <michal.matu...@gowork.pl> wrote: > >> Hello, >> >> I've got following problem. I have a text type in my schema and a field >> "name" of that type. >> That field contains a data, there is, for example, record that has >> "300letters" as name. >> >> Now field type definition: >> <fieldType name="text" class="solr.TextField"></**fieldType> >> >> And, of course, field definition: >> <fieldname="name"type="text"**indexed="true"stored="true"/> >> >> yes, that's all - there are no tokenizers. >> >> And now time for my question: >> >> Why following queries: >> >> name:300 >> >> and >> >> name:letters >> >> are returning that result, but: >> >> name:300letters >> >> is not (0 results)? >> >> Best regards, >> Michał Matulka >>
