[ 
https://issues.apache.org/jira/browse/SOLR-11441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Gerlowski updated SOLR-11441:
-----------------------------------
    Attachment: SOLR-11441.patch

I was able to reproduce the issue the same way that Dawid described: I can 
reproduce in Powershell, but not in "standard" Command Prompt.

This does seem like something that would be nice to fix outright, but in case 
no one has the time to get to it soon, I've attached a doc-patch which updates 
the relevant {{bin/solr}} commands in the ref-guide to use quoting, as well as 
including a short blurb about the use of double-quotes in the main page for the 
{{bin/solr}} scripts.

It'd be better to actually fix the issue, but failing that, this patch might be 
useful.

> windows shell splits args on "=" so we should consider updating our docs to 
> always quote args like -Dfoo=bar or improve bin/solr.cmd to account for this
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-11441
>                 URL: https://issues.apache.org/jira/browse/SOLR-11441
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation, scripts and tools
>         Environment: Windows 10, possible other versions as well (presumably 
> not when running cygwin?)
>            Reporter: Hoss Man
>         Attachments: SOLR-11441.patch
>
>
> confusing exchange with a user on freenode#solr led to this discovery...
> {noformat}
> 14:07 < sara_:#solr> New question: bin/solr start -e techproducts 
> -Dsolr.ltr.enabled=true
> 14:07 < sara_:#solr> gave me invalid command-line option:true
> 14:07 < sara_:#solr> anyone knows why?
> ...
> 15:02 < sara_:#solr> i have 6.6.1 @elyograg
> 15:03 < sara_:#solr> mine is a windows 10 machine
> ...
> 15:28 < sara_:#solr> @elyograg i just downloaded solr-7.0.0 and ran bin/solr 
> start -e techproducts -Dsolr.ltr.enabled=true
> 15:28 < sara_:#solr> it still gave me invalid command-line
> ...
> 15:29 <@hoss:#solr> sara_: the only thing i can think of is that windows 10 
> is splitting your command line on '=' ? ... can you try 
>                     quoting the entire command line arg so the script gets 
> the entire -Dsolr.ltr.enabled=true ? (not sure how to quote 
>                     strings in the windows command shell -- i would assume 
> "-Dsolr.ltr.enabled=true"
> 15:32 <@hoss:#solr> sigh ... yes, aparently windows things "=" is a shell 
> delimiter: https://ss64.com/nt/syntax-esc.html
> 15:33 <@hoss:#solr> s/shell delimiter/parameter delimiter in shell commands/
> 15:33 < sara_:#solr> you are genius!
> 15:34 < sara_:#solr> you and elyograg. you guys are fantastic. Saving me from 
> looking at the cmd script or shell script....
> 15:34 <@hoss:#solr> sara_: do i have your permission to copy/paste this 
> exchange into our bug tracker as a note about updating our docs 
>                     (and maybe making the solr.cmd smart enough to handle 
> this) ?
> 15:45 < sara_:#solr> sure of course
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to