Re: White space in facet filter not working

[David Smiley]

Hello,

You are asking on the wrong mailing list.  Use us...@solr.apache.org
instead.  See https://solr.apache.org/community.html
Tip about your question: you will need to use the right query parser
in the fq like "field"fq={!field f=fieldName}a b c d

On Sun, Mar 3, 2024 at 2:00 PM MUHAMMADALI V  wrote:
>
> Hi,
>
> I have a facet field indexed with value contains some spaces in it. When i
> am applying filter by passing the value with space I am not getting any
> matching results.
>
> Please let me know if i need to do any configurations in solr to resolve
> this issue.
>
> Thanks & Regards
> Muhammadali V

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

Re: MixedCase or dashed-case for long options in Solr CLI?

[Eric Pugh]

-z and --zk-host works for me.


> On Mar 4, 2024, at 9:15 AM, Arrieta, Alejandro  
> wrote:
> 
> I prefer
> 
> —zk-host
> 
> Kind Regards,
> Alejandro Arrieta
> 
> On Mon, Mar 4, 2024 at 8:45 AM Eric Pugh  >
> wrote:
> 
>> “zkHost” —> “—zk-host” or “—zkhost” ?
>> 
>> 
>>> On Mar 4, 2024, at 6:34 AM, Eric Pugh 
>> wrote:
>>> 
>>> Kebab!  I love it.
>>> 
>>> 
 On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro <
>> aarri...@perrinsoftware.com> wrote:
 
 Hello,
 
 dashed-case is called kebab case almost everywhere. One example:
 https://www.theserverside.com/definition/Kebab-case
 I was looking at the meaning of dashed-case, and it always pointed to
 kebab-case.
 
 Having kebab, Kamel, and other cases helps troubleshoot over a
>> conference
 to see command errors faster or to tell where to insert other words.
 For scripts it does not matter imho.
 
 Yes, please go with Kebab case everything. Now you know the most common
 name it will never go away.
 
 Kind Regards,
 Alejandro Arrieta
 
 On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh <
>> ep...@opensourceconnections.com  
>> >
 wrote:
 
> Thanks all for weighing in.   So I’m going to go for —dashed-case for
>> long
> options.   So expect some —solr-url and —zk-host parameters coming!
> 
> 
> 
>> On Feb 26, 2024, at 10:28 AM, Walter Underwood > 
>>> 
> wrote:
>> 
>> Long options are dashed-case, following the GNU convention. POSIX only
> specifies single character options. The “—“ prefix for long options is
>> a
> GNU invention, as far as I know. Older Unix commands with long option
> names, e.g. find, only use a single dash.
>> 
>> 
>> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
>> 
>> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
>> 
>> wunder
>> Walter Underwood
>> wun...@wunderwood.org  
>>  > wun...@wunderwood.org >
>> http://observer.wunderwood.org/  (my blog)
>> 
>>> On Feb 26, 2024, at 5:29 AM, Eric Pugh <
>> ep...@opensourceconnections.com  
>> 
> > wrote:
>>> 
>>> I hear a vote for dashed-case, how about some more votes?
> —solr-update-url versus —solrUpdateUrl ?
>>> 
>>> 
>>> 
 On Feb 26, 2024, at 7:29 AM, Jason Gerlowski >>> 
>> >
> wrote:
 
 My guess is that "dashed-case" is slightly more common -- at least,
 that's my sense from haphazardly checking a few tools I use often
 ("curl", "kubectl", "git", "docker").
 
 But I don't have an opinion as long as we're internally consistent
 about using one convention or the other.
 
 Best,
 
 Jason
 
 On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
 >>>  > ep...@opensourceconnections.com > 
>>  ep...@opensourceconnections.com  
> > ep...@opensourceconnections.com >> 
>>  wrote:
> 
> Hi all,
> 
> I wanted to get the communities input on formatting of long options
> for the Solr CLI.   I noticed on
> https://commons.apache.org/proper/commons-cli/ that their examples all
> are —dashed-case.
> 
> However, we have —solrUrl or —zkHost as our pattern.   Though in
> working on the PostTool, I used —solr-update-url as the parameter
>> because I
> had been reading the commons-cli docs...
> 
> I’d like to get this sorted so that I can get
> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
> So please do speak up with preferences!   (And please let’s not support
> both!)
> 
> 
> The changes to the formatting will be a 10x thing.
> 
> Eric
> 
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
> 434.466.1467 | http://www.opensourceconnections.com 
>  <
>> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/> <
> http://www.opensourceconnections.com/><
> http://www.opensourceconnections.com/> | My Free/Busy <
> http://tinyurl.com/eric-cal>
> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> 

Re: MixedCase or dashed-case for long options in Solr CLI?

[Arrieta, Alejandro]

I prefer

—zk-host

Kind Regards,
Alejandro Arrieta

On Mon, Mar 4, 2024 at 8:45 AM Eric Pugh 
wrote:

> “zkHost” —> “—zk-host” or “—zkhost” ?
>
>
> > On Mar 4, 2024, at 6:34 AM, Eric Pugh 
> wrote:
> >
> > Kebab!  I love it.
> >
> >
> >> On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro <
> aarri...@perrinsoftware.com> wrote:
> >>
> >> Hello,
> >>
> >> dashed-case is called kebab case almost everywhere. One example:
> >> https://www.theserverside.com/definition/Kebab-case
> >> I was looking at the meaning of dashed-case, and it always pointed to
> >> kebab-case.
> >>
> >> Having kebab, Kamel, and other cases helps troubleshoot over a
> conference
> >> to see command errors faster or to tell where to insert other words.
> >> For scripts it does not matter imho.
> >>
> >> Yes, please go with Kebab case everything. Now you know the most common
> >> name it will never go away.
> >>
> >> Kind Regards,
> >> Alejandro Arrieta
> >>
> >> On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh <
> ep...@opensourceconnections.com >
> >> wrote:
> >>
> >>> Thanks all for weighing in.   So I’m going to go for —dashed-case for
> long
> >>> options.   So expect some —solr-url and —zk-host parameters coming!
> >>>
> >>>
> >>>
>  On Feb 26, 2024, at 10:28 AM, Walter Underwood  >
> >>> wrote:
> 
>  Long options are dashed-case, following the GNU convention. POSIX only
> >>> specifies single character options. The “—“ prefix for long options is
> a
> >>> GNU invention, as far as I know. Older Unix commands with long option
> >>> names, e.g. find, only use a single dash.
> 
> 
> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
> 
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
> 
>  wunder
>  Walter Underwood
>  wun...@wunderwood.org   wun...@wunderwood.org>
>  http://observer.wunderwood.org/  (my blog)
> 
> > On Feb 26, 2024, at 5:29 AM, Eric Pugh <
> ep...@opensourceconnections.com 
> >>> > wrote:
> >
> > I hear a vote for dashed-case, how about some more votes?
> >>> —solr-update-url versus —solrUpdateUrl ?
> >
> >
> >
> >> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  >
> >>> wrote:
> >>
> >> My guess is that "dashed-case" is slightly more common -- at least,
> >> that's my sense from haphazardly checking a few tools I use often
> >> ("curl", "kubectl", "git", "docker").
> >>
> >> But I don't have an opinion as long as we're internally consistent
> >> about using one convention or the other.
> >>
> >> Best,
> >>
> >> Jason
> >>
> >> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> >>  ep...@opensourceconnections.com>  >>> ep...@opensourceconnections.com  ep...@opensourceconnections.com>>  >>
> >>> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I wanted to get the communities input on formatting of long options
> >>> for the Solr CLI.   I noticed on
> >>> https://commons.apache.org/proper/commons-cli/ that their examples all
> >>> are —dashed-case.
> >>>
> >>> However, we have —solrUrl or —zkHost as our pattern.   Though in
> >>> working on the PostTool, I used —solr-update-url as the parameter
> because I
> >>> had been reading the commons-cli docs...
> >>>
> >>> I’d like to get this sorted so that I can get
> >>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
> >>> So please do speak up with preferences!   (And please let’s not support
> >>> both!)
> >>>
> >>>
> >>> The changes to the formatting will be a 10x thing.
> >>>
> >>> Eric
> >>>
> >>> ___
> >>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
> >>> 434.466.1467 | http://www.opensourceconnections.com <
> http://www.opensourceconnections.com/> <
> >>> http://www.opensourceconnections.com/> <
> >>> http://www.opensourceconnections.com/><
> >>> http://www.opensourceconnections.com/> | My Free/Busy <
> >>> http://tinyurl.com/eric-cal>
> >>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> >>>
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> 
> >>> This e-mail and all contents, including attachments, is considered
> to
> >>> be Company Confidential unless explicitly stated otherwise, regardless
> of
> >>> whether attachments are marked as such.
> >>>
> >>
> >>
> -
> >> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org  dev-unsubscr...@solr.apache.org>  >>> dev-unsubscr...@solr.apache.org  dev-unsubscr...@solr.apache.org>> 
> >> For additional commands, e-mail: 

Re: MixedCase or dashed-case for long options in Solr CLI?

[Eric Pugh]

“zkHost” —> “—zk-host” or “—zkhost” ?


> On Mar 4, 2024, at 6:34 AM, Eric Pugh  wrote:
> 
> Kebab!  I love it.
> 
> 
>> On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro  
>> wrote:
>> 
>> Hello,
>> 
>> dashed-case is called kebab case almost everywhere. One example:
>> https://www.theserverside.com/definition/Kebab-case
>> I was looking at the meaning of dashed-case, and it always pointed to
>> kebab-case.
>> 
>> Having kebab, Kamel, and other cases helps troubleshoot over a conference
>> to see command errors faster or to tell where to insert other words.
>> For scripts it does not matter imho.
>> 
>> Yes, please go with Kebab case everything. Now you know the most common
>> name it will never go away.
>> 
>> Kind Regards,
>> Alejandro Arrieta
>> 
>> On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh > >
>> wrote:
>> 
>>> Thanks all for weighing in.   So I’m going to go for —dashed-case for long
>>> options.   So expect some —solr-url and —zk-host parameters coming!
>>> 
>>> 
>>> 
 On Feb 26, 2024, at 10:28 AM, Walter Underwood 
>>> wrote:
 
 Long options are dashed-case, following the GNU convention. POSIX only
>>> specifies single character options. The “—“ prefix for long options is a
>>> GNU invention, as far as I know. Older Unix commands with long option
>>> names, e.g. find, only use a single dash.
 
 https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
 https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
 
 wunder
 Walter Underwood
 wun...@wunderwood.org  
 
 http://observer.wunderwood.org/  (my blog)
 
> On Feb 26, 2024, at 5:29 AM, Eric Pugh  
>>> > wrote:
> 
> I hear a vote for dashed-case, how about some more votes?
>>> —solr-update-url versus —solrUpdateUrl ?
> 
> 
> 
>> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski > >
>>> wrote:
>> 
>> My guess is that "dashed-case" is slightly more common -- at least,
>> that's my sense from haphazardly checking a few tools I use often
>> ("curl", "kubectl", "git", "docker").
>> 
>> But I don't have an opinion as long as we're internally consistent
>> about using one convention or the other.
>> 
>> Best,
>> 
>> Jason
>> 
>> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
>> >  >> ep...@opensourceconnections.com > 
>>> >
>>> wrote:
>>> 
>>> Hi all,
>>> 
>>> I wanted to get the communities input on formatting of long options
>>> for the Solr CLI.   I noticed on
>>> https://commons.apache.org/proper/commons-cli/ that their examples all
>>> are —dashed-case.
>>> 
>>> However, we have —solrUrl or —zkHost as our pattern.   Though in
>>> working on the PostTool, I used —solr-update-url as the parameter because I
>>> had been reading the commons-cli docs...
>>> 
>>> I’d like to get this sorted so that I can get
>>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
>>> So please do speak up with preferences!   (And please let’s not support
>>> both!)
>>> 
>>> 
>>> The changes to the formatting will be a 10x thing.
>>> 
>>> Eric
>>> 
>>> ___
>>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
>>> 434.466.1467 | http://www.opensourceconnections.com 
>>>  <
>>> http://www.opensourceconnections.com/> <
>>> http://www.opensourceconnections.com/><
>>> http://www.opensourceconnections.com/> | My Free/Busy <
>>> http://tinyurl.com/eric-cal>
>>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>>> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
 
>>> This e-mail and all contents, including attachments, is considered to
>>> be Company Confidential unless explicitly stated otherwise, regardless of
>>> whether attachments are marked as such.
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org 
>>  >> dev-unsubscr...@solr.apache.org > 
>>> 
>> For additional commands, e-mail: dev-h...@solr.apache.org 
>>  >> dev-h...@solr.apache.org > 
>>> 
> ___
> Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
>>> | http://www.opensourceconnections.com 
>>> 

Re: MixedCase or dashed-case for long options in Solr CLI?

[Eric Pugh]

Kebab!  I love it.


> On Mar 3, 2024, at 1:14 PM, Arrieta, Alejandro  
> wrote:
> 
> Hello,
> 
> dashed-case is called kebab case almost everywhere. One example:
> https://www.theserverside.com/definition/Kebab-case
> I was looking at the meaning of dashed-case, and it always pointed to
> kebab-case.
> 
> Having kebab, Kamel, and other cases helps troubleshoot over a conference
> to see command errors faster or to tell where to insert other words.
> For scripts it does not matter imho.
> 
> Yes, please go with Kebab case everything. Now you know the most common
> name it will never go away.
> 
> Kind Regards,
> Alejandro Arrieta
> 
> On Sun, Mar 3, 2024 at 2:10 PM Eric Pugh  >
> wrote:
> 
>> Thanks all for weighing in.   So I’m going to go for —dashed-case for long
>> options.   So expect some —solr-url and —zk-host parameters coming!
>> 
>> 
>> 
>>> On Feb 26, 2024, at 10:28 AM, Walter Underwood 
>> wrote:
>>> 
>>> Long options are dashed-case, following the GNU convention. POSIX only
>> specifies single character options. The “—“ prefix for long options is a
>> GNU invention, as far as I know. Older Unix commands with long option
>> names, e.g. find, only use a single dash.
>>> 
>>> https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html
>>> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
>>> 
>>> wunder
>>> Walter Underwood
>>> wun...@wunderwood.org  
>>> 
>>> http://observer.wunderwood.org/  (my blog)
>>> 
 On Feb 26, 2024, at 5:29 AM, Eric Pugh >>> 
>> > wrote:
 
 I hear a vote for dashed-case, how about some more votes?
>> —solr-update-url versus —solrUpdateUrl ?
 
 
 
> On Feb 26, 2024, at 7:29 AM, Jason Gerlowski  >
>> wrote:
> 
> My guess is that "dashed-case" is slightly more common -- at least,
> that's my sense from haphazardly checking a few tools I use often
> ("curl", "kubectl", "git", "docker").
> 
> But I don't have an opinion as long as we're internally consistent
> about using one convention or the other.
> 
> Best,
> 
> Jason
> 
> On Sat, Feb 24, 2024 at 11:35 AM Eric Pugh
> mailto:ep...@opensourceconnections.com> 
> > ep...@opensourceconnections.com > 
>> >
>> wrote:
>> 
>> Hi all,
>> 
>> I wanted to get the communities input on formatting of long options
>> for the Solr CLI.   I noticed on
>> https://commons.apache.org/proper/commons-cli/ that their examples all
>> are —dashed-case.
>> 
>> However, we have —solrUrl or —zkHost as our pattern.   Though in
>> working on the PostTool, I used —solr-update-url as the parameter because I
>> had been reading the commons-cli docs...
>> 
>> I’d like to get this sorted so that I can get
>> https://issues.apache.org/jira/browse/SOLR-16824 over the finish line.
>> So please do speak up with preferences!   (And please let’s not support
>> both!)
>> 
>> 
>> The changes to the formatting will be a 10x thing.
>> 
>> Eric
>> 
>> ___
>> Eric Pugh | Founder & CEO | OpenSource Connections, LLC |
>> 434.466.1467 | http://www.opensourceconnections.com 
>>  <
>> http://www.opensourceconnections.com/> <
>> http://www.opensourceconnections.com/><
>> http://www.opensourceconnections.com/> | My Free/Busy <
>> http://tinyurl.com/eric-cal>
>> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
>>> 
>> This e-mail and all contents, including attachments, is considered to
>> be Company Confidential unless explicitly stated otherwise, regardless of
>> whether attachments are marked as such.
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org 
>  > dev-unsubscr...@solr.apache.org > 
>> 
> For additional commands, e-mail: dev-h...@solr.apache.org 
>  > dev-h...@solr.apache.org > 
>> 
 ___
 Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467
>> | http://www.opensourceconnections.com 
>>  <
>> http://www.opensourceconnections.com/> <
>> http://www.opensourceconnections.com/> | My Free/Busy <
>> http://tinyurl.com/eric-cal>
 Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
>>