[
https://issues.apache.org/jira/browse/PHOENIX-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980971#comment-16980971
]
Lars Hofhansl edited comment on PHOENIX-5584 at 11/24/19 5:13 AM:
------------------------------------------------------------------
I see. Then maybe the answer is to default to too false in 4.15.0? People can
do it, but default would be not to.
I guess best would be if it also was a SQL command like EXECUTE UPGRADE that
can be used to trigger the internal metadata upgrades, or perhaps an option to
it.
was (Author: lhofhansl):
I see. Then maybe the answer is to default to too false in 4.15.0? People can
do it, but default would be not to.
I guess best would be if it also was a SQL command like the one that can be
used to trigger the internal metadata upgrades.
> 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)
