tracker issue : CF-3042129

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 84082:Allow setting of default operator (AND|OR) during creation of Solr index, instead of having folks modify the generated schema

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/

Reporter/Name(from Bugbase): Sami Hoda / Sami Hoda (samihoda2)

Created: 09/08/2010

Components: Text Search, Solr

Versions: 9.0.1

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Minor / Unknown

Locale/System: English / Platforms All

Vote Count: 3

Problem:

Allow setting of default operator (AND|OR) during creation of Solr index, instead of having folks modify the generated schema.xml for each collection. This is a very important setting. Also surface JVM settings for Solr, like for CF instance, to CFAdmin.Also, if there is a way to support case-insensitive boolean operators, that would rock (or to transform them before sending to Solr). See: http://www.bytestopshere.com/post.cfm/lessons-learned-moving-from-verity-to-solr-part-1
Method:

Allow setting of default operator (AND|OR) during creation of Solr index, instead of having folks modify the generated schema.xml for each collection. This is a very important setting. Also surface JVM settings for Solr, like for CF instance, to CFAdmin.Also, if there is a way to support case-insensitive boolean operators, that would rock (or to transform them before sending to Solr). See: http://www.bytestopshere.com/post.cfm/lessons-learned-moving-from-verity-to-solr-part-1
Result:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3042129

External Customer Info:
External Company:  
External Customer Name: Sami Hoda
External Customer Email: 46E545A3445FFD1F992015D5
External Test Config: 09/08/2010

Attachments:

Comments: