Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [smila-dev] Solr - indexing fields are configured twice 
Hi Andreas,

the idea of the CoreFields sequence was to create a mapping. So record attributes or attachments don't have to use the same name than Solr index fields defined in schema.xml. Also you're able to tell SMILA to look for an attribute or attachment in record while creating the SolrDocument to index. 
Nevertheless I like the idea of using SolrAdministration.getFieldNames() as a default. I'll keep it in mind for Solr 4.0 integration.

Kind regards

Peter


-----Original Message-----
From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Andreas Weber
Sent: Freitag, 30. November 2012 15:09
To: Smila project developer mailing list
Subject: [smila-dev] Solr - indexing fields are configured twice

Hi guys,

I just wondered if there is any reason that we configure the Solr index fields twice:
  1. in solr configuration's schema.xml
  2. in the configuration of the SolrIndexPipelet (see AddPipeline.bpel)

Wouldn't it be better to configure that in the schema.xml and read the configured fields in the SolrIndexPipelet via SolrManager / SolrAdministration.getFieldNames() ?

And if so, does it make sense to leave the "CoreFields" parameter in the Pipelet and use the schema.xml fields only as a default if parameter isn't set?
(Maybe because you don't want to index values for all configured fields, but this seems to be a very theoretic use case...)

Cheers,
  Andreas




_______________________________________________
smila-dev mailing list
smila-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-dev

Back to the top