manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramanan Sathiyanarayanan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-840) Job - Solr Mapping Improvement
Date Thu, 23 Jul 2015 02:43:04 GMT

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

Ramanan Sathiyanarayanan commented on CONNECTORS-840:
-----------------------------------------------------

Hi - We are using 2.1 version and I am not seeing this tab for Solr Output Connector. Is this
removed?
Is it possible to have one primary job that indexes data to Solr from a repository and one
or more jobs to do partial updates (only few fields in Solr). Usually repository data does
not changes often, but meta data changes a lot. So, we are planning to have a second job to
index some meta-data updates throughout the day and update the content only once a day.

Solr documentation - https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents

> Job - Solr Mapping Improvement
> ------------------------------
>
>                 Key: CONNECTORS-840
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-840
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 1.4.1
>            Reporter: Alessandro Benedetti
>            Assignee: Karl Wright
>            Priority: Minor
>              Labels: field, mapping, request, solr, update
>             Fix For: ManifoldCF 1.5
>
>         Attachments: CONNECTORS-840.patch
>
>
> "When you configure a job to use a Solr-type output connection, the Solr connection type
provides a tab called "Field Mapping". The purpose of this tab is to allow you to map metadata
fields as fetched by the job's connection type to fields that Solr is set up to receive. This
is necessary because the names of the metadata items are often determined by the repository,
with no alignment to fields defined in the Solr schema. You may also suppress specific metadata
items from being sent to the index using this tab. 
> Add a new mapping by filling in the "source" with the name of the metadata item from
the repository, and "target" as the name of the output field in Solr, and click the "Add"
button. Leaving the "target" field blank will result in all metadata items of that name not
being sent to Solr."
> In my opinion we should change the way a metadata field is suppressed.
> The most natural way is that we express only the mappings of the metadata fields we want
to keep.
> All the missing params will not be sent to Solr.
> The improvement will be :
> - same interface with a boolean flag in addition, this flag will specify if the missing
metadata fields not expressed should be sent to Solr with the original names or not sent at
all.
> In this way if we want to keep 3/100 metadata fields, we don't have to write 100 mapping
entries , 97 empty but simply 3 entries and activate the flag.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message