[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
[ 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.
