[jira] [Commented] (SOLR-9891) Add mkroot command to bin/solr and bin/solr.cmd
[ https://issues.apache.org/jira/browse/SOLR-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927384#comment-15927384 ] Erick Erickson commented on SOLR-9891: -- Please open new JIRAs rather than comment on closed ones, that makes the bookkeeping easier ;). > Add mkroot command to bin/solr and bin/solr.cmd > --- > > Key: SOLR-9891 > URL: https://issues.apache.org/jira/browse/SOLR-9891 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Minor > Fix For: trunk, 6.4 > > Attachments: SOLR-9891.patch, SOLR-9891.patch > > > This came to my attention just now. To use a different root in Solr, we say > this in the ref guide: > IMPORTANT: If your ZooKeeper connection string uses a chroot, such as > localhost:2181/solr, then you need to bootstrap the /solr znode before > launching SolrCloud using the bin/solr script. To do this, you need to use > the zkcli.sh script shipped with Solr, such as: > server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181/solr -cmd > bootstrap -solrhome server/solr > I think all this really does is create an empty /solr ZNode. We're trying to > move the common usages of the zkcli scripts to bin/solr so I tried making > this work. > It's clumsy. If I try to copy up an empty directory to /solr nothing happens. > I got it to work by copying file:README.txt to zk:/solr/nonsense then delete > zk:/solr/nonsense. Ugly. > I don't want to get into reproducing the whole Unix shell file manipulation > commands with mkdir, touch, etc. > I guess we already have special 'upconfig' and 'downconfig' commands, so > maybe a specific command for this like 'mkroot' would be OK. Do people have > opinions about this as opposed to 'mkdir'? I'm tending to mkdir. > Or have the cp command handle empty directories, but mkroot/mkdir seems more > intuitive if not as generic. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9891) Add mkroot command to bin/solr and bin/solr.cmd
[
https://issues.apache.org/jira/browse/SOLR-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15927165#comment-15927165
]
kiran commented on SOLR-9891:
-
It would be useful if this command worked when the connect string has the
chroot path like {noformat}bin/solr zk mkroot -z {}/chroot{noformat}
That would achieve similar functionality with how bootstrap command worked
> Add mkroot command to bin/solr and bin/solr.cmd
> ---
>
> Key: SOLR-9891
> URL: https://issues.apache.org/jira/browse/SOLR-9891
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
>Reporter: Erick Erickson
>Assignee: Erick Erickson
>Priority: Minor
> Fix For: trunk, 6.4
>
> Attachments: SOLR-9891.patch, SOLR-9891.patch
>
>
> This came to my attention just now. To use a different root in Solr, we say
> this in the ref guide:
> IMPORTANT: If your ZooKeeper connection string uses a chroot, such as
> localhost:2181/solr, then you need to bootstrap the /solr znode before
> launching SolrCloud using the bin/solr script. To do this, you need to use
> the zkcli.sh script shipped with Solr, such as:
> server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181/solr -cmd
> bootstrap -solrhome server/solr
> I think all this really does is create an empty /solr ZNode. We're trying to
> move the common usages of the zkcli scripts to bin/solr so I tried making
> this work.
> It's clumsy. If I try to copy up an empty directory to /solr nothing happens.
> I got it to work by copying file:README.txt to zk:/solr/nonsense then delete
> zk:/solr/nonsense. Ugly.
> I don't want to get into reproducing the whole Unix shell file manipulation
> commands with mkdir, touch, etc.
> I guess we already have special 'upconfig' and 'downconfig' commands, so
> maybe a specific command for this like 'mkroot' would be OK. Do people have
> opinions about this as opposed to 'mkdir'? I'm tending to mkdir.
> Or have the cp command handle empty directories, but mkroot/mkdir seems more
> intuitive if not as generic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9891) Add mkroot command to bin/solr and bin/solr.cmd
[ https://issues.apache.org/jira/browse/SOLR-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786607#comment-15786607 ] Erick Erickson commented on SOLR-9891: -- Thanks Steve! > Add mkroot command to bin/solr and bin/solr.cmd > --- > > Key: SOLR-9891 > URL: https://issues.apache.org/jira/browse/SOLR-9891 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Minor > Attachments: SOLR-9891.patch, SOLR-9891.patch > > > This came to my attention just now. To use a different root in Solr, we say > this in the ref guide: > IMPORTANT: If your ZooKeeper connection string uses a chroot, such as > localhost:2181/solr, then you need to bootstrap the /solr znode before > launching SolrCloud using the bin/solr script. To do this, you need to use > the zkcli.sh script shipped with Solr, such as: > server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181/solr -cmd > bootstrap -solrhome server/solr > I think all this really does is create an empty /solr ZNode. We're trying to > move the common usages of the zkcli scripts to bin/solr so I tried making > this work. > It's clumsy. If I try to copy up an empty directory to /solr nothing happens. > I got it to work by copying file:README.txt to zk:/solr/nonsense then delete > zk:/solr/nonsense. Ugly. > I don't want to get into reproducing the whole Unix shell file manipulation > commands with mkdir, touch, etc. > I guess we already have special 'upconfig' and 'downconfig' commands, so > maybe a specific command for this like 'mkroot' would be OK. Do people have > opinions about this as opposed to 'mkdir'? I'm tending to mkdir. > Or have the cp command handle empty directories, but mkroot/mkdir seems more > intuitive if not as generic. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9891) Add mkroot command to bin/solr and bin/solr.cmd
[ https://issues.apache.org/jira/browse/SOLR-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786605#comment-15786605 ] ASF subversion and git services commented on SOLR-9891: --- Commit ed55658620e66b7a06a820219daf6435dfb070d6 in lucene-solr's branch refs/heads/branch_6x from [~erickerickson] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ed55658 ] SOLR-9891: Add mkroot command to bin/solr and bin/solr.cmd (cherry picked from commit cb266d5) > Add mkroot command to bin/solr and bin/solr.cmd > --- > > Key: SOLR-9891 > URL: https://issues.apache.org/jira/browse/SOLR-9891 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Minor > Attachments: SOLR-9891.patch, SOLR-9891.patch > > > This came to my attention just now. To use a different root in Solr, we say > this in the ref guide: > IMPORTANT: If your ZooKeeper connection string uses a chroot, such as > localhost:2181/solr, then you need to bootstrap the /solr znode before > launching SolrCloud using the bin/solr script. To do this, you need to use > the zkcli.sh script shipped with Solr, such as: > server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181/solr -cmd > bootstrap -solrhome server/solr > I think all this really does is create an empty /solr ZNode. We're trying to > move the common usages of the zkcli scripts to bin/solr so I tried making > this work. > It's clumsy. If I try to copy up an empty directory to /solr nothing happens. > I got it to work by copying file:README.txt to zk:/solr/nonsense then delete > zk:/solr/nonsense. Ugly. > I don't want to get into reproducing the whole Unix shell file manipulation > commands with mkdir, touch, etc. > I guess we already have special 'upconfig' and 'downconfig' commands, so > maybe a specific command for this like 'mkroot' would be OK. Do people have > opinions about this as opposed to 'mkdir'? I'm tending to mkdir. > Or have the cp command handle empty directories, but mkroot/mkdir seems more > intuitive if not as generic. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-9891) Add mkroot command to bin/solr and bin/solr.cmd
[ https://issues.apache.org/jira/browse/SOLR-9891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786602#comment-15786602 ] ASF subversion and git services commented on SOLR-9891: --- Commit cb266d5fc775bd9d26ed7f0e68e9d0d12793f9b5 in lucene-solr's branch refs/heads/master from [~erickerickson] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=cb266d5 ] SOLR-9891: Add mkroot command to bin/solr and bin/solr.cmd > Add mkroot command to bin/solr and bin/solr.cmd > --- > > Key: SOLR-9891 > URL: https://issues.apache.org/jira/browse/SOLR-9891 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Erick Erickson >Assignee: Erick Erickson >Priority: Minor > Attachments: SOLR-9891.patch, SOLR-9891.patch > > > This came to my attention just now. To use a different root in Solr, we say > this in the ref guide: > IMPORTANT: If your ZooKeeper connection string uses a chroot, such as > localhost:2181/solr, then you need to bootstrap the /solr znode before > launching SolrCloud using the bin/solr script. To do this, you need to use > the zkcli.sh script shipped with Solr, such as: > server/scripts/cloud-scripts/zkcli.sh -zkhost localhost:2181/solr -cmd > bootstrap -solrhome server/solr > I think all this really does is create an empty /solr ZNode. We're trying to > move the common usages of the zkcli scripts to bin/solr so I tried making > this work. > It's clumsy. If I try to copy up an empty directory to /solr nothing happens. > I got it to work by copying file:README.txt to zk:/solr/nonsense then delete > zk:/solr/nonsense. Ugly. > I don't want to get into reproducing the whole Unix shell file manipulation > commands with mkdir, touch, etc. > I guess we already have special 'upconfig' and 'downconfig' commands, so > maybe a specific command for this like 'mkroot' would be OK. Do people have > opinions about this as opposed to 'mkdir'? I'm tending to mkdir. > Or have the cp command handle empty directories, but mkroot/mkdir seems more > intuitive if not as generic. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
