[
https://issues.apache.org/jira/browse/PHOENIX-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981887#comment-16981887
]
Lars Hofhansl edited comment on PHOENIX-5584 at 11/25/19 9:00 PM:
------------------------------------------------------------------
Also tried with both phoenix.schema.isNamespaceMappingEnabled and
phoenix.allow.system.catalog.rollback enabled.
Cool. Will commit soon.
If someone can think of a good way to tests for this, I'd love to hear that. As
is we do not have a single backwards compatibility tests with an old client.
We'd have to somehow check-in a old copy of the jar (or at least the relevant
client classes).
was (Author: lhofhansl):
Also tried with both phoenix.schema.isNamespaceMappingEnabled and
phoenix.allow.system.catalog.rollback enabled.
> Older clients don't get correct view metadata when a 4.15 client creates a
> 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: Lars Hofhansl
> Priority: Blocker
> Fix For: 4.15.0, 5.1.0
>
> Attachments: 5584-4.x-HBase-1.5-v2.txt, 5584-4.x-HBase-1.5-v4.txt,
> 5584-4.x-HBase-1.5.txt, PHOENIX-5584-4.x-HBase-1.3-v3.patch
>
>
> 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)
