manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Updated] (CONNECTORS-552) Forced solr attributes in job specification and/or configuration
Date Fri, 16 Nov 2012 19:00:12 GMT


Karl Wright updated CONNECTORS-552:

    Affects Version/s: ManifoldCF 1.0.1
        Fix Version/s: ManifoldCF 1.1
             Assignee: Karl Wright

Haven't had time to work on this yet, but assigning to myself and triaging for 1.1 so it doesn't
fall off my queue.

> Forced solr attributes in job specification and/or configuration
> ----------------------------------------------------------------
>                 Key: CONNECTORS-552
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework crawler agent
>    Affects Versions: ManifoldCF 1.0.1
>            Reporter: Maciej Lizewski
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.1
> 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:

View raw message