FAQ
Hi,

This is a valid bug, can you file it at
https://issues.cloudera.org/browse/IMPALA please? The sanitizer in
impala_shell.py is lower-casing the first read token to ascertain what
command it is, and doesn't currently counter the "=".

You can workaround it by adding spaces around that = in your
highlighted statement. That is, this should work:

impala_account_dim.account_name = "King.com"
On Tue, Apr 16, 2013 at 3:55 PM, wrote:
Hi,

When I run the query -
select pq_network_fact.day_key,
sum(pq_network_fact.spend)
from pq_network_fact join impala_account_dim on
pq_network_fact.advertiser_account_key = impala_account_dim.account_key
join impala_date_dim on pq_network_fact.day_key = impala_date_dim.day_key
where
impala_date_dim.day_key = 1554 and
impala_account_dim.account_name="King.com"
group by pq_network_fact.day_key;

Impala-shell is converting it to -

Query: select pq_network_fact.day_key,
sum(pq_network_fact.spend)
from pq_network_fact join impala_account_dim on
pq_network_fact.advertiser_account_key = impala_account_dim.account_key
join impala_date_dim on pq_network_fact.day_key = impala_date_dim.day_key
where
impala_date_dim.day_key = 1554 and
impala_account_dim.account_name="king.com" group by pq_network_fact.day_key

This seems to be happening only when there are newlines in the query. Is
this a bug in 0.7? I think queries with newlines were not supported earlier?
Thanks,
Jaideep


_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify us
immediately by responding to this email and then delete it from your system.
The firm is neither liable for the proper and complete transmission of the
information contained in this communication nor for any delay in its
receipt.


--
Harsh J

Search Discussions

  • Jaideep Dhok at Apr 16, 2013 at 11:02 am
    Created - https://issues.cloudera.org/browse/IMPALA-261

    Thanks
    Jaideep.

    On Tue, Apr 16, 2013 at 4:21 PM, Harsh J wrote:

    Hi,

    This is a valid bug, can you file it at
    https://issues.cloudera.org/browse/IMPALA please? The sanitizer in
    impala_shell.py is lower-casing the first read token to ascertain what
    command it is, and doesn't currently counter the "=".

    You can workaround it by adding spaces around that = in your
    highlighted statement. That is, this should work:

    impala_account_dim.account_name = "King.com"
    On Tue, Apr 16, 2013 at 3:55 PM, wrote:
    Hi,

    When I run the query -
    select pq_network_fact.day_key,
    sum(pq_network_fact.spend)
    from pq_network_fact join impala_account_dim on
    pq_network_fact.advertiser_account_key = impala_account_dim.account_key
    join impala_date_dim on pq_network_fact.day_key = impala_date_dim.day_key
    where
    impala_date_dim.day_key = 1554 and
    impala_account_dim.account_name="King.com"
    group by pq_network_fact.day_key;

    Impala-shell is converting it to -

    Query: select pq_network_fact.day_key,
    sum(pq_network_fact.spend)
    from pq_network_fact join impala_account_dim on
    pq_network_fact.advertiser_account_key = impala_account_dim.account_key
    join impala_date_dim on pq_network_fact.day_key = impala_date_dim.day_key
    where
    impala_date_dim.day_key = 1554 and
    impala_account_dim.account_name="king.com" group by
    pq_network_fact.day_key
    This seems to be happening only when there are newlines in the query. Is
    this a bug in 0.7? I think queries with newlines were not supported earlier?
    Thanks,
    Jaideep


    _____________________________________________________________
    The information contained in this communication is intended solely for the
    use of the individual or entity to whom it is addressed and others
    authorized to receive it. It may contain confidential or legally
    privileged
    information. If you are not the intended recipient you are hereby notified
    that any disclosure, copying, distribution or taking any action in reliance
    on the contents of this information is strictly prohibited and may be
    unlawful. If you have received this communication in error, please notify us
    immediately by responding to this email and then delete it from your system.
    The firm is neither liable for the proper and complete transmission of the
    information contained in this communication nor for any delay in its
    receipt.


    --
    Harsh J
    --
    _____________________________________________________________
    The information contained in this communication is intended solely for the
    use of the individual or entity to whom it is addressed and others
    authorized to receive it. It may contain confidential or legally privileged
    information. If you are not the intended recipient you are hereby notified
    that any disclosure, copying, distribution or taking any action in reliance
    on the contents of this information is strictly prohibited and may be
    unlawful. If you have received this communication in error, please notify
    us immediately by responding to this email and then delete it from your
    system. The firm is neither liable for the proper and complete transmission
    of the information contained in this communication nor for any delay in its
    receipt.
  • Harsh J at Apr 16, 2013 at 11:04 am
    Thanks Jaideep!
    On Tue, Apr 16, 2013 at 4:32 PM, Jaideep Dhok wrote:
    Created - https://issues.cloudera.org/browse/IMPALA-261

    Thanks
    Jaideep.

    On Tue, Apr 16, 2013 at 4:21 PM, Harsh J wrote:

    Hi,

    This is a valid bug, can you file it at
    https://issues.cloudera.org/browse/IMPALA please? The sanitizer in
    impala_shell.py is lower-casing the first read token to ascertain what
    command it is, and doesn't currently counter the "=".

    You can workaround it by adding spaces around that = in your
    highlighted statement. That is, this should work:

    impala_account_dim.account_name = "King.com"
    On Tue, Apr 16, 2013 at 3:55 PM, wrote:
    Hi,

    When I run the query -
    select pq_network_fact.day_key,
    sum(pq_network_fact.spend)
    from pq_network_fact join impala_account_dim on
    pq_network_fact.advertiser_account_key = impala_account_dim.account_key
    join impala_date_dim on pq_network_fact.day_key =
    impala_date_dim.day_key
    where
    impala_date_dim.day_key = 1554 and
    impala_account_dim.account_name="King.com"
    group by pq_network_fact.day_key;

    Impala-shell is converting it to -

    Query: select pq_network_fact.day_key,
    sum(pq_network_fact.spend)
    from pq_network_fact join impala_account_dim on
    pq_network_fact.advertiser_account_key = impala_account_dim.account_key
    join impala_date_dim on pq_network_fact.day_key =
    impala_date_dim.day_key
    where
    impala_date_dim.day_key = 1554 and
    impala_account_dim.account_name="king.com" group by
    pq_network_fact.day_key

    This seems to be happening only when there are newlines in the query. Is
    this a bug in 0.7? I think queries with newlines were not supported
    earlier?
    Thanks,
    Jaideep


    _____________________________________________________________
    The information contained in this communication is intended solely for
    the
    use of the individual or entity to whom it is addressed and others
    authorized to receive it. It may contain confidential or legally
    privileged
    information. If you are not the intended recipient you are hereby
    notified
    that any disclosure, copying, distribution or taking any action in
    reliance
    on the contents of this information is strictly prohibited and may be
    unlawful. If you have received this communication in error, please
    notify us
    immediately by responding to this email and then delete it from your
    system.
    The firm is neither liable for the proper and complete transmission of
    the
    information contained in this communication nor for any delay in its
    receipt.


    --
    Harsh J


    _____________________________________________________________
    The information contained in this communication is intended solely for the
    use of the individual or entity to whom it is addressed and others
    authorized to receive it. It may contain confidential or legally privileged
    information. If you are not the intended recipient you are hereby notified
    that any disclosure, copying, distribution or taking any action in reliance
    on the contents of this information is strictly prohibited and may be
    unlawful. If you have received this communication in error, please notify us
    immediately by responding to this email and then delete it from your system.
    The firm is neither liable for the proper and complete transmission of the
    information contained in this communication nor for any delay in its
    receipt.


    --
    Harsh J

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupimpala-user @
categorieshadoop
postedApr 16, '13 at 10:52a
activeApr 16, '13 at 11:04a
posts3
users2
websitecloudera.com
irc#hadoop

2 users in discussion

Harsh J: 2 posts Jaideep Dhok: 1 post

People

Translate

site design / logo © 2022 Grokbase