[SOLR-6952] Re-using data-driven configsets by default is not helpful

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0
• Fix Version/s: 5.0, 6.0
• Component/s: Schema and Analysis
• Assignee: Timothy Potter
• Reporter: Grant Ingersoll
• Created: 10/Jan/15 15:32
• Updated: 09/May/16 18:56
• Resolved: 05/May/15 13:41

Description

When creating collections (I'm using the bin/solr scripts), I think we should automatically copy configsets, especially when running in "getting started mode" or data driven mode.

I did the following:

bin/solr create_collection -n foo
bin/post foo some_data.csv

I then created a second collection with the intention of sending in the same data, but this time run through a python script that changed a value from an int to a string (since it was an enumerated type) and was surprised to see that I got:

Caused by: java.lang.NumberFormatException: For input string: "NA"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)

for my new version of the data that passes in a string instead of an int, as this new collection had only seen strings for that field.

Issue Links

• incorporates: SOLR-6933 bin/solr script should just have a single create action that creates a core or collection depending on the mode solr is running in
• relates to: SOLR-7502 start script should not try to create config set for .system collection