[
https://issues.apache.org/jira/browse/PHOENIX-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980870#comment-16980870
]
Chinmay Kulkarni commented on PHOENIX-5584:
-------------------------------------------
[~larsh] In your
[comment|https://issues.apache.org/jira/browse/PHOENIX-5584?focusedCommentId=16980846&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16980846],
did you just query the view from the old client (with the rollback config set
to true), leading to this exception?
Also, I think irrespective of the value of the rollback config, old clients
should either get the correct metadata/be able to do an operation OR get an
exception, rather than silently failing like it does right now.
I don't think it makes sense to throw an exception and disallow old clients
from even querying a view created by a 4.15 client (disallowing adding a column
and other such DDL is still fine). To support old clients, I guess we will need
to bring back some of the old client logic to the server (maybe we already do
that when rollback is true), wdyt [~tdsilva]?
> old client can't get right view metadata when 4.15 client created view
> ----------------------------------------------------------------------
>
> Key: PHOENIX-5584
> URL: https://issues.apache.org/jira/browse/PHOENIX-5584
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.15.0, 5.1.0
> Reporter: Xinyi Yan
> Assignee: Chinmay Kulkarni
> Priority: Blocker
> Fix For: 4.15.0, 5.1.0
>
>
> To reproduce this bug locally:
> 1. start the sandbox at 4.15.
> 2. created table and view at 4.15 client.
> {code:java}
> CREATE TABLE AAA (A BIGINT PRIMARY KEY, B BIGINT);
> CREATE VIEW A_VIEW AS SELECT * FROM AAA;
> {code}
> 3. query `SELECT * FROM A_VIEW` at 4.14 client.
> {code:java}
> 0: jdbc:phoenix:localhost:51070> SELECT * FROM A_VIEW;
> +--+
> | |
> +--+
> +--+
> No rows selected (0.009 seconds)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
