Agreed.
I will see what kind of alternative we can do on our side
On Mon, Apr 22, 2019 at 2:53 PM Vova Vysotskyi wrote:
> Hi Nitin,
>
> This behavior to allow aliases in a group by clause is driven by Calcite
> and commonly used in other projects.
> I think the workaround proposed by Aman is
Hi Nitin,
This behavior to allow aliases in a group by clause is driven by Calcite
and commonly used in other projects.
I think the workaround proposed by Aman is the best solution for this
problem, since for example if you have several aggregate functions in the
project for the same columns, it
Right now the aliases are derived programmatically and we use the same name
in group by as an alias and these are already defined in the jobs so we can
not change them now
That's one reason it became blocker as these jobs are configured and were
running fine and suddenly started breaking.
On Sat,
Interesting that it ran on 1.13..but I still think the new behavior is the
right one. Several changes went into Calcite between Drill's 1.13 and 1.15
release, so I cannot identify when this behavior changed. Can you use a
slightly different alias name ? The following should work:
select
sorry my bad. i meant the query which was failing was with alias
following is output on drill 1.13.0
bash-3.2$ bin/drill-embedded
Apr 20, 2019 2:46:45 AM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
01:25:26...
This is legal:
select max(last_name) from cp.`employee.json` group by last_name limit 5;
But this is not:
select max(last_name) last_name from cp.`employee.json` group by
last_name limit 5;
The reason is the second query is aliasing the max() output to 'last_name'
which is being referenced
I think the error is not with storage plugin but with query parsing
here is the exception
0: jdbc:drill:zk=local> select max(last_name) last_name from
cp.`employee.json` group by last_name limit 5;
Error: VALIDATION ERROR: From line 1, column 8 to line 1, column 21:
Aggregate expression is
(Replying on the Drill user list)
This is odd. The CP storage plugin is inbuilt with Drill and that hasn't
changed. 1.15 by itself works fine.
What is the error you are seeing, Nitin?
On 4/18/2019 10:58:48 PM, Nitin Pawar wrote:
Hi,
We are trying to upgrade drill from 1.13 to 1.15
Hi,
We are trying to upgrade drill from 1.13 to 1.15
following query works in drill 1.13 but not in 1.15
select max(last_name) from cp.`employee.json` group by last_name limit 5
can you let us know if this backward compatibility issue will be fixed ??
--
Nitin Pawar
