Monday 12 July 2010 3:20:34 pm

Indeed, in ezfind 2.2 you can define dedicated field types for attributes in a facet context ... this was introduced exactly for having both meaningful search results (in that case you usually want this "break up") and facets/sorting (where you want verbatim strings).

What datatype is used for keywords? You are using either eZ Find 2.0 or eZ Find 2.1+ with a text field judging from your results

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Tuesday 27 July 2010 5:45:30 am

In case you do want to tune schema.xml, here is the information you need. Leave in the line:

<dynamicField name="*_t" type="text" indexed="true" stored="true" multiValued="true" termVectors="true"/>

but add a definition underneath that one for your own field, and replace type="text" in type="long", e.g.:

<field name="attr_dc_coverage_t" type="long" indexed="true" stored="true" multiValued="true"/>

Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.

Tuesday 05 October 2010 11:18:26 am

This looks interesting too: on http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.WordDelimiterFilterFactory check out the entry for
solr.WordDelimiterFilterFactory, which has an option preserveOriginal="1", which causes the original token to be indexed without modifications (in addition to the tokens produced due to other options).

for example:

<fieldtype name="subword" class="solr.TextField">       <analyzer type="query">           <tokenizer class="solr.WhitespaceTokenizerFactory"/>           <filter class="solr.WordDelimiterFilterFactory"                 generateWordParts="1"                 generateNumberParts="1"                 catenateWords="0"                 catenateNumbers="0"                 catenateAll="0"                 preserveOriginal="1"                 />
etc...

Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.

Wednesday 06 October 2010 1:47:02 am

Damn still not working :(

I added those variables in ezfind.ini (which seems to be cleaner than modifying system wide schema.xml) :

• DatatypeMap[ezstring]=string
• DatatypeMapSort[ezstring]=string
• DatatypeMapFilter[ezstring]=string
• DatatypeMapFacet[ezstring]=string
• Default=string

Then rerun updatesearchindexsolr.php -s $siteaccess_name --clean-all

My ezstring attribute still return facets truncated values.

EZP is Great

Thursday 07 October 2010 2:44:21 am

I tried to put this everywhere but tweaking of ezfind.ini or schema.xml seems to have no effect on what solr or ezfind returns.

Even deleting or bugging schema.xml doesn't change anything : After running "updatesearchindexsolr.php" all facets results remains the same !!!

Could someone tell me which schema.xml do we have to edit ? Here is the list i found :

• ./java/solr/conf/schema.xml
• ./java/solr.multicore/eng-GB/conf/schema.xml
• ./java/solr.multicore/fre-FR/conf/schema.xml
• ./java/solr.multicore/nor-NO/conf/schema.xml

None of those seems to be used ? if i delete all those files nothing changes.

EZP is Great

Monday 18 October 2010 8:04:30 am

Thank you. In fact i haven't restarted solr.

What do you mean by deleting previous index and commit ? Commit = restart solr with new schema.xml ?

When i add my directive : <field name="attr_ville_t" type="long" indexed="true" stored="true" multiValued="true"/>

Then solr is crashing : (curl error 7)

EZP is Great

Monday 18 October 2010 9:00:20 am

This looks interesting too: on http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.WordDelimiterFilterFactory check out the entry for
solr.WordDelimiterFilterFactory, which has an option preserveOriginal="1", which causes the original token to be indexed without modifications (in addition to the tokens produced due to other options).

for example:

<fieldtype name="subword" class="solr.TextField">       <analyzer type="query">           <tokenizer class="solr.WhitespaceTokenizerFactory"/>           <filter class="solr.WordDelimiterFilterFactory"                 generateWordParts="1"                 generateNumberParts="1"                 catenateWords="0"                 catenateNumbers="0"                 catenateAll="0"                 preserveOriginal="1"                 />
etc...

This is what i get after adding "preserveOriginal="1" to schema.xml on line 221 (then restarting solr, then removing extension/ezfind/java/(...)/data/*, then rerunning updatesolrindex) :

<body><h2>HTTP ERROR: 500</h2><pre>Severe errors in solr configuration.  Check your log files for more detailed information on what may be wrong.  If you want solr to continue after configuration errors, change:    &lt;abortOnConfigurationError&gt;false&lt;/abortOnConfigurationError&gt;  in solr.xml

EZP is Great

Monday 18 October 2010 9:31:51 am

Ok Patrick.

Thanks all those informations are a great help for me to finally being able to use ezfind on production projects.

My attribute is a simple "ezstring" attribute holding city names.

If i just add : DatatypeMapFacet[ezstring]=lckeyword in ezfind.ini then its not changing anything. after rerunning updatesolrindex.

My results are still truncated like this :

• Paris become Pari
• Rennes become Renn
• ...etc

Do i need to insert : DatatypeMapFacet[ezstring]=string ?

EZP is Great

Tuesday 19 October 2010 10:57:42 am

You were right i had a loading problem with my ezfind.ini....extension loading order problem...:(

Now everything works with your directives !

Thanx a lot !

EZP is Great

Friday 01 April 2011 7:15:42 am

I solved using http://projects.ez.no/ezfsolrdocumentfieldobjectrelation and making some modifications to it.

Now my problem is filtering with white space words...

Bye