[ https://issues.apache.org/jira/browse/SOLR-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272560#comment-14272560 ]
Noble Paul commented on SOLR-6952: ---------------------------------- Keeping in mind ease the script by default should create a copy unless specified otherwise > Copying data-driven configsets by default is not helpful > -------------------------------------------------------- > > Key: SOLR-6952 > URL: https://issues.apache.org/jira/browse/SOLR-6952 > Project: Solr > Issue Type: Bug > Components: Schema and Analysis > Affects Versions: 5.0 > Reporter: Grant Ingersoll > Fix For: 5.0 > > > When creating collections (I'm using the bin/solr scripts), I don't think we > should automatically copy configsets, especially when running in "getting > started mode" or data driven mode. > I did the following: > {code} > bin/solr create_collection -n foo > bin/post foo some_data.csv > {code} > 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: > {quote} > 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) > {quote} > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org