[
https://issues.apache.org/jira/browse/PHOENIX-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980832#comment-16980832
]
Lars Hofhansl commented on PHOENIX-5584:
----------------------------------------
[~ckulkarni], shouldn't phoenix.allow.system.catalog.rollback default to true
then?
The way we do updates we upgrade the server first and then some time (weeks)
later the client. During that time everything has to work. Of course we could
set the flag to true.
But the of course we are not getting all of the benefits so after all clients
are upgraded we should unset that flag again.
Is there no other way? I suppose we need to carefully think abut how client
retrieve the metadata and cleanly disentangle that from how the metadata is
actually stored on the server.
But I agree if it works with phoenix.allow.system.catalog.rollback set to true
is not necessarily a blocker.
> 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)
