lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Potter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3619) Rename 'example' dir to 'server' and pull examples into an 'examples' directory
Date Fri, 21 Nov 2014 03:45:35 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220482#comment-14220482
] 

Timothy Potter commented on SOLR-3619:
--------------------------------------

Thanks for digging in [~arafalov] ... your feedback is much appreciated.

Agreed on the *create_core* cloning the configset, e.g. if I do: {{bin/solr create_core -n
foo -c basic_configs}}, then the create_core action will:
{code}
mkdir server/solr/foo
cp -r server/solr/configsets/basic_configs/conf server/solr/foo/conf
{code}

As for the names of the configsets and the examples, I used the names Hoss suggested in his
comment above for the configsets but heard rumblings at Rev that others didn't like the long
names ;-) It's easy to change the names at this point, so what do we want them to be called?
I'm cool with whatever people think are short but descriptive enough.

multicore - ugh! I intended on just getting rid of it, but there are unit tests that rely
on that directory. It should be removed under a separate ticket (SOLR-6773); I don't think
it should be an example anymore but if we don't get rid of it, then I can add it back as an
example in the bin/solr script as the consistency will be confusing and that's exactly what
we don't want.

As for the {{bin/solr -e cloud}} example being affected by artifacts from running other examples,
I think we can just have the script clean-up unrecognized directories after cloning, i.e.

{code}
cp -r server node1
rm -r node1/solr/<unrecognized_dir>
cp -r node1 node2
{code}

This is just an example, so putting the node1 directory into the expected state after cloning
seems reasonable, albeit a bit of a maintenance issue if the list of expected dirs changes,
but that happens very infrequently.

Lastly, you can restart the cloud example, but you have to just use the bin/solr options directly.
For instance, if you launched {{bin/solr -e cloud -noprompt}} (2 nodes on the default ports),
you could stop and restart using:

{code}
bin/solr stop -all
bin/solr restart -c -p 8983 -d node1
bin/solr restart -c -p 7574 -d node2 -z localhost:9983
{code}

The example prints out these commands as it runs to help the user make the link between what
the example is doing and the command-line options supported by the script.


> 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: 5.0, Trunk
>
>         Attachments: SOLR-3619.patch, SOLR-3619.patch, SOLR-3619.patch, managed-schema,
server-name-layout.png, solrconfig.xml
>
>




--
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


Mime
View raw message