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

Karl Wright commented on CONNECTORS-552:
----------------------------------------

Each output connector has the ability to define a per-job tab that will appear 
in each job that uses an output connection of that type.  So I think one 
possibility would be to add such a tab to the Solr output connector.  It sounds 
like this would meet your specific needs, correct?

The other possibility would be adding a general tab that appears on every job 
regardless of output connection, which forces specific metadata attributes to 
specific values.  This tab would not be associated with any particular 
repository or output connector.  That too would work for you, right?

I'm not sure which approach would be better, but bear in mind that the second 
possibility will likely require a schema change, while the first possibility 
would not.




                
> Forced solr attributes in job specification and/or configuration
> ----------------------------------------------------------------
>
>                 Key: CONNECTORS-552
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-552
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework crawler agent
>            Reporter: Maciej Lizewski
>
> Would be nice if there was a globally managed tab (like "connection" or 
> "scheduling") for job specification (or configuration) allowing to force some 
> solr attributes. It could look and work similar to "Solr Field Mapping" 
> allowing to specify name=value associations.
> I am thinking about such case:
> Index all documents from repository X, and set then "source" attribute to 
> "repository X". Then I could filter results to those that came from specified 
> source. But I think there can be other possibilities, like: index all 
> documents from windows share and set them field "client" to "Client X", 
> because all documents there are associated with one client and I would like 
> to have filters, facets on such field (and I cannot fetch such value from 
> documents because people never set meta tags...).
> Real life: I have three document sources: Samba share with some project 
> documents, internal wiki system, mantis bug tracker. I would like to query 
> Solr for "all documents from wiki, which contain phrase XXXX".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to