Picon

[jira] [Created] (SOLR-2997) Defining <uniqueKey> as a "long" type throws an error on startup

Defining <uniqueKey> as a "long" type throws an error on startup
----------------------------------------------------------------

                 Key: SOLR-2997
                 URL: https://issues.apache.org/jira/browse/SOLR-2997
             Project: Solr
          Issue Type: Bug
    Affects Versions: 4.0
            Reporter: Erick Erickson
            Priority: Blocker

I'm looking at a client index that has the <uniqueKey> defined as a long and Solr trunk (updated 31-Dec)
blows up with the stack traces below on startup. I insured that multiValued="false" when testing.

I don't quite know anything about other types. "string" and "lowercase" (both solr.TextField) work so I'm
guessing it's really "anything other than a TextField" that blows things up.

3.x allows this, so I'm calling it a blocker. It'll certainly mess up this client if/when they go to 4.x.

Dec 31, 2011 7:59:21 PM org.apache.solr.common.SolrException log
SEVERE: java.lang.NullPointerException
	at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:167)
	at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:129)
	at org.apache.solr.core.SolrCore.execute(SolrCore.java:1471)
	at org.apache.solr.core.QuerySenderListener.newSearcher(QuerySenderListener.java:59)
	at org.apache.solr.core.SolrCore$3.call(SolrCore.java:1248)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
(Continue reading)

Picon

[jira] [Commented] (SOLR-2997) Defining <uniqueKey> as a "long" type throws an error on startup


    [
https://issues.apache.org/jira/browse/SOLR-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178122#comment-13178122
] 

Yonik Seeley commented on SOLR-2997:
------------------------------------

bq. Caused by: java.lang.NumberFormatException: For input string: "MA147LL/A"

Quick guess: the existing elevate config uses string keys which aren't valid if the uniqueKey is a number?

> Defining <uniqueKey> as a "long" type throws an error on startup
> ----------------------------------------------------------------
>
>                 Key: SOLR-2997
>                 URL: https://issues.apache.org/jira/browse/SOLR-2997
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: Erick Erickson
>            Priority: Blocker
>
> I'm looking at a client index that has the <uniqueKey> defined as a long and Solr trunk (updated 31-Dec)
blows up with the stack traces below on startup. I insured that multiValued="false" when testing.
> I don't quite know anything about other types. "string" and "lowercase" (both solr.TextField) work so
I'm guessing it's really "anything other than a TextField" that blows things up.
> 3.x allows this, so I'm calling it a blocker. It'll certainly mess up this client if/when they go to 4.x.
> Dec 31, 2011 7:59:21 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NullPointerException
(Continue reading)

Picon

[jira] [Resolved] (SOLR-2997) Defining <uniqueKey> as a "long" type throws an error on startup


     [
https://issues.apache.org/jira/browse/SOLR-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erick Erickson resolved SOLR-2997.
----------------------------------

    Resolution: Not A Problem

Thanks Yonik, you nailed it!

Problem was I copied parts of the schema from the customer's 3.5 to a trunk installation (to work with your
suggestions for LukeRequestHandler if you must know <G>) but not the solrconfig. And I forgot all about
QEV issue. And of course the client's solrconfig.xml had QEV commented out.....
 That'll teach me to try to read through the stack trace more carefully, had I seen the QEV part of the trace it
might have jogged my memory.

> Defining <uniqueKey> as a "long" type throws an error on startup
> ----------------------------------------------------------------
>
>                 Key: SOLR-2997
>                 URL: https://issues.apache.org/jira/browse/SOLR-2997
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: Erick Erickson
>            Priority: Blocker
>
> I'm looking at a client index that has the <uniqueKey> defined as a long and Solr trunk (updated 31-Dec)
blows up with the stack traces below on startup. I insured that multiValued="false" when testing.
(Continue reading)


Gmane