[
https://issues.apache.org/jira/browse/CONNECTORS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473088#comment-13473088
]
Maciej Lizewski commented on CONNECTORS-552:
--------------------------------------------
to Ahmet - your solution works if there is not many values (like 3-10)
so it might work for putting "source" attribute, but still you have to
maintain as many solr connections as "source" values. If I would like
to add second fields (lets say "client") you would end up with
Cartesian product (n*m) connections which is *really* hard to
maintain. This is why I suggested this improvement.
to Karl - in my case adding this functionality to solr output
connector would be sufficient so we could go this way. This means that
on every job specification connected to solr output there will be
additional tab with forced attributes? If so - very good. Just thought
this could be helpful also in case of other output connectors, but
then there could be similar tab added to those output connectors.
> 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