Which schema.xml to modify for a patch?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Which schema.xml to modify for a patch?

Otis Gospodnetic-2
Hi,

As I'm adding NGramTokenizer and other things to my local schema.xml for development, I'm wondering where the new tokenizer/fieldtype/copyField should really go?  In other words, which schema.xml instance should I add them to before making a diff/patch?

$ ff schema.xml
./src/test/test-files/solr/conf/schema.xml         <-- this one?
./example/solr/conf/schema.xml                     <-- or this one?  I'm modifying this one locally

I'll add them to the example one, but all commented out, unless somebody has a better suggestion.

Thanks,
Otis


Reply | Threaded
Open this post in threaded view
|

Re: Which schema.xml to modify for a patch?

Yonik Seeley-2
On 12/22/06, Otis Gospodnetic <[hidden email]> wrote:
> As I'm adding NGramTokenizer and other things to my local schema.xml for development, I'm wondering where the new tokenizer/fieldtype/copyField should really go?  In other words, which schema.xml instance should I add them to before making a diff/patch?
>
> $ ff schema.xml
> ./src/test/test-files/solr/conf/schema.xml         <-- this one?
> ./example/solr/conf/schema.xml                     <-- or this one?  I'm modifying this one locally

The one in "example" is the recommended starting point for users, and
we should try to keep that one useful, correct, and concise,
out-of-the-box.

The one in test has everything plus the kitchen sink thrown in for testing.

-Yonik
Reply | Threaded
Open this post in threaded view
|

Re: Which schema.xml to modify for a patch?

Bertrand Delacretaz
On 12/22/06, Yonik Seeley <[hidden email]> wrote:
> The one in "example" is the recommended starting point for users...

I have added this info as comments in the schema files to clarify this.
-Bertrand