Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 12 Jan 2015 15:34:34 +0000 (UTC)
From: "Timothy Potter (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12766645.1420903944000.60891.1421076874772@Atlassian.JIRA>
In-Reply-To: <JIRA.12766645.1420903944000@Atlassian.JIRA>
References: <JIRA.12766645.1420903944000@Atlassian.JIRA>
 <JIRA.12766645.1420903944529@arcas>
Subject: [jira] [Updated] (SOLR-6952) Re-using data-driven configsets by
 default is not helpful
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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 a patch that implements the desired behavior. Easiest way to understand is to look at a few examples:

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

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 -n foo2 -t basic_configs -c SharedBasicSchema
{code}

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: {{bin/solr create -n foo3 -c SharedBasicSchema}}

If we're happy with this approach, I'll port over the changes to solr.cmd (for Windows)


> 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
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org