[ 
https://issues.apache.org/jira/browse/SOLR-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Potter updated SOLR-6952:
---------------------------------
    Attachment: SOLR-6952.patch

Here's an updated patch that changes around some of the parameter names to be 
consistent with the zkcli.sh script. I also tackled the "create" alias 
(SOLR-6933) in this patch since it was easier to address both issues with one 
patch.

*Example 1*
{code}
bin/solr create -c foo
{code}

This is equivalent to doing:

{code}
bin/solr create -c foo -d data_driven_schema_configs
{code}

or

{code}
bin/solr create -c foo -d data_driven_schema_configs -n foo
{code}

The create action will upload the data_driven_schema_configs directory (the 
default) into ZooKeeper as /configs/foo, i.e. the data_driven_schema_configs 
"template" is copied to a unique config directory in ZooKeeper using the name 
of the collection you are creating.

*Example 2*
{code}
bin/solr create -c foo2 -d basic_configs -n SharedBasicSchema
{code}

This will upload the basic_configs directory into ZooKeeper as 
/configs/SharedBasicSchema. If one wants to reuse the SharedBasicSchema 
configuration directory when creating another collection, they can just do: 
{code}
bin/solr create -c foo3 -n SharedBasicSchema
{code}

Going to start porting these changes to the Windows solr.cmd, so please speak 
up now or this is what we'll have for 5.0 ;-)

> Re-using 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
>            Assignee: Timothy Potter
>             Fix For: 5.0
>
>         Attachments: SOLR-6952.patch, SOLR-6952.patch
>
>
> 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:
> {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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to