hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Francke (JIRA)" <>
Subject [jira] [Commented] (HIVE-7348) Beeline could not parse ; separated queries provided with -e option
Date Mon, 04 Aug 2014 08:48:13 GMT


Lars Francke commented on HIVE-7348:

I won't argue much on this and leave the final decision up to you but here's my opinion:

I think that splitting on semicolon as well as requiring an escaped semicolon are bad ideas
because both need special handling on the client side. I've written quite a few bash jobs
that are run as cron or manually and take some input put it in a query and execute it. All
these would now need to be changed to special case the semicolon. The help on the other hand
says {{query that should be executed}} which is singular.

So what you're really trying to do is to add a new feature. What I've been doing when I need
multiple statements is just call beeline multiple times. Maybe another feature to add instead
is to support multiple "-e" parameters.

You could obviously use the HiveParser in beeline to parse the statement but then we're tied
to a specific Hive version again which we don't want either.

So while Ashish has already put work into this I'm afraid I'm in favor of closing this issue
as WONTFIX for the reasons mentioned.

> Beeline could not parse ; separated queries provided with -e option
> -------------------------------------------------------------------
>                 Key: HIVE-7348
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Ashish Kumar Singh
>            Assignee: Ashish Kumar Singh
>         Attachments: HIVE-7348.1.patch, HIVE-7348.2.patch, HIVE-7348.patch
> Beeline could not parse ; separated queries provided with -e option. This works fine
on hive cli.

This message was sent by Atlassian JIRA

View raw message