Title:
Bug 83900:When a coldfusion SOLR collection is created, there is a file in the conf directory called schema
| View in TrackerStatus/Resolution/Reason: Closed/Fixed/
Reporter/Name(from Bugbase): Travis Walters / Travis Walters (Travis Walters)
Created: 08/22/2010
Components: Text Search, Solr
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Minor / Unknown
Locale/System: English / Platforms All
Vote Count: 3
Problem:
When a coldfusion SOLR collection is created, there is a file in the conf directory called schema.xml. This file defines the types of the custom1 through custom4 fields for example. among many others. I would like better control over how this file is created when using CFCOLLECTION. It would be nice if we could specify the type of the field such as integer instead of every field being created as type text. In addition, it would be nice if we could specify whether a field should be indexed. The "key" field for example is not indexed in SOLR version 2.2 by default. When a key is not indexed in SOLR, it does not allow sorting by that field. If you have a product collection for example, it is nice to sort products by newest products or oldest products. The key field would be a nice field to do that sorting by. The CFSEARCH function really needs to pass a sort variable to do this but that is another issue I opened recently. For this issue, I am suggestion better control over how the schema file is created when using CFCOLLECTION. If you do this, coldfusion developers can do stuff like custom2:[0 TO 350] using the criteria field in CFSEARCH. That is great for getting products priced from 0 to 350 dollars.
Method:
Result:
This is a CFCOLLECTION suggestion.
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3041925
External Customer Info:
External Company:
External Customer Name: Travis Walters
External Customer Email: 163148AE447DEBE799201549
External Test Config: 08/22/2010Attachments:
Comments: