You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@impala.apache.org by Jeff Mortimer <jm...@phdata.io> on 2020/08/24 15:24:46 UTC
Defaulting to case-insensitive searching
Hey all! Is it possible to set up Impala to default to case-insensitive
searching? In other words, a search for "fooBar" returns "fooBar",
"foobar", "FOOBAR", etc? I've been looking through the documentation and
haven't found anything, but just wanted to be sure...
Also, I'm interested in joining the Slack workspace, but the link
previously posted to this list is returning an error that says "this link
is no longer active". Can someone post an updated invite link?
Thanks!
--
Jeff Mortimer
phData
P: 651-247-9352
E: jmortimer@phdata.io
<https://www.phdata.io/>
phData Voted 2020 Best Places to Work
<https://www.phdata.io/2020-best-places-to-work-winner/>
<https://www.instagram.com/phdatainc/>
<https://www.linkedin.com/company/phdata/> <https://twitter.com/phdatainc>
<https://www.facebook.com/phData.io/>
Re: Defaulting to case-insensitive searching
Posted by Shant Hovsepian <sh...@superdupershant.com>.
Hi Jeff!
In which context do you mean "case-insensitive search"?
Is this for schema objects like table and column names? Or do you mean for
actual data, for example select a from t where a = 'fooBar';
-Shant
On Mon, Aug 24, 2020 at 11:25 AM Jeff Mortimer <jm...@phdata.io> wrote:
> Hey all! Is it possible to set up Impala to default to case-insensitive
> searching? In other words, a search for "fooBar" returns "fooBar",
> "foobar", "FOOBAR", etc? I've been looking through the documentation and
> haven't found anything, but just wanted to be sure...
>
> Also, I'm interested in joining the Slack workspace, but the link
> previously posted to this list is returning an error that says "this link
> is no longer active". Can someone post an updated invite link?
>
> Thanks!
>
> --
>
> Jeff Mortimer
>
> phData
>
> P: 651-247-9352
>
> E: jmortimer@phdata.io
>
> <https://www.phdata.io/>
>
> phData Voted 2020 Best Places to Work
> <https://www.phdata.io/2020-best-places-to-work-winner/>
>
> <https://www.instagram.com/phdatainc/>
> <https://www.linkedin.com/company/phdata/> <https://twitter.com/phdatainc>
> <https://www.facebook.com/phData.io/>
>
Re: Defaulting to case-insensitive searching
Posted by Shant Hovsepian <sh...@superdupershant.com>.
Yes to Boris's point using ILIKE or IREGEXP would give you case insensitive
string matching options.
In general this type of behavior is achieved with COLLATION support in the
SQL Standard. Impala doesn't currently support collations but feel free to
file a jira bug request for it.
-Shant
On Mon, Aug 24, 2020 at 12:13 PM Boris Tyukin <bo...@boristyukin.com> wrote:
> Jeff, I think your best option is to use ilike/iregexp. One of these
> things that I do not like about Impala :)
>
> bonus tip, if you end up with lots of LIKEs, regexp will be way more
> efficient.
>
> In CDH 5.7 / Impala 2.5 and higher, you can simplify queries that use many
> UPPER() and LOWER() calls to do case-insensitive comparisons, by using
> the ILIKE or IREGEXP operators instead. See ILIKE Operator
> <https://docs.cloudera.com/documentation/enterprise/5-9-x/topics/impala_operators.html#ilike>
> and IREGEXP Operator
> <https://docs.cloudera.com/documentation/enterprise/5-9-x/topics/impala_operators.html#iregexp> for
> details.
>
> On Mon, Aug 24, 2020 at 11:24 AM Jeff Mortimer <jm...@phdata.io>
> wrote:
>
>> Hey all! Is it possible to set up Impala to default to case-insensitive
>> searching? In other words, a search for "fooBar" returns "fooBar",
>> "foobar", "FOOBAR", etc? I've been looking through the documentation and
>> haven't found anything, but just wanted to be sure...
>>
>> Also, I'm interested in joining the Slack workspace, but the link
>> previously posted to this list is returning an error that says "this link
>> is no longer active". Can someone post an updated invite link?
>>
>> Thanks!
>>
>> --
>>
>> Jeff Mortimer
>>
>> phData
>>
>> P: 651-247-9352
>>
>> E: jmortimer@phdata.io
>>
>> <https://www.phdata.io/>
>>
>> phData Voted 2020 Best Places to Work
>> <https://www.phdata.io/2020-best-places-to-work-winner/>
>>
>> <https://www.instagram.com/phdatainc/>
>> <https://www.linkedin.com/company/phdata/>
>> <https://twitter.com/phdatainc> <https://www.facebook.com/phData.io/>
>>
>
Re: Defaulting to case-insensitive searching
Posted by Boris Tyukin <bo...@boristyukin.com>.
Jeff, I think your best option is to use ilike/iregexp. One of these things
that I do not like about Impala :)
bonus tip, if you end up with lots of LIKEs, regexp will be way more
efficient.
In CDH 5.7 / Impala 2.5 and higher, you can simplify queries that use many
UPPER() and LOWER() calls to do case-insensitive comparisons, by using the
ILIKE or IREGEXP operators instead. See ILIKE Operator
<https://docs.cloudera.com/documentation/enterprise/5-9-x/topics/impala_operators.html#ilike>
and IREGEXP Operator
<https://docs.cloudera.com/documentation/enterprise/5-9-x/topics/impala_operators.html#iregexp>
for
details.
On Mon, Aug 24, 2020 at 11:24 AM Jeff Mortimer <jm...@phdata.io> wrote:
> Hey all! Is it possible to set up Impala to default to case-insensitive
> searching? In other words, a search for "fooBar" returns "fooBar",
> "foobar", "FOOBAR", etc? I've been looking through the documentation and
> haven't found anything, but just wanted to be sure...
>
> Also, I'm interested in joining the Slack workspace, but the link
> previously posted to this list is returning an error that says "this link
> is no longer active". Can someone post an updated invite link?
>
> Thanks!
>
> --
>
> Jeff Mortimer
>
> phData
>
> P: 651-247-9352
>
> E: jmortimer@phdata.io
>
> <https://www.phdata.io/>
>
> phData Voted 2020 Best Places to Work
> <https://www.phdata.io/2020-best-places-to-work-winner/>
>
> <https://www.instagram.com/phdatainc/>
> <https://www.linkedin.com/company/phdata/> <https://twitter.com/phdatainc>
> <https://www.facebook.com/phData.io/>
>