[jira] [Commented] (CONNECTORS-493) Metadata Support for JDBC Connector

["Karl Wright (JIRA)" <ji...@apache.org>]

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

Karl Wright commented on CONNECTORS-493:
----------------------------------------

It turns out you can already do this for single-valued metadata fields.  All returned columns in the "data" query are either required (e.g. $URLCOLUMN) or are considered a metadata value.  So, for example:

{code}
SELECT myidcolumn as $IDCOLUMN, myurlcolumn as $URLCOLUMN, mydatacolumn AS $DATACOLUMN, mydatecolumn AS mydatefield, mypricecolumn AS mypricefield ...
{code}

In the above example, metadata attributes "mydatefield" and "mypricefield" will be included in the document.  (On some databases, you may need to quote the names in order to preserve case.)

This only works for single-valued metadata fields, but for your particular use case that may well be sufficient.  If it is, I'll turn this ticket into a documentation ticket.

                
> Metadata Support for JDBC Connector
> -----------------------------------
>
>                 Key: CONNECTORS-493
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-493
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: JDBC connector
>    Affects Versions: ManifoldCF next
>            Reporter: Wolfgang Schreiber
>              Labels: Connector, JDBC, Metadata
>             Fix For: ManifoldCF next
>
>
> We need to map the contents of database columns of an Oracle database to separate index fields in Solr. Currently the JDBC connector does not support metadata; any entries in the Solr Field Mapping tab of a ManifoldCF job are ignored in case the repository connection is from type JDBC. Therefore we suggest the implementation of metadata support for JDBC connectors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira