You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@manifoldcf.apache.org by "Karl Wright (JIRA)" <ji...@apache.org> on 2010/06/22 20:48:55 UTC

[jira] Created: (CONNECTORS-49) Solr connector metadata and id field can collide, causing multiple id fields to be passed in

Solr connector metadata and id field can collide, causing multiple id fields to be passed in
--------------------------------------------------------------------------------------------

                 Key: CONNECTORS-49
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-49
             Project: Lucene Connector Framework
          Issue Type: Bug
          Components: Lucene/SOLR connector
            Reporter: Karl Wright


If a document has a metadata field called "id", or "ID", or "Id", or any such thing, the Solr connector will blithely send both the document id and the metadata id along to Solr, which will then crap out with an error.  The solution is to map the metadata "id" field to something else, which should be determined by the solr connection definition.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (CONNECTORS-49) Solr connector metadata and id field can collide, causing multiple id fields to be passed in

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright reassigned CONNECTORS-49:
-------------------------------------

    Assignee: Karl Wright

> Solr connector metadata and id field can collide, causing multiple id fields to be passed in
> --------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-49
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-49
>             Project: Lucene Connector Framework
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>
> If a document has a metadata field called "id", or "ID", or "Id", or any such thing, the Solr connector will blithely send both the document id and the metadata id along to Solr, which will then crap out with an error.  The solution is to map the metadata "id" field to something else, which should be determined by the solr connection definition.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (CONNECTORS-49) Solr connector metadata and id field can collide, causing multiple id fields to be passed in

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CONNECTORS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881604#action_12881604 ] 

Karl Wright commented on CONNECTORS-49:
---------------------------------------

As per discussions in connectors-user, it's probably important to also provide a declaration of the name of the solr "id" field in the configuration, with a default value of "id".  Longer term, maybe Solr can learn to accept a generic notion of primary key, but that's as yet undecided.



> Solr connector metadata and id field can collide, causing multiple id fields to be passed in
> --------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-49
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-49
>             Project: Lucene Connector Framework
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>
> If a document has a metadata field called "id", or "ID", or "Id", or any such thing, the Solr connector will blithely send both the document id and the metadata id along to Solr, which will then crap out with an error.  The solution is to map the metadata "id" field to something else, which should be determined by the solr connection definition.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (CONNECTORS-49) Solr connector metadata and id field can collide, causing multiple id fields to be passed in

Posted by "Karl Wright (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CONNECTORS-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Wright resolved CONNECTORS-49.
-----------------------------------

    Resolution: Fixed

r959167.  Tested, except in the context of an actual crawl.


> Solr connector metadata and id field can collide, causing multiple id fields to be passed in
> --------------------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-49
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-49
>             Project: Lucene Connector Framework
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>
> If a document has a metadata field called "id", or "ID", or "Id", or any such thing, the Solr connector will blithely send both the document id and the metadata id along to Solr, which will then crap out with an error.  The solution is to map the metadata "id" field to something else, which should be determined by the solr connection definition.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.