lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3029) Poor json formatting of spelling collation info
Date Thu, 29 Mar 2012 02:13:27 GMT


Yonik Seeley commented on SOLR-3029:

OK, this may be too much for 3.6.
I tried an example and it looks like there are a couple of places with this problem.

I edited solr.xml so the name field looked like
  <field name="name">Solr, the Enterprise Search Server solra solrb abcdefgx abcdefgy</field>

Then I tried the following spellcheck command:


        "collationQuery","abcdefgx solra",

Apologies if I'm misinterpreting some things - I don't have much experience with the spellchecker
stuff (other than trying to clean up the tests in the past).
- Unless order is really important, "suggestions" should be a map
- same for "collation" and "misspellingsAndCorrections"
- why is "collation" inside "suggestions" along with other words?  should this be one level
- why isn't this giving me multiple collations... am I misunderstanding the spellcheck.maxCollations
- why aren't multiple suggestions returned in misspellingsAndCorrections?  (and what's the
purpose of this seemingly redundant info anyway?)
- I briefly tried distributed search by adding &shards=localhost:8983/solr&shards.qt=/spell
and I get
    "msg":"isShard is only acceptable with search handlers",

> Poor json formatting of spelling collation info
> -----------------------------------------------
>                 Key: SOLR-3029
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: spellchecker
>    Affects Versions: 4.0
>            Reporter: Antony Stubbs
>            Priority: Blocker
>         Attachments: SOLR-3029.patch
> {noformat}
> "spellcheck": {
>     "suggestions": [
>     "dalllas",
>     {
> <snip>
>         {
>             "word": "canallas",
>             "freq": 1
>         }
>         ]
>     },
>     "correctlySpelled",
>     false,
>     "collation",
>     "dallas"
>     ]
> }
> {noformat}
> The correctlySpelled and collation key/values are stored as consecutive elements in an
array - quite odd. Is there a reason isn't not a key/value map like most things?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message