tracker issue : CF-3935959

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

Solr on ColdFusion 10 Does not Support More than 4 Custom Fields

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/UserError

Reporter/Name(from Bugbase): Mary Jo Sminkey / Mary Jo Sminkey (Mary Jo Sminkey)

Created: 02/06/2015

Components: Text Search, Solr

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 1

Problem Description: Trying to run cfindex with more than 4 custom fields, dynamic or not, throws errors. 

Steps to Reproduce: cfindex tag with more than 4 custom fields

Actual Result: Error received: An error occurred while performing an index operation. There is an invalid attributname-attributevalue combination 

Expected Result: Should index the data as requested

Any Workarounds: Have to either concatenate the data into the 4 fields or work with Solr outside of CF

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

Watson Bug ID:	3935959

External Customer Info:
External Company:  
External Customer Name: Mary
External Customer Email:  
External Test Config: Tested on both CFC10 Standard and Enterprise on Windows server

Attachments:

Comments:

Information on Solr in CF10 clearly mentions being able to use more than 4 custom fields : https://wikidocs.adobe.com/wiki/display/coldfusionen/Solr+enhancements+in+ColdFusion+10
Comment by External U.
8515 | February 06, 2015 06:01:19 PM GMT
"column_i is the custom field provided by user while indexing.This option was available in ColdFusion 9, but limited to four custom fields. In ColdFusion 10, the options are unlimited."
Comment by External U.
8516 | February 06, 2015 06:02:46 PM GMT
This is affecting our development efforts
Vote by External U.
8523 | February 06, 2015 06:15:21 PM GMT
Mary, Can you please share the relevant part in your code which is returning that error. If you enable the "robust exception information" in the CF administrator > Debugging and Logging > Debug output settings, the error output should be more detailed with the cfm page, location and line number causing the error. I don't see any errors (on a standalone CF 10,0,15,292620 / Win x64) with the following : <cfindex action='refresh' collection="#col_name#" type="path" key="#datadir#" extensions = ".bmp, .doc, .rtf, .pdf, .txt" urlpath='http://localhost:85xx/' status="stat" datefld_dt = "#DateFormat(now())#" intfld1_i = 10 intfld2_i = 11 intfld3_i = 12 intfldbool_b = 1 intflddbl_d = 12.89890998 strfld1_s = "fldtest str1" strfld2_s = "fldtest str2" strfld3_s = "fldtest str3" strfld4_s = "fldtest str4" strfld5_s = "fldtest str5" />
Comment by Piyush K.
8517 | February 11, 2015 07:54:55 AM GMT
Mary, I am closing this since I have been unable to reproduce the issue. I would really like to know how you have been using the custom fields. We can reopen this if you can share the details. Thanks.
Comment by Piyush K.
8518 | June 16, 2015 03:26:05 AM GMT
Same bug here when using anything other than string type data (field_s).
Comment by External U.
8519 | June 18, 2015 06:59:40 AM GMT
Sorry, I did not have email notifications on so didn't see this, but as Paul mentioned, it probably is due to you not testing with anything other than string fields. In our case, we had both integer and string custom fields.
Comment by External U.
8520 | July 03, 2015 12:53:13 PM GMT
Oh sorry, it looks like you did have other non-string custom fields. It's possible that it was due to being on an earlier update of CF10, however due to another bug which broke CF10 for us after update 13 I'm not able to update in order to test this. As for the exact code that gives this error, it's basically the cfindex tag, as reported. If i have only 4 custom fields, it's fine, more than that and it errors out with the message given.
Comment by External U.
8521 | July 03, 2015 12:56:46 PM GMT
Also, this may have something to do with it, I was indexing a query recordset, not documents. Please test using a query and not a document path.
Comment by External U.
8522 | July 03, 2015 12:58:38 PM GMT