[jira] [Updated] (PHOENIX-6424) SELECT cf1.* FAILS with a WHERE clause including cf2.

[ https://issues.apache.org/jira/browse/PHOENIX-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6424: --- Description: {code} > create table test3(pk1 integer not null primary key, x.v1 varchar,

[jira] [Updated] (PHOENIX-6424) SELECT cf1.* FAILS with a WHERE clause including cf2.

[ https://issues.apache.org/jira/browse/PHOENIX-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6424: --- Description: {code} > create table test3(pk1 integer not null primary key, x.v1 varchar,

[jira] [Updated] (PHOENIX-6424) SELECT cf1.* FAILS with a WHERE clause including cf2.

[ https://issues.apache.org/jira/browse/PHOENIX-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6424: --- Description: {code} > create table test3(pk1 integer not null primary key, x.v1varchar,

[jira] [Updated] (PHOENIX-6423) Wildcard queries fail with mixed default and explicit column families.

[ https://issues.apache.org/jira/browse/PHOENIX-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6423: --- Attachment: 6423-5.1.txt > Wildcard queries fail with mixed default and explicit column

[jira] [Updated] (PHOENIX-6423) Wildcard queries fail with mixed default and explicit column families.

[ https://issues.apache.org/jira/browse/PHOENIX-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6423: --- Affects Version/s: 5.1.1 > Wildcard queries fail with mixed default and explicit column

[jira] [Created] (PHOENIX-6424) SELECT cf1.* FAILS with a WHERE clause including cf2.

Lars Hofhansl created PHOENIX-6424: -- Summary: SELECT cf1.* FAILS with a WHERE clause including cf2. Key: PHOENIX-6424 URL: https://issues.apache.org/jira/browse/PHOENIX-6424 Project: Phoenix

Re: [VOTE] Release of Apache Phoenix 5.1.1 RC2

PHOENIX-6423 could be blocker...? What happens is that SELECT * queries with mixed default and explicit column families would return the wrong set of columns. And in some situation the WHERE clause evaluation would fail. I'm fine either way. -- Lars On Friday, March 19, 2021, 7:04:08 PM

[jira] [Updated] (PHOENIX-6423) Wildcard queries fail with mixed default and explicit column families.

[ https://issues.apache.org/jira/browse/PHOENIX-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6423: --- Summary: Wildcard queries fail with mixed default and explicit column families. (was:

[jira] [Updated] (PHOENIX-6423) Mixing default and explicit column families causes exceptions and wrong results.

[ https://issues.apache.org/jira/browse/PHOENIX-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6423: --- Description: This one is obscure. Edit: not so obscure, see below. Without a local index

[jira] [Updated] (PHOENIX-6423) Mixing default and explicit column families causes exceptions and wrong results.

[ https://issues.apache.org/jira/browse/PHOENIX-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6423: --- Priority: Critical (was: Major) > Mixing default and explicit column families causes

[jira] [Updated] (PHOENIX-6423) Mixing default and explicit column families causes exceptions and wrong results.

[ https://issues.apache.org/jira/browse/PHOENIX-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated PHOENIX-6423: --- Description: This one is obscure. Edit: not so obscure, see below. Without a local index