Several ideas, all shots in the dark because to analyze this we
need the schema definitions and the result of your query with
=true added. In particular you'll see the "parsed query"
section near the bottom, and often the parsed query isn't
quite what you think it is. In particular this is often
Oh my. I'll leave it to the DIH guys to suggest whether there's
something that can be done with pure DIH, and offer a couple
of alternatives:
1> You could put a MappingCharFilterFactory in your analysis
chain. In the mapping file you can map things like:
"%20" => " " that would work with DIH as
Additional experimenting lead me to the discovery that /dataimport does
*not* index words with a preceding %20 (a URL-encoded space), or in fact
*any* preceding %xx encoding. I can probably replace each %20 with a
'+' in each record of my database -- the dataimporter/indexer doesn't
sneeze at
Greetings!
So, I've created my first index and am able to search programmatically
(through SolrJ) and through the Web interface. (Yay!) I get non-empty
results for my searches!
My index was built from database records using
/dataimport?command=full-import. I have 9936 records in the table
