[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089886#comment-14089886
]
Hoss Man commented on SOLR-3619:
--------------------------------
bq. Can we agree to start with 2 configsets (based on Hoss' plan above) and
then work on converting the other examples iteratively?
It sounds like you'd need a _minimum_ of 3 to start with:
* data_driven_schema_configs (new, based on example-schemaless's
solrconfig.xml, but no starting schema.xml )
* basic_configs (new, as bare bones as we can get w/ the rest APIs enabled)
* sample_techproducts_configs (exact copy of the current collection1 configs
reasoning: basic_configs & data_driven_schema_configs should start out (and
stay!) _tiny_ and clean, and demonstrate how simple starting configs can be --
the key distinction between them simply being that one let's you just throw
data at, and the other you have to use the REST API to explicit create fields.
That way it's more obvious (then it is today) how you can do things
programtically even if you don't want auto-generated fields ... it's not an
"all or nothing" world of schemaless vs manual editing of schema.xml. But
basic_configs is still super small and clean and tiny and easy to see how you
can disable the REST API if you don't want it. But then, in addition to those
two, you still have the big beefy sample_techproducts_configs that can be used
in the tutorial to shows off the kitchen sink of features.
So right from the start, you have something to make the "schemaless" fan boys
happy, and you have something a bit more locked down but still welcoming for
the REST zealots, and then you still have the reliable old standby that's easy
to understand for people who like editing config files and/or are trying to
follow along an article they're reading that was written 4 years ago.
Then, as you say, we can iterate on adding more configsets by gradually teasing
out (and pairing down) things from sample_techproducts_configs and bringing
back things from example-DIH.
bq. So it seems like we should just do: svn mv example/solr/collection1/conf
and have server/solr/configsets/basic_configs/conf
I can not, in good conscious, allow you to rename the current collection1
configs "basic" ... i know where you live Tim, don't make me come after you.
> Rename 'example' dir to 'server' and pull examples into an 'examples'
> directory
> -------------------------------------------------------------------------------
>
> Key: SOLR-3619
> URL: https://issues.apache.org/jira/browse/SOLR-3619
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Timothy Potter
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-3619.patch, SOLR-3619.patch, managed-schema,
> server-name-layout.png, solrconfig.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
