I just checked in the last part of those changes that should eliminate any restriction on key. But, that last part dealt with escaping keys that contained whitespace or } Your example really should have worked after my previous 2 commits. Perhaps not all of the servers got successfully upgraded? Can you try trunk again now?
-Yonik http://lucenerevolution.org Lucene/Solr Conference, Boston Oct 7-8 On Wed, Sep 8, 2010 at 6:28 PM, Ron Mayer <r...@0ape.com> wrote: > Yonik Seeley wrote: >> On Tue, Sep 7, 2010 at 8:31 PM, Ron Mayer <r...@0ape.com> wrote: >>> Short summary: >>> * Mixing Facets and Shards give me a NullPointerException >>> when not all docs have all facets. >> >> https://issues.apache.org/jira/browse/SOLR-2110 >> >> I believe the underlying real issue stemmed from your use of a complex >> key "involvement/race_facet". > > Thanks! Yes - that looks like the actual reason, rather than what > I was guessing. I spent a while this morning trying to reproduce the > problem with a simpler example, and wasn't able to - probably because > I overlooked that part. > > > I see changes have been made (based on comments in) SOLR-2110 and > SOLR-2111, so I'll try with the current trunk...... > [trying now with trunk as of a few minutes ago] > ....Looking much better. > > I'm seeing this in the log files: > SEVERE: Exception during facet.field of > {!terms=$involvement/gender_facet__terms}involvement/gender_facet:org.a > pache.lucene.queryParser.ParseException: Expected identifier at pos 20 > str='{!terms=$involvement/gender_facet__ > terms}involvement/gender_facet' > at > org.apache.solr.search.QueryParsing$StrParser.getId(QueryParsing.java:718) > at > org.apache.solr.search.QueryParsing.parseLocalParams(QueryParsing.java:165) > ... > but at least I'm getting results, and results that look right for both the > body of > the document and for most of the facets. > > Perhaps next thing I try will be simplifying my keys for my own sanity as much > as for solr's. >
