[
https://issues.apache.org/jira/browse/PHOENIX-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980604#comment-16980604
]
Chinmay Kulkarni commented on PHOENIX-5584:
-------------------------------------------
[~larsh] [~yanxinyi] [~vincentpoon]
On second thought, I actually think this is by design due to the change
introduced by [PHOENIX-4893|https://issues.apache.org/jira/browse/PHOENIX-4893]
and [PHOENIX-4765|https://issues.apache.org/jira/browse/PHOENIX-4765] since we
only continue writing the parent table column metadata while creating a view in
case "phoenix.allow.system.catalog.rollback" is true. If this config is false
(which is the default case), this is not done.
I have verified that when the above config is true, this issue does not exist
and old clients are able to query the view properly.
[~tdsilva] can you please confirm my understanding?
> 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 TABLE 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)
